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 agentmods add commands/hoangsonww/forge-agentic-coding-cli/fix-issuegit clone --depth 1 https://github.com/hoangsonww/Forge-Agentic-Coding-CLIWhat 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 | $0.00000 | $0.00158 |
| Opus 5 | $0.00000 | $0.00079 |
| Sonnet 5 | $0.00000 | $0.00032 |
| Haiku 4.5 | $0.00000 | $0.00016 |
Grade A, and why
fix-issue 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 yesterday.
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
!gh issue view $ARGUMENTS 2>/dev/null || echo "Could not fetch issue $ARGUMENTS"
Investigate and fix the issue above in the Forge repository.
- Identify the root cause. Prefer reading
src/core/loop.ts,src/agents/executor.ts, and the relevant registry file first. - Write or update a failing test that reproduces the bug before the fix.
- Implement the minimal fix. No speculative abstractions.
- Run
/verifyand confirm the test turns green. - Draft a commit message that follows conventional-commit style and references the issue. Do not push or open a PR unless explicitly asked.
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.
- yesterday First seen · 18 lines · 0 tokens per session scan A 37fd1618d701
fix-issue is a command published in the GitHub repository hoangsonww/Forge-Agentic-Coding-CLI (22 stars, last pushed 15d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 158 tokens. 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 commands, from other repositories
workflow-claude-settings
Track Claude Code settings report changes and find what needs updating.
implement
Execute phased implementation with validation gates.
research
Research and analyze feature viability - GO/NO-GO decision gate.
workflow-claude-subagents
Track Claude Code subagents report changes and find what needs updating.
weather-orchestrator
Fetch Dubai weather and create an SVG weather card.
time-orchestrator
Fetch the current time for Dubai (GST, UTC+4) and create a visual SVG time card.