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/diet103/claude-code-infrastructure-showcase/source-command-verify-setupnpx skills add diet103/claude-code-infrastructure-showcase --skill source-command-verify-setupgit clone --depth 1 https://github.com/diet103/claude-code-infrastructure-showcaseWhat 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.00017 | $0.00333 |
| Opus 5 | $0.00009 | $0.00167 |
| Sonnet 5 | $0.00003 | $0.00067 |
| Haiku 4.5 | $0.00002 | $0.00033 |
Grade A, and why
source-command-verify-setup 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.
What it actually says
source-command-verify-setup
Use this skill when the user asks to run the migrated source command verify-setup.
Command Template
Run the Codex infrastructure health check and get it fully green.
Steps
-
Run the health check from the project root:
bash .Codex/scripts/verify-setup.sh -
For every
[FAIL]line, apply the printed fix. Common fixes:- Dependencies missing:
cd .Codex/hooks && npm install - Scripts not executable:
chmod +x .Codex/hooks/*.sh - Invalid JSON in
.Codex/settings.jsonor.Codex/skills/skill-rules.json: read the file, find the syntax error (usually a trailing comma), and repair it without changing any settings values - Missing hook scripts registered in settings.json: ask the user whether to copy them from the showcase repo (https://github.com/diet103/Codex-infrastructure-showcase) or remove the dead registrations
- Dependencies missing:
-
Re-run the script after each fix until it reports 0 failed.
-
[WARN]lines are optional features (session intelligence, jq-based file tracking, AI classification keys). Do NOT install API keys or system packages on the user's behalf - summarize what each warning means and let the user decide. -
Report the final result to the user: what was broken, what you fixed, and what (if anything) remains as a warning.
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 · 32 lines · 17 tokens per session scan A 1b5b06dfc98a
source-command-verify-setup is a skill published in the GitHub repository diet103/claude-code-infrastructure-showcase (10,016 stars, last pushed 1mo ago), licensed MIT. It adds 17 tokens to every session and 333 once invoked, about $0.0001 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
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…