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/xiaolai/cc-suite/verifynpx skills add xiaolai/cc-suite --skill verifygit clone --depth 1 https://github.com/xiaolai/cc-suiteWrote 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/xiaolai/cc-suite/verify)<a href="https://agentmods.dev/skills/xiaolai/cc-suite/verify"><img src="https://agentmods.dev/badge/skills/xiaolai/cc-suite/verify.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.00059 | $0.00914 |
| Opus 5 | $0.00030 | $0.00457 |
| Sonnet 5 | $0.00012 | $0.00183 |
| Haiku 4.5 | $0.00006 | $0.00091 |
Grade A, and why
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 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verify
Ask Claude Code to check whether previously reported audit findings have been resolved. Claude re-reads the files at the reported locations and renders a verdict per issue. Codex provides the issue list; Claude provides the verdict.
When to Use
- After Codex has applied fixes from a
$auditrun - To confirm a manual fix was applied at the correct location
- As the final step of a
$audit-fixcycle
Arguments
| Argument | Effect |
|---|---|
session_id |
Claude session from the prior $audit — reuses full audit context |
| issue list | Paste or reference the findings to verify (file:line + description) |
Call Pattern
Option A: Continue the audit session (preferred)
If {audit_session_id} is available from a prior $audit or $audit-fix run:
mcp__claude-code__claude_code_reply:
session_id: {audit_session_id}
prompt: |
The following issues from your audit have been addressed. Verify each one.
ISSUES TO VERIFY:
{paste findings in "file:line | severity | issue description" format}
For each issue report one of:
- FIXED — issue resolved fully, no new problems introduced
- NOT FIXED — issue still present at the reported location (explain why)
- PARTIAL — partially addressed; describe what remains
- REGRESSED — fix introduced a new problem (describe it)
Read the files at the reported locations. Do not assume a fix is correct
without reading the current code.
Option B: Fresh verification session
When no prior session is available:
mcp__claude-code__claude_code:
prompt: |
Verify whether the following issues have been fixed.
ISSUES TO VERIFY:
{paste findings in "file:line | severity | issue description" format}
For each issue:
1. Read the file at the reported location
2. Check if the issue is resolved
3. Report: FIXED / NOT FIXED / PARTIAL / REGRESSED
For NOT FIXED and PARTIAL: explain what is still wrong.
For REGRESSED: describe the new problem introduced.
Apply independent judgment — do not accept surface-level changes that
mask the underlying issue.
cwd: {project working directory}
effort: high
permissionMode: plan
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.
- 3d ago First seen · 107 lines · 59 tokens per session scan A 1500b219c20a
verify is a skill published in the GitHub repository xiaolai/cc-suite (45 stars, last pushed yesterday), licensed ISC. It adds 59 tokens to every session and 914 once invoked, about $0.0003 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…