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 dean0x/devflow --skill documentationgit clone --depth 1 https://github.com/dean0x/devflowWrote 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/dean0x/devflow/documentation)<a href="https://agentmods.dev/skills/dean0x/devflow/documentation"><img src="https://agentmods.dev/badge/skills/dean0x/devflow/documentation/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/dean0x/devflow/documentation"><img src="https://agentmods.dev/badge/skills/dean0x/devflow/documentation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00016 | $0.01050 |
| Opus 5.5 | $0.00006 | $0.00420 |
| Sonnet 5.5 | $0.00003 | $0.00210 |
| Haiku 4.5 | $0.00002 | $0.00105 |
Grade A, and why
documentation 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 7d 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Patterns
Domain expertise for documentation quality and alignment. Use alongside devflow:review-methodology for complete documentation reviews.
Iron Law
DOCUMENTATION MUST MATCH REALITY
Outdated documentation is worse than no documentation. It actively misleads. Every code change that affects behavior requires a documentation check. Comments that explain "what" instead of "why" are noise. The best documentation is code that doesn't need documentation.
Documentation Categories
1. Code Documentation Issues
| Issue | Problem | Fix |
|---|---|---|
| Missing docstrings | Complex functions without explanation | Add JSDoc with params, returns, throws |
| Outdated comments | Comments that contradict code | Update or remove |
| "What" comments | // Loop through users |
Explain "why" instead |
| Magic algorithms | Complex logic without explanation | Document algorithm and rationale |
| Transition residue | "We no longer do X" notes, in-file changelogs, or refs to removed code/sections | Remove — git holds the history |
Brief Example - Missing vs. Complete:
// BAD: No documentation on complex function
export function calculateProratedAmount(plan: Plan, startDate: Date, endDate: Date): number;
// GOOD: Purpose, params, returns, edge cases documented
/**
* Calculates prorated billing amount when switching plans mid-cycle.
* @param plan - The new plan to prorate to
* @returns Prorated amount in cents (can be negative for downgrades)
*/
export function calculateProratedAmount(plan: Plan, startDate: Date, endDate: Date): number;
2. API Documentation Issues
| Issue | Problem | Fix |
|---|---|---|
| Missing params | Callers don't know valid values | Document all params with types and constraints |
| Missing returns | Return shape unknown | Describe return structure and units |
| Missing errors | Callers don't know what to catch | List all thrown error types |
Brief Example - Incomplete vs. Complete:
// BAD: No params, no errors documented
/** Creates a subscription. */
async function createSubscription(userId: string, planId: string): Promise<Subscription>;
// GOOD: Full contract documented
/**
* @param userId - User's unique identifier
* @param planId - Plan ID from /plans endpoint
* @throws {UserNotFoundError} If userId doesn't exist
* @throws {PlanNotFoundError} If planId doesn't exist
*/
async function createSubscription(userId: string, planId: string): Promise<Subscription>;
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 7d ago Changed · -5 tokens per session 5b00c4a9f4da
- 1mo ago First seen · 127 lines · 21 tokens per session scan A 3b52c97746d9
documentation is a skill published in the GitHub repository dean0x/devflow (20 stars, last pushed today), licensed MIT. It adds 16 tokens to every session and 1,050 once invoked, about $0.0001 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 skills, from other repositories
argot-suggest-rules
Turn a convention argot has already discovered into a scripted custom rule. Runs argot conventions, surfaces the repo's mined placement conventions (where a kind of code lives — "validation in schema files", "DB access only in migrations", "business logic in the service layer, not views") and internal-API vocabulary…
software-design-patterns-and-refactoring
Use when architecture or backend work needs pre-code structural guidance from design patterns, or post-code cleanup guidance from refactoring and code-smell-driven improvement.
api-contract-audit
Static OpenAPI contract audit - endpoint drift (spec vs code), schema drift, status-code mismatch, breaking-change detection vs previous spec version, versioning consistency, security scheme alignment, deprecation markers, Richardson Maturity L0-L3 scoring. Framework auto-gen for FastAPI, NestJS…
microservices-architecture
Guides service boundary analysis, communication pattern selection, data consistency design, API contract strategy, and resilience checklist for microservices systems. Complements the microservices fragment. Invoked when the user asks to design a microservices system, split a monolith, or review service boundaries.
gate-design
Review technical design documents for API contracts, data models, component architecture, and technology decisions.
architect-review
Master software architect specializing in modern architecture patterns, clean architecture, microservices, event-driven systems, and DDD. Reviews system designs and code changes for architectural integrity, scalability, and maintainability. Use PROACTIVELY for architectural decisions.