Borrowing it
Nothing to install: this file belongs to Jcstack/ashare-ai-analyst. 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/Jcstack/ashare-ai-analyst/main/.claude/commands/verify.mdgit clone --depth 1 https://github.com/Jcstack/ashare-ai-analystWrote 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/commands/jcstack/ashare-ai-analyst/verify)<a href="https://agentmods.dev/commands/jcstack/ashare-ai-analyst/verify"><img src="https://agentmods.dev/badge/commands/jcstack/ashare-ai-analyst/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/commands/jcstack/ashare-ai-analyst/verify"><img src="https://agentmods.dev/badge/commands/jcstack/ashare-ai-analyst/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.00000 | $0.00100 |
| Opus 5.5 | $0.00000 | $0.00040 |
| Sonnet 5.5 | $0.00000 | $0.00020 |
| Haiku 4.5 | $0.00000 | $0.00010 |
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 2mo 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
Run the full local verification the way CI does, and report pass/fail for each step:
.venv/bin/ruff check src/ tests/.venv/bin/ruff format --check src/ tests/.venv/bin/pytest tests/unit -qcd frontend && npx tsc --noEmit && npm run build
If a step fails, show the failing output and stop. Do not attempt fixes unless I ask.
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.
- 2mo ago First seen · 9 lines · 0 tokens per session scan A 63542fff3920
verify is a command published in the GitHub repository Jcstack/ashare-ai-analyst (8 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 100 tokens. 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 commands, from other repositories
expect
Diff-aware AI browser testing — reads the git diff, maps changes to affected pages via the route map, generates a targeted test plan, and executes it via agent-browser (Rust daemon + CDP, ARIA-tree-first) with pass/fail reporting. Use when testing UI changes, verifying PRs before merge, or running regression checks on…
tdd
Test-driven change — write the failing test first, then implement.
fire-verify-uat
Conversational User Acceptance Testing with automatic parallel diagnosis on failures.
story-and-test
For the component(s) in scope.
fire-test
Run Dominion Flow plugin integration tests to verify all commands and integrations work correctly.
modernize-transform
Transform one legacy module to the target stack — idiomatic rewrite with behavior-equivalence tests.