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 risadams/ink-and-agency --skill documentation-engineergit clone --depth 1 https://github.com/risadams/ink-and-agencyWrote 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/risadams/ink-and-agency/documentation-engineer)<a href="https://agentmods.dev/skills/risadams/ink-and-agency/documentation-engineer"><img src="https://agentmods.dev/badge/skills/risadams/ink-and-agency/documentation-engineer/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/risadams/ink-and-agency/documentation-engineer"><img src="https://agentmods.dev/badge/skills/risadams/ink-and-agency/documentation-engineer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00037 | $0.00699 |
| Opus 5 | $0.00018 | $0.00349 |
| Sonnet 5 | $0.00007 | $0.00140 |
| Haiku 4.5 | $0.00004 | $0.00070 |
Grade A, and why
documentation-engineer 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 6d 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 6d ago First seen · 82 lines · 37 tokens per session scan A fc1b2b24ab97
documentation-engineer is a skill published in the GitHub repository risadams/ink-and-agency (2 stars, last pushed 1mo ago), with no licence file. It adds 37 tokens to every session and 699 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-09-03.
Other skills, from other repositories
forward-derivation
Derive BDD scenarios and TDD test skeletons from approved SDD specifications. ATDD acceptance test tables are optional output for specialized needs. Use when: spec is approved, starting BDD/TDD implementation, generating test structures. Keywords: forward derivation, spec to test, BDD generation, TDD skeleton, test…
atdd-assistant
A guide to Acceptance Test-Driven Development, or ATDD, a process where a team agrees on user-story requirements and acceptance tests before coding. Acceptance tests check whether a feature meets the agreed business requirements.
checkin-assistant
A checklist for the steps before making a Git commit. It treats a commit as one complete, reversible unit of work that should leave the codebase working.
documentation-guide
A guide for organizing project documentation such as README files, architecture notes, API references, and deployment instructions. It covers what different kinds of projects should document.
refactoring-assistant
A guide for deciding how to improve existing code, including when to refactor it gradually or replace it with a rewrite. Refactoring changes code structure without changing what it is meant to do.
reverse-engineer
A guide for examining existing software and turning what it does into specification documents. Specification-driven development means writing an agreed description of a system before changing it.