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 docs-frameworkgit 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/docs-framework)<a href="https://agentmods.dev/skills/dean0x/devflow/docs-framework"><img src="https://agentmods.dev/badge/skills/dean0x/devflow/docs-framework/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/docs-framework"><img src="https://agentmods.dev/badge/skills/dean0x/devflow/docs-framework.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.00020 | $0.03045 |
| Opus 5.5 | $0.00008 | $0.01218 |
| Sonnet 5.5 | $0.00004 | $0.00609 |
| Haiku 4.5 | $0.00002 | $0.00304 |
Grade A, and why
docs-framework 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 2d 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 — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Framework
The canonical source for what Devflow names under .devflow/docs/. A command that writes or looks up a doc path follows it, and the one place a command differs is stated here as an exception, never left implicit.
Iron Law
ALL ARTIFACTS FOLLOW NAMING CONVENTIONS
A run directory is
YYYY-MM-DD_HHMMin local time; a second run in the same minute takes seconds (YYYY-MM-DD_HHMMSS). Branch slugs replace/with-. Topic slugs are lowercase alphanumeric with single dashes, at most 50 characters. The exceptions are the ones listed under Naming Conventions, and no others. Inconsistent naming breaks tooling, searching, and automation. Follow the pattern or fix the pattern for everyone.
Directory Structure
All generated documentation lives under .devflow/docs/ at the checkout's toplevel:
.devflow/docs/
├── reviews/{branch-slug}/ # /code-review, per branch
│ ├── .last-review-head # HEAD SHA of the last completed review (incremental)
│ └── {timestamp}/ # one directory per review
│ ├── {focus}.md # Review agent report (security.md, architecture.md, ...)
│ ├── review-summary.md # Synthesize agent output
│ ├── resolution-summary.md # /resolve
│ ├── evidence.md # /resolve: appended test-plan claims
│ └── stale-plan.md # /resolve: stale test-plan lines
├── bug-analysis/{branch-slug}/ # /bug-analysis, per branch
│ ├── .last-analysis-head # HEAD SHA of the last analysis (incremental)
│ └── {timestamp}/
│ ├── {focus}.md # Debug agent report
│ ├── static-findings.md # Raw static analysis tool output
│ ├── bug-analysis-summary.md # Synthesize agent output
│ └── resolution-summary.md # /resolve (evidence.md and stale-plan.md as in reviews)
├── research/{topic-slug}/{timestamp}/ # /research
│ ├── {type}.md # Research agent output (codebase.md, external.md, ...)
│ └── research-summary.md # Synthesize agent output
├── design/
│ ├── {ISSUE_ID}-{topic-slug}.{timestamp}.md # /plan, one issue
│ ├── multi-{topic-slug}.{timestamp}.md # /plan, several issues (frontmatter issue: pending)
│ ├── {topic-slug}.{timestamp}.md # /plan, no issue
│ └── {slug}/{timestamp}/ # /dynamic-plan run
│ ├── {ticket-slug}-plan.md # one plan per ticket
│ └── DECISIONS-NEEDED.md
├── tickets/{slug}/{timestamp}/ # /dynamic-tickets
│ ├── {ticket-slug}.md
│ └── tracking-issue.md
├── waves/{slug}/{timestamp}/wave-report.md # /dynamic-build
├── handoff-{branch-slug}.md # Code agent phase handoff; deleted once the PR exists
├── evidence-{branch-slug}.md # /implement test plan and claims; stays after the PR
└── evidence-wave-{slug}.md # /dynamic-build wave test plan and claims
.devflow/memory/
├── WORKING-MEMORY.md # Auto-maintained by Stop hook (overwritten)
└── backup.json # Pre-compact git state snapshot
.devflow/learning/
├── decisions.md # Architectural decisions (ADR-NNN format)
└── pitfalls.md # Known pitfalls (PF-NNN format)
What ships with it
2 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.
- 2d ago Changed 33fe3587d6a1
- 5d ago Changed · -3 lines 857f9347cd88
- 7d ago Changed · -52 tokens per session 8d80835fa6ee
- 10d ago Changed 74b9dad69d7b
- 16d ago Changed · -1 lines bf92058418f1
- 1mo ago Changed · +2 lines 806d48942e9f
- 1mo ago First seen · 191 lines · 72 tokens per session scan A ac657fe4c975
docs-framework is a skill published in the GitHub repository dean0x/devflow (20 stars, last pushed today), licensed MIT. It adds 20 tokens to every session and 3,045 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
find-simplifications
Use for a periodic repo-wide sweep of qwen-code for accumulated excess surface — dead components and files, orphaned locale keys, exports nothing consumes, added-then-removed scaffolding — filing candidates on a tracking issue and landing only what a maintainer has said yes to. Repo-wide and evidence-first; every…
pr-review-canvas
Create a OpenBitFun Canvas for reviewing a pull request, branch diff, or change set with Cursor-style diff cards, review maps, risk callouts, and focused reviewer flow. Use when the user asks for a PR review canvas, diff walkthrough, change-set overview, or visual review summary.
code-review
You are a senior code reviewer. You receive diffs via stdin.
include-test-files-that-assert-on-behavior-being-changed-in-decl
When delegating a task affected by this skill, include.
review
Adversarial fresh-context review and risk check of an increment before it ships; every finding cites path:line and is re-verified. Use for "review", "qa", "quality check", "critique this".
tech-debt-ci-review
Codex adapter for deep technical-debt and CI-stability audits. Use when asked to find test theater, flaky tests, missing or mis-scoped tests, brittle CI/toolchain behavior, structural debt blocking green PRs, or a remediation order for opencode-swarm.