Borrowing it
Nothing to install: this file belongs to stevesolun/ctx. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/stevesolun/ctx/main/.claude/skills/ctx-verify/SKILL.mdgit clone --depth 1 https://github.com/stevesolun/ctxWrote 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/stevesolun/ctx/ctx-verify)<a href="https://agentmods.dev/skills/stevesolun/ctx/ctx-verify"><img src="https://agentmods.dev/badge/skills/stevesolun/ctx/ctx-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/stevesolun/ctx/ctx-verify"><img src="https://agentmods.dev/badge/skills/stevesolun/ctx/ctx-verify.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00062 | $0.00545 |
| Opus 5.5 | $0.00025 | $0.00218 |
| Sonnet 5.5 | $0.00012 | $0.00109 |
| Haiku 4.5 | $0.00006 | $0.00055 |
Grade A, and why
ctx-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.
How it starts
The opening of the file, as written. The whole thing — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verify ctx changes
- Inspect the requested behavior and changed surface. Read only the relevant
section of
CONTRIBUTING.mdbefore selecting checks. - Run the smallest focused tests or deterministic checks that exercise the changed behavior first.
- Escalate evidence in proportion to risk:
- Small, localized change: focused tests, schemas, or diff checks.
- Material repository change:
scripts/no_mistakes_run.sh fast. - PR-level, contract, workflow, migration, packaging, security, or release
change: run the fast gate, then
python scripts/ci_preflight.py --profile pr. - Documentation navigation or linked public-asset change: follow the tracker
contract in
CONTRIBUTING.md; do not require tracker changes for ordinary prose-only edits. - Windows-sensitive change: follow the native-CI contract in
CONTRIBUTING.md; local checks do not replace required Windows evidence.
- Treat the fast gate as committed-history evidence. When the working tree is dirty, pair it with focused checks against the actual uncommitted changes.
- If a gate cannot find its trusted pytest, Ruff, and mypy environment, report the environment failure. Do not silently install dependencies or weaken the trust check.
- Use an independent validator only when semantic risk remains after deterministic checks, especially for material security, migration, or release work.
- Report each check, its result, and any omitted or unavailable evidence.
Rubric
Mark each applicable criterion pass, fail, or not verified:
- Intent: The artifact satisfies the request without unrelated scope.
- Behavior: Fresh evidence covers the changed success path and relevant failure or regression paths.
- Static integrity: Applicable lint, formatting, and type checks pass.
- Repository contracts: Migration, changed-file, documentation, packaging, and platform requirements remain satisfied where relevant.
- Evidence quality: Results apply to the actual changed surface and are not stale or inapplicable.
- Handoff: Skipped checks and residual risks are stated plainly.
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 · 49 lines · 62 tokens per session scan A 4bfa8aa064b9
ctx-verify is a skill published in the GitHub repository stevesolun/ctx (589 stars, last pushed 11d ago), licensed MIT. It adds 62 tokens to every session and 545 once invoked, about $0.0002 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-30.
Other skills, from other repositories
create-prove
Run a changed Aeon skill for real and attach SHA-bound behavioral evidence to its PR.
verification-engine
Use when verifying build/test/lint before commit, PR, or completion claims. Runs verification pipeline in fresh subagent context with auto-repair. Triggers on /handoff-verify, pre-commit check, build verification, test validation.
verify-implementation
A workflow that runs a project’s verification skills to produce a report on coding patterns, architecture rules, and project conventions. It is intended for work after implementation, before a pull request, or during code review.
accessibility-a11y
WCAG 2.2 compliance, ARIA patterns, keyboard navigation, screen readers, automated testing.
agent-e2e-test-specialist
Specialist subagent: Playwright, Cypress, and visual regression testing specialist. Use only when the user explicitly asks for E2E tests, browser test automation, or visual regression testing. Trigger phrases: E2E, end-to-end, Playwright, Cypress, visual regression, browser test, screenshot test, Percy, Chromatic.
agent-test-generator
Specialist subagent: Generates comprehensive test suites using TDD patterns. Use only when the user explicitly asks for tests, improved coverage, or test-first development.