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/razaib-khan/forgeweave/forge-docsgit clone --depth 1 https://github.com/Razaib-khan/ForgeWeaveWhat 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.00010 | $0.00188 |
| Opus 5 | $0.00005 | $0.00094 |
| Sonnet 5 | $0.00002 | $0.00038 |
| Haiku 4.5 | $0.00001 | $0.00019 |
Grade A, and why
forge-docs 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 2d 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
Forge Docs
Generate or review documentation for the specified file or module.
Generate Mode (new file)
For a new module, generate:
- JSDoc/PyDoc comments for all exported functions, classes, types
- A README section describing the module's purpose, API, and usage example
- Type definitions and interfaces documentation
Review Mode (existing file)
For an existing file, review existing docs for:
- Accuracy against implementation
- Completeness (missing parameters, return types, edge cases)
- Clarity and readability
- Outdated documentation
Output format:
## {module name}
### {function/class name}
- Signature: ...
- Parameters: ...
- Returns: ...
- Example: ...
- Notes: ...
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.
- 2d ago First seen · 34 lines · 10 tokens per session scan A cbe508f316f3
forge-docs is a command published in the GitHub repository Razaib-khan/ForgeWeave (1 stars, last pushed 2mo ago), licensed MIT. It adds 10 tokens to every session and 188 once invoked, about $0.0001 per session on Opus 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
agentlas-cloud
Staff a task only from the signed-in owner's Agent Cloud agents.
issue-amend
Re-snapshot the active issue's scope from the spec, clear verified and reviewed receipts, and record the change as a permanent amendment.
q-research
Read the research-mode skill's SKILL.md for the full ruleset before proceeding. Follow all constraints, the source lookup cascade, the token budget, and the "what counts as cited" rules exactly.
auto-goal
goal 래퍼 — /goal 생성, 상태 확인, 완료/blocked handoff를 goal tool 또는 slash command로 연결합니다.
blackboard
Read or write a Network-AI blackboard key (shared multi-agent state).
create-pr
Push the current branch and open a pull request into main with a structured description derived from the branch's commits and issue references.