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-update)<a href="https://agentmods.dev/commands/aspenkit/aspens/dev-docs-update"><img src="https://agentmods.dev/badge/commands/aspenkit/aspens/dev-docs-update/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-update"><img src="https://agentmods.dev/badge/commands/aspenkit/aspens/dev-docs-update.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.00007 | $0.00352 |
| Opus 5.5 | $0.00003 | $0.00141 |
| Sonnet 5.5 | $0.00001 | $0.00070 |
| Haiku 4.5 | $0.00001 | $0.00035 |
Grade A, and why
dev-docs-update 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
We're approaching context limits. Please update the development documentation to ensure seamless continuation after context reset.
Required Updates
1. Update Active Task Plans
For each task in /dev/active/<task-name>/:
- Update
<task-name>/plan.mdwith:- Mark completed tasks as checked (
[x]) - Add any new tasks discovered during this session
- Log key decisions in the Decisions section
- Note current implementation state and next steps
- Update any blockers or issues discovered
- Mark completed tasks as checked (
2. Capture Session Context
Include any relevant information about:
- Complex problems solved
- Architectural decisions made
- Tricky bugs found and fixed
- Integration points discovered
- Testing approaches used
- Performance optimizations made
3. Update Memory (if applicable)
- Store any new patterns or solutions in project memory/documentation
- Update entity relationships discovered
- Add observations about system behavior
4. Document Unfinished Work
- What was being worked on when context limit approached
- Exact state of any partially completed features
- Commands that need to be run on restart
- Any temporary workarounds that need permanent fixes
5. Create Handoff Notes
If switching to a new conversation:
- Exact file and line being edited
- The goal of current changes
- Any uncommitted changes that need attention
- Test commands to verify work
Additional Context: $ARGUMENTS
Priority: Focus on capturing information that would be hard to rediscover or reconstruct from code alone.
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 · 48 lines · 7 tokens per session scan A 8967cdd314fd
dev-docs-update is a command published in the GitHub repository aspenkit/aspens (102 stars, last pushed 1mo ago), licensed MIT. It adds 7 tokens to every session and 352 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.