Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/yusufalikync/ccsnpx agentmods add skills/yusufalikync/ccs/verifyWrote 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/yusufalikync/ccs/verify)<a href="https://agentmods.dev/skills/yusufalikync/ccs/verify"><img src="https://agentmods.dev/badge/skills/yusufalikync/ccs/verify/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/yusufalikync/ccs/verify"><img src="https://agentmods.dev/badge/skills/yusufalikync/ccs/verify.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00016 | $0.00336 |
| Opus 5.5 | $0.00006 | $0.00134 |
| Sonnet 5.5 | $0.00003 | $0.00067 |
| Haiku 4.5 | $0.00002 | $0.00034 |
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 1mo 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
Verify
Run all checks in sequence and report results.
Instructions
1. Smoke tests
npm test
All tests must pass.
2. Install cycle
node bin/cli.js install
node bin/cli.js status
node bin/cli.js uninstall
node bin/cli.js status
- After install: status should show ACTIVE
- After uninstall: status should show NOT INSTALLED
3. console.log check
Grep scripts/statusline.js for console.log. It must NOT contain any — only process.stdout.write() is allowed.
4. Package check
npm pack --dry-run
Verify these are included: bin/cli.js, src/, scripts/statusline.js. Verify scripts/smoke-test.js is NOT included (excluded by design — only scripts/statusline.js is in the package).
5. No hardcoded paths
Grep src/ files for hardcoded ~/.claude or /tmp/ paths. All paths should come from src/paths.js or os.tmpdir().
Output
Report each check as:
- PASS: Check description
- FAIL: Check description — what went wrong and how to fix
Final summary: X/5 checks passed.
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.
- 1mo ago First seen · 50 lines · 16 tokens per session scan A 915f272e88c4
verify is a skill published in the GitHub repository yusufalikync/ccs (3 stars, last pushed 6mo ago), licensed MIT. It adds 16 tokens to every session and 336 once invoked, about $0.0001 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-31.
Other skills, from other repositories
live-preview
Mid-build visual verification loop. Takes screenshots of components during construction, not just after. Catches visual regressions and invisible features before they compound. Requires Playwright or similar screenshot tool.
brooks-sweep
Full-sweep mode: runs a unified analysis across all quality dimensions — code decay, architecture, tech debt, and test quality — then applies fixes directly to the codebase. Safe changes are auto-applied; risky changes are confirmed before execution. Drawing on twelve classic engineering books. Triggers when: user…
bug-fixer
A bug reproduces, the expected behaviour is clear, and the fix stands apart from the current work.
api-testing
HTTP API testing for TypeScript (Supertest) and Python (httpx, pytest). Test REST APIs, GraphQL, request/response validation, authentication, and error handling.
bun-jest-migration
Use when migrating from Jest to Bun's test runner, import compatibility, mocks, and config.
bun-test-mocking
Use for mock functions in Bun tests, spyOn, mock.module, implementations, and test doubles.