What is wave-issue-coverage?

A workflow for matching draft requirements in Ground Control—a requirements-tracking system—with GitHub issues, which record development work. It handles one wave of requirements or all unfinished waves.

Finding draft requirements, creating or updating GitHub issue coverage, and tracking which requirements are represented by issues. It requires Ground Control access and authenticated GitHub command-line access.

It prevents draft requirements from having no corresponding work item and keeps the requirement and issue linked in both directions.

wave-issue-coverage — Skill for Claude Code and Codex by Brad-Edwards: A workflow for matching draft requirements in Ground Control

Install

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.

agentmods

npx agentmods add skills/brad-edwards/aptl/wave-issue-coverage

Any agent

npx skills add Brad-Edwards/aptl --skill wave-issue-coverage

Clone the repo

git clone --depth 1 https://github.com/Brad-Edwards/aptl

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/brad-edwards/aptl/wave-issue-coverage.svg)](https://agentmods.dev/skills/brad-edwards/aptl/wave-issue-coverage)

Your own site

<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="Measured on agentmods" height="20"></a>

Per session 72 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,778 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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	$0.00072	$0.01778
Opus 5	$0.00036	$0.00889
Sonnet 5	$0.00014	$0.00356
Haiku 4.5	$0.00007	$0.00178

Measured 5d ago against content hash 631405ab2526, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 5d 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.

.claude/skills/wave-issue-coverage/SKILL.md · 120 lines

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 string all
- all → process every wave that has DRAFT requirements, smallest wave first

Preconditions

Read .ground-control.yaml at the repo root via gc_get_repo_ground_control_context to obtain:
- project — Ground Control project identifier
- github_repo — owner/repo for gh calls These values are passed to every MCP and gh call in this workflow. Do not hard-code them.
The GC MCP server (mcp__ground-control__*) must be available.
gh auth status must be authenticated with write access to github_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 wave filter if all was 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_traceability with the requirement UUID. Note any existing GITHUB_ISSUE artifact 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.

Read the full file on GitHub · 120 lines

Changes

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.

5d ago First seen · 120 lines · 72 tokens per session scan A 631405ab2526

Subscribe to this mod's changes

wave-issue-coverage is a skill published in the GitHub repository Brad-Edwards/aptl (24 stars, last pushed yesterday), licensed MIT. It adds 72 tokens to every session and 1,778 once invoked, about $0.0004 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.

Git and workflow Project management agents blue-team cyber-range cybersecurity cybersecurity-tools infosec

api-security-testing

Security-test a REST, GraphQL, or gRPC API with Strix — autonomous agents that enumerate endpoints from an OpenAPI/GraphQL schema (or by crawling), then actually exploit the API-specific vulnerability classes in the OWASP API Security Top 10 (2023) — broken object-level authorization (BOLA/IDOR), broken object…

usestrix/strix · 144 tokens

owasp-top-10-testing

Test an application against the OWASP Top 10 with Strix — autonomous AI agents that attempt real exploits for each category of the current OWASP Top 10:2025 (broken access control including SSRF, security misconfiguration, software supply chain failures, cryptographic failures, injection, insecure design…

usestrix/strix · 151 tokens

fix-security-vulnerabilities-with-strix

Fix security vulnerabilities found by a Strix pentest (open-source CLI or app.strix.ai cloud) — triage by severity, patch the root cause rather than the symptom, and re-run Strix to prove each fix actually closes the exploit. Handles injection, XSS, SSRF, broken access control, IDOR, and other validated findings. Use…

usestrix/strix · 124 tokens

find-security-vulnerabilities-in-code

Find security vulnerabilities in a codebase or repository with Strix — a white-box AI security review that reads your source, reasons about the actual data flow and authorization model, then exploits what it finds in a live sandbox so every reported issue has a working proof-of-concept instead of a noisy…

usestrix/strix · 129 tokens

web-app-penetration-testing

Pentest a web app or website end to end — black-box testing of a live URL, staging environment, or local dev server that finds and exploits real vulnerabilities (auth bypass, broken access control, IDOR, injection, XSS, SSRF, business logic) and proves each one with a working proof-of-concept instead of a signature…