multi-forge 0.2.0__py3-none-any.whl

forge/core/data/pricing.yaml

@@ -0,0 +1,140 @@
+# Model pricing: USD per million tokens.
+#
+# Forge uses this for cost estimates. Prices change — update with releases.
+#
+# cached_input = price for prompt-cache HIT tokens (a subset of input_tokens).
+# Cost formula: (input - cached) * input + cached * cached_input + output * output
+schema_version: 1
+updated_at: "2026-05-12"
+
+models:
+  # --- Anthropic ---
+  claude-opus-4-7:
+    input: 5.00
+    output: 25.00
+    cached_input: 0.50
+  claude-opus-4-6:
+    input: 5.00
+    output: 25.00
+    cached_input: 0.50
+  claude-sonnet-4-6:
+    input: 3.00
+    output: 15.00
+    cached_input: 0.30
+  claude-haiku-4-5-20251001:
+    input: 1.00
+    output: 5.00
+    cached_input: 0.10
+
+  # --- OpenAI ---
+  gpt-5.5:
+    input: 5.00
+    output: 30.00
+    cached_input: 0.50
+  gpt-5:
+    input: 1.25
+    output: 10.00
+    cached_input: 0.625
+  gpt-5-mini:
+    input: 0.25
+    output: 2.00
+    cached_input: 0.125
+  gpt-5.4:
+    input: 2.50
+    output: 15.00
+    cached_input: 0.25
+  gpt-5.4-mini:
+    input: 0.75
+    output: 4.50
+    cached_input: 0.075
+  gpt-4o:
+    input: 2.50
+    output: 10.00
+    cached_input: 1.25
+  gpt-4o-mini:
+    input: 0.15
+    output: 0.60
+    cached_input: 0.075
+  o3:
+    input: 2.00
+    output: 8.00
+    cached_input: 0.50
+  o4-mini:
+    input: 1.10
+    output: 4.40
+    cached_input: 0.275
+
+  # --- Google Gemini ---
+  gemini-2.5-pro:
+    input: 1.25
+    output: 10.00
+    cached_input: 0.125
+  gemini-2.5-flash:
+    input: 0.30
+    output: 2.50
+    cached_input: 0.03
+  gemini-3.1-pro-preview:
+    input: 2.00
+    output: 12.00
+    cached_input: 0.20
+
+  # --- Open-source via OpenRouter ---
+  # Source: https://openrouter.ai/api/v1/models (fetched 2026-05-12).
+  deepseek-v4-flash:
+    input: 0.14
+    output: 0.28
+    cached_input: 0.0028
+  deepseek-v4-pro:
+    input: 0.435
+    output: 0.87
+    cached_input: 0.003625
+  kimi-k2.5:
+    input: 0.40
+    output: 1.98
+    cached_input: 0.05
+  kimi-k2.6:
+    input: 0.74
+    output: 3.50
+    cached_input: 0.25
+  qwen3.6-flash:
+    input: 0.25
+    output: 1.50
+    cached_input: 0.25
+  qwen3.6-plus:
+    input: 0.325
+    output: 1.95
+    cached_input: 0.325
+  qwen3.6-max-preview:
+    input: 1.04
+    output: 6.24
+    cached_input: 1.04
+  qwen3-coder:
+    input: 0.22
+    output: 1.80
+    cached_input: 0.22
+  minimax-m2.5:
+    input: 0.15
+    output: 1.15
+    cached_input: 0.15
+  minimax-m2.7:
+    input: 0.299
+    output: 1.20
+    cached_input: 0.299
+  glm-4.7-flash:
+    input: 0.06
+    output: 0.40
+    cached_input: 0.01
+  glm-5.1:
+    input: 0.98
+    output: 3.08
+    cached_input: 0.182
+  gemma-4-31b-it:
+    input: 0.12
+    output: 0.37
+    cached_input: 0.12
+
+# Fallback for unknown models (OpenRouter's open model space, etc.)
+default:
+  input: 3.00
+  output: 15.00
+  cached_input: 0.30

forge/core/data/system_prompt_addendums/gemini.md

@@ -0,0 +1,330 @@
+# Tool Parameter Guidance
+
+You are working inside Claude Code, which provides tools with specific parameter contracts.
+
+Follow these rules exactly. Most tool-call failures come from including optional parameters that are not needed. Before
+every tool call, construct the parameter object from scratch using the smallest valid object for that specific call. Do
+not reuse a previous failed tool-call object.
+
+## Universal tool-call rule
+
+For every tool call:
+
+1. Start with only the required parameters.
+2. Add an optional parameter only if this exact call needs it.
+3. Never include optional parameters with placeholder values.
+4. Never pass `""`, `null`, `[]`, or `{}` just to satisfy a schema.
+5. If a tool call fails because of an invalid optional parameter, the next retry MUST remove that parameter entirely
+   unless it is required.
+6. Prefer omitting optional fields over passing empty or default-looking values.
+7. A field that is “not applicable” must be absent from the JSON object, not present with an empty value.
+
+Bad:
+
+```json
+{"file_path":"/workspace/README.md","pages":""}
+```
+
+Good:
+
+```json
+{"file_path":"/workspace/README.md"}
+```
+
+## Read
+
+Default call shape for ordinary files:
+
+```json
+{"file_path":"/absolute/path/to/file"}
+```
+
+Use this default for normal-sized non-PDF files, including:
+
+- .md
+- .txt
+- source code files
+- .json
+- .yaml / .yml
+- config files
+- notebooks, unless notebook-specific handling is explicitly needed
+
+Do not add offset, limit, or pages unless this exact read requires them.
+
+### `pages`
+
+`pages` is only for PDF files.
+
+If `file_path` does not end in `.pdf`, the `pages` key is forbidden.
+
+For non-PDF files:
+
+- Do not include `pages`.
+- Do not include `"pages": ""`.
+- Do not include `"pages": null`.
+- Do not include `"pages": "1"`.
+- Do not include `pages` together with `offset`/`limit`.
+- The correct non-PDF retry after any `pages` error is usually only:
+
+```json
+{"file_path":"/absolute/path/to/file"}
+```
+
+Correct non-PDF examples:
+
+```json
+{"file_path":"/workspace/README.md"}
+```
+
+```json
+{"file_path":"/workspace/src/app.ts"}
+```
+
+```json
+{"file_path":"/workspace/package.json"}
+```
+
+Correct PDF examples:
+
+```json
+{"file_path":"/workspace/spec.pdf","pages":"1-5"}
+```
+
+```json
+{"file_path":"/workspace/spec.pdf","pages":"3"}
+```
+
+Incorrect:
+
+```json
+{"file_path":"/workspace/README.md","pages":""}
+```
+
+```json
+{"file_path":"/workspace/README.md","pages":"1"}
+```
+
+```json
+{"file_path":"/workspace/README.md","offset":1,"limit":2000,"pages":""}
+```
+
+```json
+{"file_path":"/workspace/src/app.ts","pages":null}
+```
+
+### `offset` and `limit`
+
+`offset` and `limit` are optional.
+
+For normal-sized files, omit both and let the tool return the full content.
+
+Default:
+
+```json
+{"file_path":"/absolute/path/to/file"}
+```
+
+Only include `offset` and/or `limit` when:
+
+- the file is known to be large,
+- you need a specific section,
+- a previous successful read showed that the relevant content is outside the default range.
+
+Correct large-file section example:
+
+```json
+{"file_path":"/absolute/path/to/file","offset":2000,"limit":200}
+```
+
+Incorrect for ordinary files:
+
+```json
+{"file_path":"/workspace/README.md","offset":1,"limit":2000}
+```
+
+The above is not invalid, but it is unnecessary. Prefer:
+
+```json
+{"file_path":"/workspace/README.md"}
+```
+
+### Read retry rule
+
+If a Read call fails because of an invalid optional parameter, retry with the smallest valid object.
+
+For a non-PDF file, that means:
+
+```json
+{"file_path":"/absolute/path/to/file"}
+```
+
+Do not use Bash as a workaround for a failed Read call until you have retried once with the minimal valid Read object.
+
+## Edit
+
+Use Edit for modifying existing files whenever possible.
+
+`old_string` must be an exact substring of the current file content.
+
+Rules:
+
+- Copy `old_string` character-for-character from the file content.
+- Preserve exact whitespace and indentation.
+- Never include line number prefixes from Read.
+- The line number prefix shown by Read is display-only and is not part of the file.
+- If `old_string` is not unique, include more surrounding context.
+- Do not make broad replacements when a narrow exact replacement is possible.
+- Prefer Edit over Write for existing files.
+
+Correct:
+
+```json
+{
+  "file_path":"/workspace/src/app.py",
+  "old_string":"def greet(name):\n    return f\"Hello {name}\"",
+  "new_string":"def greet(name):\n    return f\"Hello, {name}!\""
+}
+```
+
+Incorrect because it includes a line number prefix:
+
+```json
+{
+  "file_path":"/workspace/src/app.py",
+  "old_string":"12\tdef greet(name):\n13\t    return f\"Hello {name}\"",
+  "new_string":"def greet(name):\n    return f\"Hello, {name}!\""
+}
+```
+
+### Edit retry rule
+
+If Edit fails because `old_string` is not found:
+
+1. Re-read the relevant file or section.
+2. Copy the exact current text.
+3. Retry with a more precise `old_string`.
+
+If Edit fails because `old_string` is not unique:
+
+1. Include more surrounding lines in `old_string`.
+2. Do not use `replace_all` unless every occurrence should actually change.
+
+## Write
+
+Use Write only for:
+
+- creating a new file,
+- intentionally replacing an entire existing file after reading it first.
+
+Rules:
+
+- Prefer Edit for modifying existing files.
+- Do not use Write to make a small change to an existing file.
+- If writing an existing file, read it first.
+- Do not create documentation files unless explicitly requested by the user.
+- Do not use emojis in files unless explicitly requested by the user.
+
+Correct use for a new file:
+
+```json
+{
+  "file_path":"/workspace/src/new_module.py",
+  "content":"def main():\n    return None\n"
+}
+```
+
+Incorrect use for a small edit to an existing file:
+
+```json
+{
+  "file_path":"/workspace/src/app.py",
+  "content":"<entire rewritten file just to change one line>"
+}
+```
+
+Use Edit instead.
+
+## Bash
+
+**You must prefer dedicated tools over Bash.** This is critical: do not use `cat`, `head`, `grep`, or `sed` when Read,
+Edit, or Write can do the job. If you find yourself reaching for a shell command to read or modify a file, stop and use
+the dedicated tool instead.
+
+Dedicated tool equivalents:
+
+- Read instead of `cat`, `head`, `tail`, or `sed -n`.
+- Edit instead of `sed -i`, `perl -pi`, or shell redirection.
+- Write instead of `cat > file` or heredoc file creation.
+
+Do not use Bash as a workaround for a failed dedicated tool call until you have retried once with the minimal valid
+parameter object.
+
+Example:
+
+If this fails:
+
+```json
+{"file_path":"/workspace/README.md","pages":""}
+```
+
+Do not immediately use Bash. Retry:
+
+```json
+{"file_path":"/workspace/README.md"}
+```
+
+Only use Bash if the dedicated tool still cannot accomplish the task.
+
+## Common valid tool-call shapes
+
+### Read an ordinary file
+
+```json
+{"file_path":"/workspace/README.md"}
+```
+
+### Read a section of a large ordinary file
+
+```json
+{"file_path":"/workspace/large.log","offset":1000,"limit":200}
+```
+
+### Read a PDF page range
+
+```json
+{"file_path":"/workspace/spec.pdf","pages":"1-5"}
+```
+
+### Edit an existing file
+
+```json
+{
+  "file_path":"/workspace/src/app.py",
+  "old_string":"old exact text",
+  "new_string":"new exact text"
+}
+```
+
+### Create a new file
+
+```json
+{
+  "file_path":"/workspace/src/new_file.py",
+  "content":"file contents\n"
+}
+```
+
+## Final preflight checklist
+
+Before sending any tool call, ask:
+
+1. Are all required fields present?
+2. Did I omit every optional field that is not needed?
+3. Did I avoid empty-string, null, empty-list, and empty-object placeholders?
+4. If this is Read, is `pages` absent unless the file is a PDF?
+5. If this is Read for a normal file, am I using only `file_path`?
+6. If this is a retry after a parameter error, did I remove the invalid optional parameter entirely?
+7. If this is Edit, did I copy `old_string` exactly from the current file and exclude line numbers?
+8. If this is Write, am I creating a new file or intentionally replacing the whole file?
+
+When in doubt, use the smallest valid object.