Forge is a command-line development environment that uses AI models as a pair programmer for working with code and shell commands. Developers use it to understand projects and carry out coding tasks through interactive, one-shot, or ZSH-based workflows. The catalogue entries extend Forge with reusable skills, agents, commands, and instructions.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add tailcallhq/forgecode --skill test-reasoninggit clone --depth 1 https://github.com/tailcallhq/forgecodeWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/tailcallhq/forgecode/test-reasoning)<a href="https://agentmods.dev/skills/tailcallhq/forgecode/test-reasoning"><img src="https://agentmods.dev/badge/skills/tailcallhq/forgecode/test-reasoning/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/tailcallhq/forgecode/test-reasoning"><img src="https://agentmods.dev/badge/skills/tailcallhq/forgecode/test-reasoning.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00064 | $0.01030 |
| Opus 5.5 | $0.00026 | $0.00412 |
| Sonnet 5.5 | $0.00013 | $0.00206 |
| Haiku 4.5 | $0.00006 | $0.00103 |
Grade A, and why
test-reasoning scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
Copies of this mod
1 near-identical copy found in the catalogue:
- test-reasoning — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Reasoning Serialization
Validates that ReasoningConfig fields are correctly serialized into provider-specific JSON
for OpenRouter, Anthropic, GitHub Copilot, and Codex.
Quick Start
Run all tests with the bundled script:
./scripts/test-reasoning.sh
The script builds forge in debug mode, runs each provider/model combination, captures the
outgoing HTTP request body via FORGE_DEBUG_REQUESTS, and asserts the correct JSON fields.
Running a Single Test Manually
FORGE_DEBUG_REQUESTS="forge.request.json" \
FORGE_SESSION__PROVIDER_ID=<provider_id> \
FORGE_SESSION__MODEL_ID=<model_id> \
FORGE_REASONING__EFFORT=<effort> \
target/debug/forge -p "Hello!"
Then inspect .forge/forge.request.json for the expected fields.
Test Coverage
| Provider | Model | Config fields | Expected JSON field |
|---|---|---|---|
open_router |
openai/o4-mini |
effort: none|minimal|low|medium|high|xhigh |
reasoning.effort |
open_router |
openai/o4-mini |
max_tokens: 4000 |
reasoning.max_tokens |
open_router |
openai/o4-mini |
effort: high + exclude: true |
reasoning.effort + .exclude |
open_router |
openai/o4-mini |
enabled: true |
reasoning.enabled |
open_router |
anthropic/claude-opus-4-5 |
max_tokens: 4000 |
reasoning.max_tokens |
open_router |
moonshotai/kimi-k2 |
max_tokens: 4000 |
reasoning.max_tokens |
open_router |
moonshotai/kimi-k2 |
effort: high |
reasoning.effort |
open_router |
minimax/minimax-m2 |
max_tokens: 4000 |
reasoning.max_tokens |
open_router |
minimax/minimax-m2 |
effort: high |
reasoning.effort |
anthropic |
claude-opus-4-6 |
effort: low|medium|high|max |
output_config.effort |
anthropic |
claude-3-7-sonnet-20250219 |
enabled: true + max_tokens: 8000 |
thinking.type + budget_tokens |
github_copilot |
o4-mini |
effort: none|minimal|low|medium|high|xhigh |
reasoning_effort (top-level) |
codex |
gpt-5.1-codex |
effort: none|minimal|low|medium|high|xhigh |
reasoning.effort + .summary |
codex |
gpt-5.1-codex |
effort: medium + exclude: true |
reasoning.summary = "concise" |
| all providers | one model each | effort: invalid |
non-zero exit, no request written |
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 62 lines · 64 tokens per session scan A 4f98815ab665
test-reasoning is a skill published in the GitHub repository tailcallhq/forgecode (7,638 stars, last pushed today), licensed Apache-2.0. It adds 64 tokens to every session and 1,030 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
advanced-evaluation
Design LLM-as-judge rubrics, direct scores and pairwise comparisons. Use for judge models, evals, position bias and calibration against human labels.
agent-harness-fault-injection
Use when an agent workflow needs deterministic recovery evidence for sandbox, MCP/tool, worker, checkpoint, memory, or orchestration failures.
agent-orchestration-improve-agent
Systematic improvement of existing agents through performance analysis, prompt engineering, and continuous iteration.
api-fuzzing-bug-bounty
Provide comprehensive techniques for testing REST, SOAP, and GraphQL APIs during bug bounty hunting and penetration testing engagements. Covers vulnerability discovery, authentication bypass, IDOR exploitation, and API-specific attack vectors.
appium-skill
Generates production-grade Appium mobile automation scripts for Android and iOS in Java, Python, or JavaScript. Supports real device and emulator testing locally and on TestMu AI cloud with 100+ real devices.
agent-evaluation
Evaluate agent behavior with versioned cases and explicit verifiers. Use when comparing agent or prompt changes, reproducing failures, or running agent regression tests.