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 agentmods add skills/zstevovich/claude-apd/apd-githubnpx skills add zstevovich/claude-apd --skill apd-githubgit clone --depth 1 https://github.com/zstevovich/claude-apdWrote 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/zstevovich/claude-apd/apd-github)<a href="https://agentmods.dev/skills/zstevovich/claude-apd/apd-github"><img src="https://agentmods.dev/badge/skills/zstevovich/claude-apd/apd-github.svg" alt="Measured on agentmods" height="20"></a>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.00104 | $0.01927 |
| Opus 5 | $0.00052 | $0.00963 |
| Sonnet 5 | $0.00021 | $0.00385 |
| Haiku 4.5 | $0.00010 | $0.00193 |
Grade A, and why
apd-github 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 3d 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 — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Projects — APD Pipeline Tracking (Codex)
Maps APD pipeline phases to GitHub Projects v2 columns. Each task becomes an issue with the spec-card.md content embedded, and pipeline progress is reflected on the board.
When to use / When to skip
Use when:
- The project has a GitHub Projects v2 board configured (
GITHUB_PROJECTS_URLin AGENTS.md) - A pipeline phase just transitioned — sync the column
- Spec was just approved — create the issue
- Pipeline just committed — close the issue with the commit reference
Skip when:
- No GitHub Projects board is configured for the project
- The repo is not on GitHub (Gitlab/Bitbucket/local)
ghCLI is not authenticated — escalate, don't silently skip- The user is in a hotfix flow that bypasses the pipeline (no issue to track)
Automation — gh-sync
Instead of calling gh directly, use the gh-sync wrapper which tracks the
active issue across the pipeline:
bash ${APD_PLUGIN_ROOT}/bin/core/gh-sync spec "User login"
bash ${APD_PLUGIN_ROOT}/bin/core/gh-sync builder
bash ${APD_PLUGIN_ROOT}/bin/core/gh-sync reviewer
bash ${APD_PLUGIN_ROOT}/bin/core/gh-sync verifier
bash ${APD_PLUGIN_ROOT}/bin/core/gh-sync done 42 abc1234
bash ${APD_PLUGIN_ROOT}/bin/core/gh-sync skip 42 "Hotfix"
bash ${APD_PLUGIN_ROOT}/bin/core/gh-sync status
gh-sync automatically tracks the issue number for the current pipeline — you
don't need to pass it at every step. On Codex, the wrapper is invoked through
shell calls subject to guard-bash-scope.
Prerequisite
ghCLI authenticated (gh auth login)- GitHub Projects v2 created with columns: Spec, In Progress, Review, Testing, Done
GITHUB_PROJECTS_URLset inAGENTS.md
Pipeline → column mapping
| APD step | GitHub Projects column | Action |
|---|---|---|
apd:apd_advance_pipeline('spec', "Task") |
Spec | Create issue with spec-card.md content, add to board |
apd:apd_advance_pipeline('builder') |
In Progress | Move issue to In Progress |
apd:apd_advance_pipeline('reviewer') |
Review | Move issue to Review |
apd:apd_advance_pipeline('verifier') |
Testing | Move issue to Testing |
| Commit (successful) | Done | Close issue, link commit, move to Done |
apd:apd_advance_pipeline('skip', "<reason>") |
Done | Close issue with apd-skip label |
What ships with it
4 files 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.
- 3d ago First seen · 185 lines · 104 tokens per session scan A 2454947a65ea
apd-github is a skill published in the GitHub repository zstevovich/claude-apd (5 stars, last pushed 1mo ago), licensed MIT. It adds 104 tokens to every session and 1,927 once invoked, about $0.0005 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…