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 final-graingit 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/final-grain)<a href="https://agentmods.dev/skills/outlinedriven/outline-driven-development/final-grain"><img src="https://agentmods.dev/badge/skills/outlinedriven/outline-driven-development/final-grain/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/final-grain"><img src="https://agentmods.dev/badge/skills/outlinedriven/outline-driven-development/final-grain.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.00658 |
| Opus 5.5 | $0.00021 | $0.00263 |
| Sonnet 5.5 | $0.00011 | $0.00132 |
| Haiku 4.5 | $0.00005 | $0.00066 |
Grade A, and why
final-grain 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 1mo 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- final-grain — 88% identical, 13 lines differ
How it starts
The opening of the file, as written. The whole thing — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Final grain
Contract
| Field | Bound contract |
|---|---|
| Trigger | User wants to push an already working artifact to finished composition, texture, and feel. Not for hygiene routing — use clean-and-true. |
| Authority | Reversible local writes to the named artifact only. Use its current VCS version as the rollback source. If it is not tracked, require a human-supplied recovery source before mutation. |
| Side effect | Produce a polished local artifact at the named path. No VCS, remote, credential, or paid mutation. |
| Done | The artifact exists at the named path with visible polish applied and original functionality confirmed intact. |
Inputs
- Artifact: the working file or set of files to be polished. Required; user provides the path.
- Polish targets: the specific structure, grain, or feel dimensions the human wants refined. Optional; if absent, the agent proposes three targets and the human confirms before proceeding.
Procedure
- Confirm the artifact path and that it is working as delivered. Done when: the artifact path is confirmed and the artifact is working.
- Classify the artifact type (document, code file, config, spec, report, or other). Done when: the artifact type is classified.
- Propose three polish dimensions (structural coherence, compositional refinement, and presentational polish) unless the human named them. Done when: three polish dimensions are proposed or the human's named targets are adopted.
- Obtain explicit human confirmation of the polish targets before mutating any file. Done when: the human confirms the polish targets.
- If the artifact is tracked in version control, note its current committed version as the rollback source. If it is not tracked, require the human to supply an existing recovery source before mutation; otherwise stop as blocked. Done when: the rollback source is noted or the run is blocked for lacking one.
- Apply polish to the artifact along the confirmed dimensions only. Do not change implementation correctness. Done when: polish is applied along the confirmed dimensions with implementation correctness unchanged.
- Verify the polished artifact preserves the original functionality: run a smoke test if applicable. Done when: original functionality is confirmed intact.
- Replace the original artifact with the polished version. Done when: the polished version replaces the original at the named path.
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.
- 1mo ago First seen · 40 lines · 53 tokens per session scan A f3730909aca8
final-grain is a skill published in the GitHub repository OutlineDriven/outline-driven-development (54 stars, last pushed 26d ago), licensed Apache-2.0. It adds 53 tokens to every session and 658 once invoked, about $0.0002 per session on Opus 5.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
audit-project
Run an iterative multi-agent code audit until critical and high findings are resolved. Use when the user says "audit my code", "find all the bugs", "deep code audit", "iterative review", or "review until clean".
duet
Use when the user invokes /duet, says "pair with me", or faces aesthetic, architectural, or irreversible decisions.
goal-prompt-drafting
Use when asked to draft copy-ready /goal objectives for long-running agents; returns one normalized one-line objective with measurable end state, grounded proof, easy-out invariants, a stop clause, and a Missing list. Not for source or remote-system changes.
handoff-prompt
Use when the user asks for a handoff, delegation, or clipboard-ready prompt for another agent: a standalone path-free prompt copied to the clipboard, confirmed by title. Not for session-snapshot briefs — use handoff; never remote, credential, publish, deploy, or irreversible.
publish-branch
Use when asked to publish the checked-out branch: commit and push it on whatever branch it is, the default branch included. Not for creating branches, PRs, force pushes, or pushing any other branch; when the request excludes the default branch, use commit-push-current.
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.