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/andresharpe/dotbot/verifynpx skills add andresharpe/dotbot --skill verifygit clone --depth 1 https://github.com/andresharpe/dotbotWhat 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.00020 | $0.00436 |
| Opus 5 | $0.00010 | $0.00218 |
| Sonnet 5 | $0.00004 | $0.00087 |
| Haiku 4.5 | $0.00002 | $0.00044 |
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 Verification Gates
Run all verification hooks in .bot/hooks/verify/ and present a clear pass/fail report.
Steps
1. Privacy Scan
Run the privacy/secrets scanner:
pwsh .bot/hooks/verify/00-privacy-scan.ps1
If the user said /verify staged or mentioned "staged only", add the -StagedOnly flag:
pwsh .bot/hooks/verify/00-privacy-scan.ps1 -StagedOnly
2. Git Clean Check
Check for uncommitted changes outside .bot/:
pwsh .bot/hooks/verify/01-git-clean.ps1
3. Git Pushed Check
Check for unpushed commits:
pwsh .bot/hooks/verify/02-git-pushed.ps1
Presentation Format
Present results as a verification report:
## Verification Report
| Gate | Result |
|----------------|--------|
| Privacy scan | PASS/FAIL |
| Git clean | PASS/FAIL |
| Git pushed | PASS/FAIL |
Overall: ALL PASSED / N FAILED
### Failures (if any)
#### <Gate name>
- Issue: <description>
- Remediation: <what to do>
Rules
- Read-only: Never fix issues automatically — only report them with remediation guidance
- Always run all gates: Do not stop on first failure; run every gate and report all results
- Report honestly: Show exact output from each hook; do not summarize away important details
- Exit code awareness: Each hook outputs JSON to stdout with
issuesanddetailskeys — parse these for structured reporting - Remediation guidance: For each failure, provide a concrete command or action the user can take to resolve it
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 · 64 lines · 20 tokens per session scan A 4cc49b01af43
verify is a skill published in the GitHub repository andresharpe/dotbot (54 stars, last pushed 6d ago), licensed MIT. It adds 20 tokens to every session and 436 once invoked, about $0.0001 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
hedgehog-planning-intake
Use on any core for first-run planning intake — Phase 0 runs the vendored BMAD-METHOD planning shelf, shared by every core, and Phase 1 (mining 04-prd.md into intent records plus the Add-ons/sync-and-remote-entities decision) is full-stack-app's and pwa-app's shared procedure — identical mechanics, a different…
inbound-triage
Maintainer-only. Use when triaging inbound GitHub issues and pull requests on skyf0xx/hedgehog — "triage the issues", "check the PRs", "review inbound", "what's in the queue". Reads each item read-only, judges it for security and for whether it is real, then fixes and closes or comments and closes. Not part of the…
bmad-product-brief
Create, update, or validate a product brief. Use when the user wants help producing, editing, or validating a brief.
bmad-revendor
Maintainer-only. Use when re-vendoring vendor-skills/BMAD/ against a newer BMAD-METHOD commit — "update BMAD", "re-vendor BMAD", "bump the BMAD pin". Not part of the Hedgehog discipline a consuming project copies; this only applies to the Hedgehog repo itself.
bmad-deep-recon
Decision-grade research, three ways: draft a deep-research prompt for the user to run in their own tool (ChatGPT, Gemini, Grok, Perplexity, …), process a finished research report — file it, distill a succinct cited summary with metadata that downstream skills consume without reprocessing — or run the research here…
conventional-commits
Use when uncommitted changes need to be split into atomic, conventional commits ordered for review. Triggers on "commit this", "make commits", "clean up commits", "commit the changes". In Hedgehog, each Loop step is already meant to be its own commit — this skill matters most when a Correction Protocol fast-forward…