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/mrbinnacle/azimuth/gap-scannernpx skills add MrBinnacle/azimuth --skill gap-scannergit clone --depth 1 https://github.com/MrBinnacle/azimuthWrote 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/mrbinnacle/azimuth/gap-scanner)<a href="https://agentmods.dev/skills/mrbinnacle/azimuth/gap-scanner"><img src="https://agentmods.dev/badge/skills/mrbinnacle/azimuth/gap-scanner.svg" alt="Measured on agentmods" 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 | $0.00055 | $0.01553 |
| Opus 5 | $0.00028 | $0.00776 |
| Sonnet 5 | $0.00011 | $0.00311 |
| Haiku 4.5 | $0.00006 | $0.00155 |
Grade A, and why
gap-scanner 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 4d 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 — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Gap Scanner
Find where AZIMUTH's stated coverage exceeds its actual reference support, and where reference material covers domains not yet claimed.
This skill reads files and produces a structured gap report. It does not propose fixes — it maps the delta between claims and reality.
Protocol
Run all 6 steps sequentially. Read each file group before drawing conclusions.
Step 1 — Extract Coverage Claims from SKILL.md
Read SKILL.md. Extract and list:
- Every decision type in "Use When"
- Every domain named in the DEEP mode load rules (tech/engineering →
software-failure-patterns.md, product/launch →launch-risks.md, startup/venture →startup-failures.md) - Every diagnostic load condition (which module trigger → which diagnostic file)
- Every domain-policy route (which Layer-3 domain → which file in
domain-policies/) - Every domain explicitly named in the base rate load rule
Step 2 — Audit Reference Files Against Claims
For each domain claimed in Step 1, read the corresponding reference file. Assess coverage depth:
- STRONG: File provides specific patterns, mechanisms, and diagnostic questions for this domain
- PARTIAL: File mentions the domain but coverage is thin, hedged, or missing mechanisms
- THIN: Domain is in base-rates.md but has no corresponding pattern file
- MISSING: Domain is claimed in SKILL.md but no reference material exists for it
Known gaps to confirm (from prior analysis):
- M&A / Partnerships: base-rates.md has a full M&A section. Is M&A listed in SKILL.md "Use When"? Is there a pattern file for M&A failure modes? Is there a domain-policy?
- IT / Infrastructure Migration: base-rates.md has a migration section. Is there a pattern file? A domain-policy?
- Organizational Change: base-rates.md has an org change section. Is org restructure in SKILL.md "Use When"? Pattern file? Domain-policy?
For each gap found, record:
- What is claimed (exact quote from SKILL.md)
- What exists (file and coverage depth)
- The delta
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.
- 4d ago First seen · 161 lines · 55 tokens per session scan A ad94d80e6117
gap-scanner is a skill published in the GitHub repository MrBinnacle/azimuth (8 stars, last pushed 3mo ago), licensed MIT. It adds 55 tokens to every session and 1,553 once invoked, about $0.0003 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-31.
Other skills, from other repositories
premortem
Run a premortem on any plan, launch, product, hire, strategy, or decision. Imagines it failed 6 months from now, works backward to find every reason why, then produces a revised plan. Triggers include "premortem this", "premortem my", "what could kill this", "stress test this plan", "find the blind spots", "poke holes…
pant-executive-decision-review
Pressure-test a product recommendation for an executive decision and rehearse the review. Use for approval, sponsorship, investment, priority, capacity, or commitment requests; not general roadmap or backlog review.
pant-antagonist-router
Select the smallest useful PANT skill, mode, entry path, pressure, and optional companion from a messy product-management request. Use when the correct pressure test or rehearsal is unclear.
pant-artifact-pressure-test
Pressure-test a product artifact, argument, or proposal when no specialist PANT scenario fits. Use for general grounding, contradictions, evidence, and readiness; not work clearly served by a specialist.
pant-business-case-review
Pressure-test a product investment business case and rehearse its review. Use for benefits, costs, alternatives, economics, uncertainty, adoption, ownership, and decision conditions; not a whole business model.
pant-market-sizing-review
Pressure-test TAM, SAM, SOM, and other market estimates. Use for market definition, segmentation, provenance, reachability, pricing, conversion, timing, sensitivity, and decision relevance; not generic market research.