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.
git clone --depth 1 https://github.com/aspenkit/aspensWrote 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/commands/aspenkit/aspens/dev-docs)<a href="https://agentmods.dev/commands/aspenkit/aspens/dev-docs"><img src="https://agentmods.dev/badge/commands/aspenkit/aspens/dev-docs/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/commands/aspenkit/aspens/dev-docs"><img src="https://agentmods.dev/badge/commands/aspenkit/aspens/dev-docs.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.00009 | $0.00314 |
| Opus 5.5 | $0.00004 | $0.00126 |
| Sonnet 5.5 | $0.00002 | $0.00063 |
| Haiku 4.5 | $0.00001 | $0.00031 |
Grade A, and why
dev-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 1mo 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
Create a focused, actionable plan for: $ARGUMENTS
Instructions
-
Analyze the request — determine scope by reading relevant code
-
Create a plan with:
- Goal (one sentence)
- Approach (brief architectural description, key decisions)
- Phases with tasks (each phase independently verifiable)
- Acceptance criteria per phase
-
Task Breakdown:
- Tasks within a phase are independent (can run in parallel)
- Tasks across phases are sequential
- Each task specifies files it touches
- Include acceptance criteria for each task
-
Create plan file:
- Create directory:
dev/active/[task-name]/(relative to project root) - Generate one file:
plan.md - Keep it under 100 lines — concise plans get executed, long ones don't
- Create directory:
Quality Standards
- Plans must be actionable — specific files, specific changes, specific verification commands
- Each phase must leave the codebase in a working state
- Don't plan what you haven't read — examine the code first
Context References
- Check CLAUDE.md and
.claude/skills/for project conventions
Tip: Use the plan agent to both plan AND execute. This command is for when you only need the plan.
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.
- 1mo ago First seen · 36 lines · 9 tokens per session scan A f431d7f7c7aa
dev-docs is a command published in the GitHub repository aspenkit/aspens (102 stars, last pushed 1mo ago), licensed MIT. It adds 9 tokens to every session and 314 once invoked, about $0.0000 per session on Opus 5.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-30.
Other commands, from other repositories
generate
Reverse-engineer canonical documentation from existing codebase.
guard
Run the full quality gate with severity triage and actionable remediation.
fix
Fix documentation drift — mechanical (no AI) or AI-driven research, depending on the issue.
anchors
List what each requirement tag anchors to (read-only).
trace
Generate requirements traceability matrix.
complete
Review implementation evidence and plan the spec completion transaction.