Borrowing it
Nothing to install: this file belongs to Brad-Edwards/aptl. 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/Brad-Edwards/aptl/main/.claude/skills/wave-issue-coverage/SKILL.mdgit clone --depth 1 https://github.com/Brad-Edwards/aptlWrote 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/brad-edwards/aptl/wave-issue-coverage)<a href="https://agentmods.dev/skills/brad-edwards/aptl/wave-issue-coverage"><img src="https://agentmods.dev/badge/skills/brad-edwards/aptl/wave-issue-coverage/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/brad-edwards/aptl/wave-issue-coverage"><img src="https://agentmods.dev/badge/skills/brad-edwards/aptl/wave-issue-coverage.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.00072 | $0.01778 |
| Opus 5.5 | $0.00029 | $0.00711 |
| Sonnet 5.5 | $0.00014 | $0.00356 |
| Haiku 4.5 | $0.00007 | $0.00178 |
Grade A, and why
wave-issue-coverage 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Wave Issue Coverage
Back-fill GitHub issue coverage for DRAFT Ground Control requirements in a given wave.
Inputs
- wave: integer wave number (e.g.
1,2,3) OR the literal stringallall→ process every wave that has DRAFT requirements, smallest wave first
Preconditions
- Read
.ground-control.yamlat the repo root viagc_get_repo_ground_control_contextto obtain:project— Ground Control project identifiergithub_repo—owner/repoforghcalls These values are passed to every MCP andghcall in this workflow. Do not hard-code them.
- The GC MCP server (
mcp__ground-control__*) must be available. gh auth statusmust be authenticated with write access togithub_repo.
Workflow
1. Resolve the requirement list
Call gc_list_requirements with project=<project>, status=DRAFT, size=200, and:
wave=<N>if a single wave was given, OR- no
wavefilter ifallwas given (then group results by wave and process oldest wave first).
Capture the full list of (uid, id, title, requirement_type, priority, wave) tuples. This is the work list.
2. Choose progress tracker
Pick based on the size of the work list:
| Count | Tracker |
|---|---|
| ≤ 25 | TaskCreate — one task per requirement, processed in order |
| > 25 | A temp file at /tmp/wave-issue-coverage-<wave>-<timestamp>.md with a checkbox per requirement; update inline as each completes |
For the temp-file path, use a single in-progress TaskCreate task ("Process wave N coverage — see temp file") so the user still sees forward motion in their TaskList.
3. Process sequentially — DO NOT parallelize
For each requirement, in order:
-
Check existing GC traceability
gc_get_traceabilitywith the requirement UUID. Note any existingGITHUB_ISSUEartifact links. -
Search GitHub for the UID
gh issue list --repo <github_repo> --state all --search "<UID> in:title,body" --json number,title,state -
Search GitHub for topic overlap (only if no UID match) Run a small number of focused keyword searches drawn from the requirement title/statement. The goal is to catch issues that pre-date the UID convention or were filed under a different name. Pick the strongest 1–3 keywords; do not flood with searches.
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 · 120 lines · 72 tokens per session scan A 631405ab2526
wave-issue-coverage is a skill published in the GitHub repository Brad-Edwards/aptl (25 stars, last pushed 24d ago), licensed MIT. It adds 72 tokens to every session and 1,778 once invoked, about $0.0003 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
pipeline-conductor
Operating procedure for the kirocrew-pipeline-conductor agent. Use when a pipeline conductor session is seeded, inspected or debugged. You MANAGE one issue/PR pipeline on one repo: two columns per item (session working? item solved?), send intent, never re-derive a red yourself.
github
Drive GitHub via the official gh CLI — repos, issues, pull requests, releases, gists, Actions runs, and raw REST through gh api. Use when the user asks to inspect or manage GitHub.
orchestrate
Toolbox for driving HumanLayer from the CLI - log in, pick a host, launch tasks in their own worktrees, launch sessions, list tasks and their PRs, and copy, move, or upload task artifacts.
create-milestone
Create a GitHub milestone for an upcoming release. Suggests the next version based on the latest release, gathers all merged PRs and closed issues since that release, presents a draft with two tables (Issues and PRs) for user approval, then creates the milestone and assigns all approved items.
github-monitor
Watch your GitHub repos across four views - a combined urgency monitor (stale PRs, new issues, releases), a new-issue triage queue, a release upgrade digest, or your own opened-PR tracker.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.