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.
git clone --depth 1 https://github.com/aneja5/forge-skillsWrote 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/commands/aneja5/forge-skills/build)<a href="https://agentmods.dev/commands/aneja5/forge-skills/build"><img src="https://agentmods.dev/badge/commands/aneja5/forge-skills/build/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/commands/aneja5/forge-skills/build"><img src="https://agentmods.dev/badge/commands/aneja5/forge-skills/build.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00014 | $0.00170 |
| Opus 5.5 | $0.00006 | $0.00068 |
| Sonnet 5.5 | $0.00003 | $0.00034 |
| Haiku 4.5 | $0.00001 | $0.00017 |
Grade A, and why
build 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.
What it actually says
Invoke the forge-skills:incremental-implementation skill, with forge-skills:tdd for each cycle.
Read .forge/tasks.yaml. Find the next unblocked task (dependencies complete, status not done).
Load the task's contracts from .forge/contracts/. Load only files in files_likely_affected.
Implement using strict vertical slices: RED: write one failing test for one acceptance criterion GREEN: write minimum code to make it pass Repeat for each acceptance criterion REFACTOR: clean up while all tests stay green
Commit after each completed task: "[TASK-ID] "
Update .forge/tasks.yaml status to done.
Report: which task was completed, which tasks are now unblocked.
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 · 20 lines · 14 tokens per session scan A 408c2b18184d
build is a command published in the GitHub repository aneja5/forge-skills (3 stars, last pushed 5mo ago), licensed MIT. It adds 14 tokens to every session and 170 once invoked, about $0.0001 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-31.
Other commands, from other repositories
bug
Reproduce then TDD-fix a ready-for-agent bug ticket in this checkout. Web bugs get a browser repro first.
qa
Smoke or browser-walk a running app. Report only. Do not implement. Do not merge.
coder
Autonomous code generation with batch file operations.
tdd
Test-driven development with TodoWrite planning and comprehensive testing.
uw-cmd-implement-feature
Build a feature complete: interrogation -> TDD implementation -> game feel -> documentation — all in one pass.
uw-cmd-create
Generate isolated code following a test-driven development approach.