Borrowing it
Nothing to install: this file belongs to jeeftor/audiobook-organizer. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/jeeftor/audiobook-organizer/master/.agents/skills/abo-issue-closeout/SKILL.mdgit clone --depth 1 https://github.com/jeeftor/audiobook-organizerWrote 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/jeeftor/audiobook-organizer/abo-issue-closeout)<a href="https://agentmods.dev/skills/jeeftor/audiobook-organizer/abo-issue-closeout"><img src="https://agentmods.dev/badge/skills/jeeftor/audiobook-organizer/abo-issue-closeout/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/jeeftor/audiobook-organizer/abo-issue-closeout"><img src="https://agentmods.dev/badge/skills/jeeftor/audiobook-organizer/abo-issue-closeout.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.00023 | $0.00630 |
| Opus 5.5 | $0.00009 | $0.00252 |
| Sonnet 5.5 | $0.00005 | $0.00126 |
| Haiku 4.5 | $0.00002 | $0.00063 |
Grade A, and why
abo-issue-closeout 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 2mo 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 — 31 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ABO Issue Closeout
You are the Audiobook Organizer issue closeout engineer.
Read AGENTS.md, references/abo-assistant/common.md, references/abo-assistant/testing.md, and references/abo-assistant/pr.md.
Workflow
- Run
$abo-issue-verifylogic first: issue criteria, branch diff, tests, docs, changelog, and ABS matrix. - Before adding missing files, confirm
git status --short --branchshows the dedicated non-masterissue branch. - Add missing
CHANGELOG.md, docs, ortest/abs/test-matrix.mdupdates when required. For functionality or workflow changes, missing docs include the relevantREADME.mdoverview, static docs site page underweb/src/content/docs/, and mirrored rootdocs/page when present. - Confirm real E2E acceptance evidence for user-facing workflow changes; do not close on mocked/stubbed tests alone unless the maintainer explicitly accepted and the issue comment documents the gap.
- Classify the issue as maintainer-created, user-originated, or unclear using
references/abo-assistant/common.md. - For user-originated or unclear issues, do not auto-close when reporter confirmation or manual interaction is needed. Comment with what changed, tests run, the expected reporter validation, and the next action; close only after reporter confirmation, explicit maintainer approval, obsolescence, or duplication is documented.
- Comment on the issue with what changed, tests run, and any follow-up work.
- If a PR will close the issue and closeout is allowed, ensure the PR body uses
Resolves #<issue>and do not manually close it. For user-originated issues that need reporter confirmation, avoid closing keywords until confirmation or maintainer approval is documented. - Treat the issue as open until the resolving PR is ready, required checks pass, auto-merge is enabled or the PR has merged back into
master, and the linked issue has closed or the reporter-confirmation block is documented. - After merge, confirm the linked issue closed when closure was intended and the feature branch or worktree was cleaned up. Repository delete-branch-on-merge should remove the remote branch, but verify it.
- Directly close only when the user explicitly asks, the issue is duplicate/obsolete, the work intentionally completed without a PR, or reporter confirmation/maintainer approval is documented.
- If closing directly, include the reason and verification summary in the closing comment.
- After issue closeout, follow
references/abo-assistant/common.mdnext-work recommendation guidance and tell the user the best next item to pick. Do not start the next item unless the user asks.
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.
- 2mo ago First seen · 31 lines · 23 tokens per session scan A ffdf59afb597
abo-issue-closeout is a skill published in the GitHub repository jeeftor/audiobook-organizer (196 stars, last pushed 1mo ago), licensed MIT. It adds 23 tokens to every session and 630 once invoked, about $0.0001 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-08-30.
Other skills, from other repositories
octo-matter
Matter (todo/task) domain — CRUD, status transitions, assignees, channels, timeline, and AI extract from chat messages. Load after octo-shared.
machinist
Use Machinist to create, assign, and monitor software tasks. Use when a coding agent needs to work with Machinist, its GitHub issue workflow, intake labels, direct runs, or managed queue.
pad
Work with the user's Pad workspaces through the Pad tools. Find, read, create and update tasks, bugs, ideas, plans and docs; comment on them, link them, and see what to work on next. Use it whenever the user talks about their Pad projects or items.
adr-workflow
Write, update or supersede an Architecture Decision Record (MADR). Load when a change picks one design among credible alternatives, sets a rule tooling or reviewers enforce, reverses an earlier ADR, or when asked to document a decision.
start-ticket
Creates the git branch for a ticket. Use when the user starts a ticket and gives its key and a short slug.
weekly-digest
Compiles the week's merged PRs and emails them to the team. Use on Friday afternoons.