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.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)<a href="https://agentmods.dev/commands/wislertt/bakefile/dev-docs"><img src="https://agentmods.dev/badge/commands/wislertt/bakefile/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/wislertt/bakefile/dev-docs"><img src="https://agentmods.dev/badge/commands/wislertt/bakefile/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.00672 |
| Opus 5.5 | $0.00004 | $0.00269 |
| Sonnet 5.5 | $0.00002 | $0.00134 |
| Haiku 4.5 | $0.00001 | $0.00067 |
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 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an elite strategic planning specialist. Create a comprehensive, actionable plan for: $ARGUMENTS
Instructions
-
Analyze the request and determine the scope of planning needed
-
Examine relevant files in the codebase to understand current state
-
Create a structured plan with:
- Executive Summary
- Current State Analysis
- Proposed Future State
- Implementation Phases (broken into sections)
- Detailed Tasks (actionable items with clear acceptance criteria)
- Risk Assessment and Mitigation Strategies
- Success Metrics
- Required Resources and Dependencies
- Timeline Estimates
-
Task Breakdown Structure:
- Each major section represents a phase or component
- Number and prioritize tasks within sections
- Include clear acceptance criteria for each task
- Specify dependencies between tasks
- Estimate effort levels (S/M/L/XL)
-
Create task management structure:
- Follow the dev docs pattern (see
.dev/README.mdfor complete documentation) - Create directory:
.dev/active/[xx-task-name]/(relative to project root)xx= Incremental number (01, 02, 03, ...)task-name= Concise descriptive name in kebab-case
- IMPORTANT: Check both
.dev/active/and.dev/archive/to assign a task number that doesn't duplicate any existing tasks - Generate three files:
plan.md- The comprehensive plancontext.md- Key files, decisions, dependenciestasks.md- Checklist format for tracking progress
- Include "Last Updated: YYYY-MM-DD" in each file
- Follow the dev docs pattern (see
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.
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 · 72 lines · 9 tokens per session scan A cfb5d8c18dee
dev-docs is a command published in the GitHub repository wislertt/bakefile (7 stars, last pushed yesterday), licensed Apache-2.0. It adds 9 tokens to every session and 672 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.