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/authornpx skills add MedAdemBHA/docflow --skill authorgit 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.00051 | $0.01825 |
| Opus 5 | $0.00026 | $0.00912 |
| Sonnet 5 | $0.00010 | $0.00365 |
| Haiku 4.5 | $0.00005 | $0.00183 |
Grade A, and why
author 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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
author
Author docs the docflow way: choose category → apply naming → fill template → cross-link. Companion of router (read side) and changelog (history). Templates live in the plugin's templates/ dir; /docflow:init drops them into a repo.
A doc's filename should tell a teammate what + when without opening it. If it can't, rename.
Writing style (enforce on every doc)
Direct, tech + business. No filler.
- Tables and bullets over paragraphs. One claim per line.
- Lead with the outcome/decision; cut "this document describes…", "in order to", "it is important to note".
- Concrete: names, paths, numbers, commit hashes. No adjectives that carry no info.
- Each section earns its place — if a placeholder stays empty, delete the section.
- Max one short intro line per doc; the structure does the rest.
1 — Pick the category (what is this doc?)
| The doc answers… | Category | Folder |
|---|---|---|
| WHAT a feature does (user-facing) | product spec | product-spec/ |
| HOW it's built (data flow, API contract, lifecycle) | technical spec | specs/ |
| WHY we chose an approach | decision (ADR) | decisions/ |
| HOW to do X / a convention / cheat sheet | reference | references/ |
| WHAT's planned / status / roadmap | plan | plans/ (features/, hygiene/, upcoming/) |
| Current quality / known bugs / audit | review | reviews/ (active/, archive/, bugs/) |
| WHAT shipped, by month | changelog | changelog/ — see changelog |
One doc, one category. If it spans two, it's two docs that cross-link.
2 — Apply the naming pattern
| Folder | Pattern | Example |
|---|---|---|
product-spec/ |
NN-topic.md (stable, reading order) |
04-jobs.md |
specs/ |
(mmm-yy)-topic.md (dated snapshot) |
(apr-26)-tab-system-workflow.md |
references/ |
topic.md (stable) |
newtable-component.md |
decisions/ |
NNNN-title.md (monotonic, never reused) |
0001-url-as-state.md |
plans/features/ |
(mmm-yy)-feature-name.md |
(apr-26)-create-job-stepper.md |
plans/hygiene/ |
(mmm-yy)-topic.md |
(apr-26)-codebase-cleanup.md |
plans/upcoming/ |
rolling roadmap, no dates | critical.md, now.md, next.md, later.md |
reviews/active/,archive/ |
(mmm-yy)-topic.md |
(may-26)-tab-system.md |
changelog/ |
(mmm-yy).md |
(may-26).md |
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 · 129 lines · 51 tokens per session scan A 4910a175b74c
author is a skill published in the GitHub repository MedAdemBHA/docflow (41 stars, last pushed 18d ago), licensed MIT. It adds 51 tokens to every session and 1,825 once invoked, about $0.0003 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…