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/evolvehq/docflow/add-conventionnpx skills add EvolveHQ/docflow --skill add-conventiongit clone --depth 1 https://github.com/EvolveHQ/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.00150 | $0.01310 |
| Opus 5 | $0.00075 | $0.00655 |
| Sonnet 5 | $0.00030 | $0.00262 |
| Haiku 4.5 | $0.00015 | $0.00131 |
Grade A, and why
add-convention 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 3d 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
add-convention
Add a convention — but only after assessing whether it should exist and where it belongs. This skill is a gatekeeper and a router, not a stenographer.
Step 0 — Preconditions and context
- Confirm the repo is bootstrapped.
- Read
CONVENTIONS.mdandAGENTS.mdin full so you can detect overlap with existing rules and judge fit.
Step 0.5 — Assessment (run first)
Run the shared assessment protocol; the triage (Step 1) and routing (Step 2) questions are asked under it:
-
Depth selector first. Ask how deep this assessment should go: express — every choice takes its recommended default; only questions with no derivable default (the free-text essentials) are still asked; guided — only the questions marked high-impact below, plus the free-text essentials; full — every question below. If the repo's
CONVENTIONS.mdrecords anAssessment depth:, pre-select it as the recommended option — the selector always appears; a recorded depth is never applied silently. Otherwise recommend full when the request arrived with little or no context and express when it is already fully specified. At any question the operator may answer "defaults from here" or "go deeper"; honour the switch immediately. -
Ask questions one at a time, each with a recommended option and a one-line reason; wait for each answer.
-
Use structured selection (single- or multiple-choice). If the host exposes a structured single-/multi-select question tool, use it and mark the recommended option; otherwise list options A/B/C in plain text and name the recommended one. Use free text only where an enumerable set is impossible (e.g. the exact wording).
-
The operator decides. Never proceed past a question without an answer, and never guess scope when invoked with no context.
Questions (skip any the request already answers):
- Worth codifying? — yes (recurring, stable, testable) or no (one-off, duplicate, churn-prone, vague). Recommended: per the Step 1 triage; this question gates the rest. (High-impact — asked in guided.)
- Home —
AGENTS.mdhard rule /CONVENTIONS.mdguidance /GLOSSARY.mdterm / actually a decision (hand off to the new-adr skill). Recommended: per the rule's nature (see Step 2). (High-impact — asked in guided: the wrong home is churn to move.) - Enforce in the verify gate? — yes / no. Recommended: no, unless the rule is mechanically checkable.
- Wording — free text (the rule statement itself; asked at every depth).
What ships with it
1 file 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.
- 3d ago First seen · 106 lines · 150 tokens per session scan A 0383027112ce
add-convention is a skill published in the GitHub repository EvolveHQ/docflow (11 stars, last pushed 28d ago), licensed MIT. It adds 150 tokens to every session and 1,310 once invoked, about $0.0007 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-31.
Other skills, from other repositories
adr-integration
This skill should be used when the user asks about "ADR integration", "ADR CI/CD", "ADR tooling", "ADR automation", "export ADRs", "ADR documentation site", or needs guidance on integrating ADRs with CI/CD, documentation sites, and other tools.
adr-format-structured-madr
This skill should be used when the user asks about "structured MADR", "structured-madr", "frontmatter ADR", "comprehensive ADR", "auditable ADR", or needs guidance on creating ADRs using the Structured MADR format with YAML frontmatter and audit sections.
adr-decision-drivers
This skill should be used when the user asks about "decision drivers", "architectural forces", "quality attributes", "how to identify trade-offs", "non-functional requirements for ADRs", or needs help identifying, documenting, and weighing the forces that influence architectural decisions.
adr-format-madr
This skill should be used when the user asks about "MADR format", "MADR template", "Markdown Architectural Decision Records", "MADR 4.0", "MADR sections", or needs guidance on creating ADRs using the MADR (Markdown Architectural Decision Records) format.
adr-fundamentals
This skill should be used when the user asks "what is an ADR", "when should I create an ADR", "ADR best practices", "architecture decision records", "ADR lifecycle", "how to document architecture decisions", or needs guidance on ADR fundamentals, when to create ADRs, or ADR lifecycle management.
adr-quality
This skill should be used when the user asks about "ADR quality", "review ADR", "ADR checklist", "improve ADR", "ADR validation", "good ADR examples", or needs guidance on evaluating, improving, and maintaining high-quality architectural decision records.