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 agentmods add skills/medadembha/docflow/checknpx skills add MedAdemBHA/docflow --skill checkgit clone --depth 1 https://github.com/MedAdemBHA/docflowWhat 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 | $0.00040 | $0.00277 |
| Opus 5 | $0.00020 | $0.00138 |
| Sonnet 5 | $0.00008 | $0.00055 |
| Haiku 4.5 | $0.00004 | $0.00028 |
Grade A, and why
check 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.
What it actually says
check
Goal: answer "is this usable and what do I do next?" in one screen.
Run
bash scripts/docflow-check.sh --target <REPO ROOT>
If running from an installed plugin where scripts are not in the target repo, use the plugin script path.
Interpret
| Status | Meaning | Next |
|---|---|---|
Ready |
DocFlow is installed and validation is clean | Start normal docs work |
Needs setup |
No meaningful docs or config detected | /docflow:init |
Needs adoption |
Existing docs need docflow infrastructure | /docflow:adopt |
Needs repair |
Generated helpers/guidance are missing or managed helpers are outdated | /docflow:repair |
Blocked |
Validation found hard errors | /docflow:validate |
Rules
- Use this before asking the user to choose a setup path.
- Keep the response short: status, reason, next command.
- Do not run mutating commands from this skill; hand off to the matching skill.
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 First seen · 33 lines · 40 tokens per session scan A 075f06d8fdcd
check is a skill published in the GitHub repository MedAdemBHA/docflow (41 stars, last pushed 18d ago), licensed MIT. It adds 40 tokens to every session and 277 once invoked, about $0.0002 per session on Opus 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
project-context
Resume, handoff, and long-running repo work by keeping durable context across threads or agents: task briefs, logs, and reusable reference notes.
codex-project-director
Invoke explicitly with $codex-project-director to act as an active, non-implementing control plane that drives multiple Codex tasks or sessions toward one verified project outcome. Use only for a user-designated director or supervisor session, not a single local task, ordinary implementation, one-off review, or status…
tighten-docs
Use by default whenever creating, revising, reviewing, or finalizing human-authored documentation whose source meaning is settled, including documentation changed within another task. Apply from first draft through final review to keep one direct current state, clear reader routes and ownership, and remove rejected…
codex-token-discipline
Use for Codex work with clear excess-cost risk: broad or unpredictable logs and diffs, browser/UI loops, subagents, repeated compaction, or explicit usage audits. Guides preflight output limits, bounded delegation, evidence reuse, and compact checkpoints. Skip routine edits, direct answers, and ordinary test runs.
interactive-state-flow
Use when an interactive flow is laggy, stale, or race-prone because user intent, source state, derived presentation, async IO, scheduling, or background work are mixed. Keep source state prompt, protect the urgent interaction path, and admit async or presentation results only through a freshness-owning boundary.
agents-md-editor
Use when creating, editing, or reviewing AGENTS.md, agents.md, CLAUDE.md, Copilot instructions, Cursor rules, or any always-read repository instruction file. Keep persistent agent instructions small, durable, non-duplicative, and action-oriented; classify content that belongs in commands, onboarding, reference docs…