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 skills add arbazkhan971/godmode --skill verifygit clone --depth 1 https://github.com/arbazkhan971/godmodeWrote 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/arbazkhan971/godmode/verify)<a href="https://agentmods.dev/skills/arbazkhan971/godmode/verify"><img src="https://agentmods.dev/badge/skills/arbazkhan971/godmode/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/arbazkhan971/godmode/verify"><img src="https://agentmods.dev/badge/skills/arbazkhan971/godmode/verify.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 283 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00023 | $0.03166 |
| Opus 5 | $0.00012 | $0.01583 |
| Sonnet 5 | $0.00005 | $0.00633 |
| Haiku 4.5 | $0.00002 | $0.00317 |
Grade A, and why
verify scanned grade A with 1 finding 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 8d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -sf -o /dev/null -w '%{http_code}' {url} How it starts
The opening of the file, as written. The whole thing — 298 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Activate When
/godmode:verify, "prove it", "verify this"- "/godmode:doctor", "which model is each role using", "model routing check"
- Another skill claims a result without evidence
- User questions a previous result
Workflow
0. Doctor Mode (early exit)
IF the invocation is /godmode:doctor or a model-routing question
("which model is each role using", "model routing check"): produce the
routing table per the spec below, print it, STOP. Skip Steps 1-8 and skip
the Goal-Bridge contract in Output Format -- the doctor is a config
report, not a claim verification. Missing config is the valid zero-config
default (every role inherits the session model), so the doctor NEVER
fails on missing config and ALWAYS exits 0. No ANSI. One command, no
guessing -- every row shows its source.
Resolution order (identical at every layer): GODMODE_MODEL_<ROLE> env ->
godmode.models.json (per-role merge: the project-root file wins per key
over ~/.config/godmode/models.json) -> session model. A model value is
valid iff it fully matches ^[A-Za-z0-9._-]+/[A-Za-z0-9._-]+$ OR is the
literal string session; an INVALID value at ANY layer emits one stderr
warning ([models] warning: ignoring invalid model value for role <role>)
and is treated as absent (fall through to the next layer). Role -> env
name: uppercase, hyphen dot underscore all -> underscore, via exactly
tr '[:lower:]._-' '[:upper:]___'; env name = GODMODE_MODEL_<that>.
Read with printenv "$name" 2>/dev/null || true. Set-but-empty value =
NOT an override (fall through). Case-folded roles (Plan/plan) collapse to
one env var -- documented here, not special-cased.
Path A (godmode repo checkout present): IF test -f adapters/pi/models.sh -> run bash adapters/pi/models.sh doctor and
print its output verbatim (same TSV contract as below), STOP.
Path B (skills-only install -- the common case; adapters/ is never
installed): inline sweep over the 8 canonical roles (plan build review
optimize explore security test docs) UNION every GODMODE_MODEL_* env
name UNION roles found in the config files, using this embedded
gm_route()-style resolver:
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.
- 8d ago First seen · 298 lines · 23 tokens per session scan A 59cd2e7d6694
verify is a skill published in the GitHub repository arbazkhan971/godmode (26 stars, last pushed 14d ago), licensed MIT. It adds 23 tokens to every session and 3,166 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
node-zombie-guardian
Use when diagnosing stale or orphaned Node.js processes launched by VCO, auditing ownership/liveness, or safely simulating cleanup without touching external Node workloads.
architecture-optimization
Guided journey from a working codebase grown slow and tangled to one measurably fast, cleanly bounded, and readable. Orchestrates eight skills phase by phase - working-with-legacy-code, clean-architecture, software-design-philosophy, refactoring-patterns, system-design, ddia-systems, release-it, pragmatic-programmer …
code-cleanup
Detect stale TODOs, unused imports, and dead code.
deliver-edge-cases
Documents edge cases, error states, boundary conditions, race conditions, and recovery paths for a feature - the systematic catalog of what can go wrong and the failure modes to design for. Use during specification to map the failure surface and ensure comprehensive coverage, or during QA planning to identify boundary…
skeptic
Adversarial code reviewer for Bug Hunter. Rigorously challenges each reported bug to determine if it's real or a false positive. Uses doc-lookup (Context Hub + Context7) to verify framework claims before disproval. The immune system that kills false positives.
fixer
Surgical code fixer for Bug Hunter. Implements minimal, precise fixes for verified bugs. Uses doc-lookup (Context Hub + Context7) to verify correct API usage in patches. Respects fix strategy classifications (safe-autofix vs manual-review vs larger-refactor).