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 skills add traviswye/ContextAtlas --skill generate-adrsgit clone --depth 1 https://github.com/traviswye/ContextAtlasWrote 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/traviswye/contextatlas/generate-adrs)<a href="https://agentmods.dev/skills/traviswye/contextatlas/generate-adrs"><img src="https://agentmods.dev/badge/skills/traviswye/contextatlas/generate-adrs/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/skills/traviswye/contextatlas/generate-adrs"><img src="https://agentmods.dev/badge/skills/traviswye/contextatlas/generate-adrs.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.00111 | $0.02657 |
| Opus 5 | $0.00056 | $0.01328 |
| Sonnet 5 | $0.00022 | $0.00531 |
| Haiku 4.5 | $0.00011 | $0.00266 |
Grade A, and why
generate-adrs 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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 260 lines — stays where its author put it; the contents beside it link to each section on GitHub.
generate-adrs — ContextAtlas ADR generation via Claude Code session
When to use this skill
You're running ContextAtlas ADR generation inside your Claude Code
session. User invoked you via /generate-adrs slash command, OR
via contextatlas project context surfacing in their session.
This is THE canonical entry point for subscription-bounded ADR
generation. The contextatlas generate-adrs CLI binary uses
Anthropic API direct generation (different cost model; not this
skill's concern). Per ADR-02 v0.7 amendment §Decision: generation
has two entry points; each entry point uses the appropriate cost
model for its invocation context.
If user is asking how to generate ADRs:
- They're working in Claude Code session right now → invoke this skill
- They want CLI / CI/CD / scripting workflow → tell them to use
contextatlas generate-adrsfrom terminal (uses Anthropic API direct; requiresANTHROPIC_API_KEYenv var)
What this skill does
Walks the codebase, identifies non-obvious architectural decisions,
and writes canonical ContextAtlas-format ADRs to docs/adr/ in the
configured repo. Supports optional reference-context input (the
user's existing architectural documentation in any format —
Markdown ADRs, reStructuredText DEPs, Confluence exports,
architectural commentary) which informs ADR generation as PROMPT
INPUT (not direct extraction substrate).
The workflow has three MANDATORY phases (A → B → C). Each phase has explicit completion criteria; do not advance until the prior phase is substantively complete.
Step 1 — Load the canonical generate-adrs prompt via Read tool
Read tool against: .contextatlas/prompts/generate-adrs.md (cwd-relative).
This file is generated by contextatlas init from the canonical
GENERATE_ADRS_PROMPT constant at src/generation/prompt.ts. The
user repo must have run contextatlas init before invoking this
skill. If the file does not exist at this path, instruct the user
to run contextatlas init before retrying.
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.
- 9d ago First seen · 260 lines · 111 tokens per session scan A 692376ce33db
generate-adrs is a skill published in the GitHub repository traviswye/ContextAtlas (7 stars, last pushed 3mo ago), licensed MIT. It adds 111 tokens to every session and 2,657 once invoked, about $0.0006 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 skills, from other repositories
plan
Structured technical planning before implementation — architecture and task breakdown.
architecture-governance
Keep code changes conformant to a repo's real, declared architecture using ArchSteer. Use when starting work in an unfamiliar repo, before finishing/committing an architecturally significant change (new dependency, new data access, new external call, new layer), or when asked about a codebase's architecture, layers…
mpm-adr
Architecture Decision Records (ADRs) — opt-in convention for documenting significant, hard-to-reverse architectural decisions using the Nygard template.
architecture-paradigms
Selects and routes to the right architecture paradigm. Use when choosing patterns for a new system or comparing trade-offs before making architecture decisions.
design-first
Guides the creation of technical design documents before writing code, producing architecture diagrams, data models, API interface definitions, implementation plans, and multi-option trade-off analyses. Use when the user asks to plan a feature, architect a system, design an API, explore implementation approaches, or…
omm-scan
Scan codebase architecture and generate/update .omm/ documentation. Use when the user says "omm scan", "scan architecture", "update architecture", "refresh diagrams".