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 skills/codexskills/agent-forge/documentation-and-adrsnpx skills add codexskills/agent-forge --skill documentation-and-adrsgit clone --depth 1 https://github.com/codexskills/agent-forgeWrote 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/skills/codexskills/agent-forge/documentation-and-adrs)<a href="https://agentmods.dev/skills/codexskills/agent-forge/documentation-and-adrs"><img src="https://agentmods.dev/badge/skills/codexskills/agent-forge/documentation-and-adrs.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.01499 |
| Opus 5 | $0.00000 | $0.00749 |
| Sonnet 5 | $0.00000 | $0.00300 |
| Haiku 4.5 | $0.00000 | $0.00150 |
Grade A, and why
documentation-and-adrs scanned grade A 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 4d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
[curl or code examples for common use cases] The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 4d ago First seen · 251 lines · 0 tokens per session scan A c80980262307
documentation-and-adrs is a skill published in the GitHub repository codexskills/agent-forge (1 stars, last pushed 2mo ago), with no licence file. It costs nothing until one of its globs matches a file; then it loads 1,499 tokens. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
eve-forge
Forge a personalized eve agent for a business end-to-end — absorb the business's artifacts, author the eve agent/ dir, validate, deploy to Vercel (or a VPS), smoke-test against ground truth, register, and evolve. The deterministic core is three safety gates distilled from a driven benchmark (BRO-1677): deploy-safety…
council-of-skills
Use when a proposed skill, workflow, or decision needs adversarial review before it ships: convenes reviewers drawn from the agent-forge registry as hostile personas, adds a BUYER who states plainly whether they would pay, and forces every verdict to include the cheapest 48-hour test that could kill or validate the…
feed-digest
Use when it is time for the weekly upstream feed review, or when the user asks what changed in the skill feeds: runs the forge miner diff, clusters new and changed upstream skills by theme, and writes a ranked proposal memo of which patterns are worth authoring into originals.
skill-steward
Use when installed skills need a lifecycle audit: scans the forge registry and the configured skill directories for staleness, overlap, and conflicting triggers, then proposes a retire, promote, merge, or quarantine action per skill with evidence.
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.