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 OutlineDriven/outline-driven-development --skill engineering-blog-writinggit clone --depth 1 https://github.com/OutlineDriven/outline-driven-developmentWrote 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/outlinedriven/outline-driven-development/engineering-blog-writing)<a href="https://agentmods.dev/skills/outlinedriven/outline-driven-development/engineering-blog-writing"><img src="https://agentmods.dev/badge/skills/outlinedriven/outline-driven-development/engineering-blog-writing/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/outlinedriven/outline-driven-development/engineering-blog-writing"><img src="https://agentmods.dev/badge/skills/outlinedriven/outline-driven-development/engineering-blog-writing.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.00053 | $0.01592 |
| Opus 5 | $0.00026 | $0.00796 |
| Sonnet 5 | $0.00011 | $0.00318 |
| Haiku 4.5 | $0.00005 | $0.00159 |
Grade A, and why
engineering-blog-writing 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 5d 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Engineering blog writing
Contract
| Field | Bound contract |
|---|---|
| Trigger | User asks to write, review, or improve an engineering blog post, technical deep dive, product launch, postmortem, data study, or technical tutorial. |
| Authority | Reversible local write: create or edit a local markdown blog draft. Roll back by discarding the draft or reverting the file. |
| Side effect | Writes or updates a local markdown file. No external publishing, deployment, credential modification, or remote mutations. |
| Done | A complete technical blog post with a named author byline, verified performance metrics, tested code examples, labeled architecture diagrams where needed, informative headings, and an actionable conclusion. |
Inputs
- Topic, post type, and intended technical audience. Required. Post type is one of: engineering deep dive, architecture overview, product launch, postmortem, data/benchmarking study, or technical tutorial.
- Author name for the byline. Required before completing the post; reject anonymous or generic team bylines.
- Existing draft to review or edit. Optional; provide when revising existing copy.
- Supporting technical evidence: verified baseline and result metrics for performance claims, tested code snippets with dependencies and imports, and architecture topology. Required for claims in the draft.
Procedure
- Confirm post type and author byline. Map the post type to its core technical objective:
- Engineering deep dive: explain an internal architecture, algorithm, or technical decision so peers learn; byline the building engineer.
- Technical product launch: explain the underlying mechanism, why it matters, and how to use it; byline the builder, product engineer, or developer advocate.
- Postmortem: provide transparent failure analysis with a timeline, root cause, and systemic mitigations; byline engineering leadership or the incident responder.
- Data or benchmarking study: share reproducible empirical data and methodology; byline the research or engineering team lead.
- Tutorial or implementation guide: guide a developer through solving a concrete technical problem; byline the contributing engineer. Stop and request the author name if none is provided.
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.
- 5d ago First seen · 96 lines · 53 tokens per session scan A 818dbd95498f
engineering-blog-writing is a skill published in the GitHub repository OutlineDriven/outline-driven-development (52 stars, last pushed 3d ago), licensed Apache-2.0. It adds 53 tokens to every session and 1,592 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-09-03.
Other skills, from other repositories
book-to-skill
Use when the user names one book, course, paper, or source document and asks to distill it into a reusable skill. Classifies the source as procedure or reference, writes an attributed SKILL.md, and proves its routing. Not for a folder of sources — use map-corpus.
drill
Use when a concept needs practising rather than explaining: run a scaffolded exercise from worked example to independent problem, quiz the learner, run spaced recall over what they cleared, or probe for the gaps blocking what they want next. For explanation, use explain-concept; for an end-to-end build, use capstone.
writing-lean-proofs
Use when asked to design, write, review, refactor, lint, or performance-diagnose Lean 4 proofs, libraries, or tactics. Not for non-Lean code or changes outside source, API, proof, or linter scope.
scaffold-exercises
Use when a course needs numbered problem, solution, and explainer scaffolds. Creates type-specific files with non-colliding names, populates them, and validates with the course linter. Not for a CLI or Next.js project scaffold — use scaffold-cli or scaffold-nextjs.
explain-concept
Use when a concept needs making clear rather than practising: build the intuition, explain why it exists and what it replaced, trace where it came from, draw it, or contrast it against what it gets confused with. For exercises and grading, use drill.
capstone
Use when the user is ready to apply what they learned to something real: scope a project sized to what they have cleared, write the brief with milestones and a done test, then judge the finished work against it. For single-concept exercises and quizzes, use drill.