work-on

A command that takes a GitHub issue—a tracked software task or bug—and carries it through investigation, implementation, review, and merging.

In plain words
What is it for?
Use it when picking up a GitHub issue that needs research, coding, review, and integration into the project.
Why use it?
It provides one workflow for moving an issue from an open request to a reviewed change in the codebase.

Command

Install

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.

agentmods
npx agentmods add commands/rapiercraftstudios/forgedock/work-on
Clone the repo
git clone --depth 1 https://github.com/RapierCraftStudios/ForgeDock
Per session 16 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 38,771 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. Scan, not verified.
Origin unknown No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00016 $0.38771
Opus 5 $0.00008 $0.19385
Sonnet 5 $0.00003 $0.07754
Haiku 4.5 $0.00002 $0.03877

Measured 3d ago against content hash 38eddfdd9736, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 3d 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.

Unrestricted tool accessmediumExcessive agency

A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.

**Learned test commands** — After all `verification.commands` steps complete, run any commands from `learned.test_commands` (captured from owner corrections in Phase 1D or set manually in forge.yaml), filtered through th
commands/work-on.md · 2,499 lines

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.

Read it on GitHub

Changes

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.

  1. 3d ago First seen · 2,499 lines · 16 tokens per session scan B 38eddfdd9736

Subscribe to this mod's changes

work-on is a command published in the GitHub repository RapierCraftStudios/ForgeDock (118 stars, last pushed 23d ago), licensed AGPL-3.0. It adds 16 tokens to every session and 38,771 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (unrestricted tool access). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.