Borrowing it
Nothing to install: this file belongs to wislertt/bakefile. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/wislertt/bakefile/main/.claude/commands/dev-docs-update.mdgit clone --depth 1 https://github.com/wislertt/bakefileWrote 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/wislertt/bakefile/dev-docs-update)<a href="https://agentmods.dev/commands/wislertt/bakefile/dev-docs-update"><img src="https://agentmods.dev/badge/commands/wislertt/bakefile/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/wislertt/bakefile/dev-docs-update"><img src="https://agentmods.dev/badge/commands/wislertt/bakefile/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.00486 |
| Opus 5.5 | $0.00003 | $0.00194 |
| Sonnet 5.5 | $0.00001 | $0.00097 |
| Haiku 4.5 | $0.00001 | $0.00049 |
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 2mo 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
We're approaching context limits. Please update the development documentation to ensure seamless continuation after context reset.
Dev Docs Pattern
This command uses the dev docs pattern for persistent task management.
Key concepts:
.dev/active/- Work in progress.dev/archive/- Completed tasks (move here when done)- Three-file structure: plan, context, tasks
- Update
context.mdfrequently during session - Use
/dev-docs-updatebefore context reset
See .dev/README.md for complete documentation on the dev docs pattern.
Required Updates
1. Update Active Task Documentation
For each task in /.dev/active/:
-
Update
[task-name]-context.mdwith:- Current implementation state
- Key decisions made this session
- Files modified and why
- Any blockers or issues discovered
- Next immediate steps
- Last Updated timestamp
-
Update
[task-name]-tasks.mdwith:- Mark completed tasks as ✅
- Add any new tasks discovered
- Update in-progress tasks with current status
- Reorder priorities if needed
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
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.
- 2mo ago First seen · 78 lines · 7 tokens per session scan A a53f56f13cad
dev-docs-update is a command published in the GitHub repository wislertt/bakefile (7 stars, last pushed yesterday), licensed Apache-2.0. It adds 7 tokens to every session and 486 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-31.
Other commands, from other repositories
memorywhale-recall
Explicitly inspect scoped MemoryWhale evidence without executing historical commands or saving notes.
memorywhale-check
Explicitly check the reviewed MemoryWhale MCP connection; this does not enable capture or write memory.
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
modernize-transform
Transform one legacy module to the target stack — idiomatic rewrite with behavior-equivalence tests.
amp-register
Register your agent with an external AMP provider for cross-provider messaging.
speckit.spec-stats.open
On-demand view of everything not complete: what stage each is stuck at, what the immediate next artifact/command is, oldest-untouched first, stale warnings past staleafterdays.