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 commands/jcstack/ashare-ai-analyst/verifygit clone --depth 1 https://github.com/Jcstack/ashare-ai-analystWhat 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.00000 | $0.00100 |
| Opus 5 | $0.00000 | $0.00050 |
| Sonnet 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 2d 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.
- 2d 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 (5 stars, last pushed 2mo 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
checkpoint
Create a checkpoint by staging the changes you have made using git. usage: git [-v | --version] [-h | --help] [-C ] [-c = ] [--exec-path[= ]] [--html-path] [--man-path] [--info-path] [-p | --paginate | -P | --no-pager] [--no-replace-objects] [--bare] [--git-dir= ] [--work-tree= ] [--namespace= ] [--super-prefix= ]…
os-meeting
快速创建和管理AI团队会议.
wish-review
description: Execute an end-to-end review loop for a wish, combining test execution, Death Testament aggregation, and scoring.
initializer-prompt
You are the FIRST agent in a long-running autonomous development process. Your job is to set up the foundation for all future coding agents.
learn
Analyze the current session and extract any patterns worth saving as skills.
eval
Legacy slash-entry shim for the eval-harness skill. Prefer the skill directly.