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-verify/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-verify)<a href="https://agentmods.dev/skills/jeeftor/audiobook-organizer/abo-issue-verify"><img src="https://agentmods.dev/badge/skills/jeeftor/audiobook-organizer/abo-issue-verify/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-verify"><img src="https://agentmods.dev/badge/skills/jeeftor/audiobook-organizer/abo-issue-verify.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.00035 | $0.00412 |
| Opus 5 | $0.00017 | $0.00206 |
| Sonnet 5 | $0.00007 | $0.00082 |
| Haiku 4.5 | $0.00003 | $0.00041 |
Grade A, and why
abo-issue-verify 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 10d 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.
What it actually says
ABO Issue Verify
You are the Audiobook Organizer acceptance verifier.
Read AGENTS.md, references/abo-assistant/common.md, and references/abo-assistant/testing.md.
Workflow
- Identify the issue and read its body/comments.
- Classify the issue as maintainer-created, user-originated, or unclear using
references/abo-assistant/common.md. - Extract acceptance criteria and any follow-up decisions recorded during implementation.
- Inspect the branch diff against
master. - Verify each criterion against code, tests, docs, and behavior.
- Check whether
CHANGELOG.mdis required and present. - For functionality or workflow changes, verify the docs impact check covered both
README.mdand the static docs site source underweb/src/content/docs/, plus mirroreddocs/pages when present. - Check whether
test/abs/test-matrix.mdis required and present for ABS-facing changes. - For user-facing workflow changes, verify that real E2E acceptance coverage exists and was run; classify mocked/stubbed UI or API tests as supplemental only.
- For user-originated or unclear issues, determine whether repo-native verification fully proves the fix. If reporter confirmation or manual interaction is needed, mark closeout blocked until confirmation, maintainer approval, or documented obsolescence/duplication.
- Run or confirm the narrowest relevant verification commands, widening when practical.
- Verify whether the work is only locally complete or fully closed out through a PR merge back into
master. - Report a checklist of pass/fail/blocked items and the exact remaining work.
Do not mark the issue done just because tests pass. Tie completion back to acceptance criteria and repo workflow obligations.
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.
- 10d ago First seen · 31 lines · 35 tokens per session scan A c1184ee207e1
abo-issue-verify is a skill published in the GitHub repository jeeftor/audiobook-organizer (188 stars, last pushed 1mo ago), licensed MIT. It adds 35 tokens to every session and 412 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-08-30.
Other skills, from other repositories
scaffold-dotnet-test-project
MUST USE when an existing .NET test project was excluded from a .slnf/CI solution filter, disappeared from .sln/.slnx discovery, or lost its production ProjectReference; also for requests to set up, create, reuse, add, register, include, or repair a test project. Handles "tests pass directly but CI discovers zero"…
cy-execute-task
Implement and verify an existing CompozyOS spec task, then update its tracking. Excludes review remediation.
team-qa
Orchestrate the QA team through a full testing cycle. Coordinates qa-lead (strategy + test plan) and qa-tester (test case writing + bug reporting) to produce a complete QA package for a sprint or feature. Covers: test plan generation, test case writing, smoke check gate, manual QA execution, and sign-off report.
gh-issue
Size-audit, write, and split BanyanDB issues that somebody else or an automated TDD workflow can implement. Use whenever the user asks to file or revise an issue, decide whether an issue is too large, make an issue TDD-ready, turn a design into tickets, or split an umbrella into executable leaves. Do not draft or file…
conductor-implement
Execute tasks from a track's implementation plan following TDD workflow.
08-three-amigos
Assesses an Epic or Story through one product, delivery, or quality lens, then reconciles three caller-supplied reports. Use when the user wants to refine one before a backlog change. Not for spawning or writing.