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 close-donegit 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/close-done)<a href="https://agentmods.dev/skills/outlinedriven/outline-driven-development/close-done"><img src="https://agentmods.dev/badge/skills/outlinedriven/outline-driven-development/close-done.svg" alt="Measured on agentmods" 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.00037 | $0.00810 |
| Opus 5 | $0.00018 | $0.00405 |
| Sonnet 5 | $0.00007 | $0.00162 |
| Haiku 4.5 | $0.00004 | $0.00081 |
Grade A, and why
close-done 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- close-done — 91% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Close done
Contract
| Field | Bound contract |
|---|---|
| Trigger | User wants to batch-close resolved or outdated tracker items. |
| Authority | Read-only. No file, VCS, credential, paid, published, deployed, or remote mutation. The agent fetches, classifies, and presents the batch; the user performs every remote closure. |
| Side effect | A prepared batch list presented to the user. No tracker item is mutated by this skill. |
| Done | A prepared batch list is presented to the user for manual closure, with each item classified as resolved or outdated and backed by evidence. |
Inputs
- The candidate tracker items, supplied as numbers, URLs, a filter, or a query the agent can resolve against the configured tracker.
- Optional: a reason or resolution note the user will attach when closing.
- Tracker host and credentials are those already configured in the environment; the agent does not create or modify credentials.
Classification criteria
An item qualifies for the batch only when it meets one of these evidence-backed criteria:
- Resolved: the item's tracker state is closed-done or merged, or the item references a merged pull request, commit, or deployment that addresses it. Evidence: the tracker state field, a linked PR/commit with a merged status, or a resolution comment from the assignee.
- Outdated: the item has had no activity for a period the user defines (default 90 days), and no open PR or branch references it. Evidence: the last-activity timestamp and the absence of linked open work.
Items that do not meet either criterion are excluded. List each excluded item with the reason it failed the criteria.
Procedure
- Resolve the supplied references or filter against the tracker read-only and fetch each item's number, title, current state, last activity timestamp, and linked PRs or branches. Done when: every supplied item is resolved with its metadata or the failing item is named.
- Classify each item as resolved or outdated using the criteria above. Drop items that are neither and list them as excluded with the reason. Done when: every item has a classification with its evidence or an exclusion reason.
- Prepare the final batch list: every item proposed for close with its number, title, current state, classification (resolved or outdated), and the evidence supporting it. Done when: the full batch is listed and no mutation has occurred.
- Present the batch to the user for manual closure. State that the agent will not close any item and that the user must perform the closure on the tracker. Include the optional resolution note for the user to attach. Done when: the batch is presented and the user has the closure instructions.
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.
- 2d ago Changed · -24 tokens per session bd5cb120b531
- 4d ago First seen · 51 lines · 61 tokens per session scan A 7864bfed71e5
close-done is a skill published in the GitHub repository OutlineDriven/outline-driven-development (52 stars, last pushed 2d ago), licensed Apache-2.0. It adds 37 tokens to every session and 810 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
drift-detect
Use when the user says "plan drift", asks whether the roadmap, plans, or docs still match the code, or is deciding what to rebuild when restarting a stalled project. For doc-vs-code drift inside a specific diff, use sync-docs.
github-backlog-triage
Use when the user invokes backlog triage for a GitHub repo's open issues and PRs. Not for proactive triage, non-GitHub trackers, or single bug issues: use github-bug-report-triage.
setup-repo-skills
Use when the user wants one-time repository setup for tracker, triage labels, and domain conventions. Not for ongoing triage, issue creation, or multi-repo setup.
git-history-analysis
Use when the user asks about recent engineering work, what the team is working on, planning or roadmap material, or an explicitly requested Slack summary. Not for remote or irreversible changes.
graph-backbone
Use when defining, revising, or gate-replanning the project structural backbone in project-root graph.yaml; produces a validated approved revision preserving immutable topology and additive metadata. Not for remote, credential, publish, deploy, or irreversible changes.
wontfix
Use when the user wants to elicit refused directions, generalize them, and close matching tracker items as not planned. Not for duplicates, spam, or items closed as completed or obsolete.