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/RapierCraftStudios/ForgeDockWrote 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/rapiercraftstudios/forgedock/work-on)<a href="https://agentmods.dev/commands/rapiercraftstudios/forgedock/work-on"><img src="https://agentmods.dev/badge/commands/rapiercraftstudios/forgedock/work-on/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/rapiercraftstudios/forgedock/work-on"><img src="https://agentmods.dev/badge/commands/rapiercraftstudios/forgedock/work-on.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.00016 | $0.19220 |
| Opus 5.5 | $0.00006 | $0.07688 |
| Sonnet 5.5 | $0.00003 | $0.03844 |
| Haiku 4.5 | $0.00002 | $0.01922 |
Grade B, and why
work-on scanned grade B with 1 finding 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 5d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
type forge_resolve >/dev/null 2>&1 || { setopt nonomatch 2>/dev/null || true; FORGE_SOURCED_ROOT='${CLAUDE_PLUGIN_ROOT}'; for _r in "$(cygpath -u "${FORGEDOCK_HOME:-}" 2>/dev/null || printf %s "${FORGEDOCK_HOME:-}")" '${ The source is not reproduced here
Licensed AGPL-3.0
The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- 5d ago Changed 2d72e57c736c
- 6d ago Changed · -1 lines 75ec6c11fe6c
- 7d ago Changed · -50 lines 947fe6c0e94e
- 8d ago Changed · +8 lines e3e8bbb0fb0d
- 9d ago Changed · +9 lines 9cb091917e2d
- 10d ago Changed · +128 lines a82495bb0556
- 11d ago Changed · -1,828 lines 2be07f6c3cd7
- 1mo ago First seen · 2,499 lines · 16 tokens per session scan B 38eddfdd9736
work-on is a command published in the GitHub repository RapierCraftStudios/ForgeDock (119 stars, last pushed 4d ago), licensed AGPL-3.0. It adds 16 tokens to every session and 19,220 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
portfolio-status
Review the health of all projects in the portfolio.
work-flow-release
Complete workflow to prepare and publish a release.
work-commit-push-pr
Pointer: Claude Code ships a native /commit-push-pr that owns the commit + push + PR macro. This command adds the foundation's pre-flight gate and convention sources on top — it does not re-implement the macro.
ops-standup
Morning briefing: commits, PRs, CI, blockers and priorities of the day.
release-manager
Automated release coordination and deployment with ruv-swarm orchestration for seamless version management, testing, and deployment across multiple packages.
repo-architect
Repository structure optimization and multi-repo management with ruv-swarm coordination for scalable project architecture and development workflows.