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/itsribbz/godspeed/verifynpx skills add itsribbZ/Godspeed --skill verifygit clone --depth 1 https://github.com/itsribbZ/GodspeedWrote 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/itsribbz/godspeed/verify)<a href="https://agentmods.dev/skills/itsribbz/godspeed/verify"><img src="https://agentmods.dev/badge/skills/itsribbz/godspeed/verify.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.00073 | $0.00915 |
| Opus 5 | $0.00036 | $0.00458 |
| Sonnet 5 | $0.00015 | $0.00183 |
| Haiku 4.5 | $0.00007 | $0.00092 |
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 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verify — Build & Test Health Check
Triggers: "verify", "check build", "does it work", "run tests", "health check", "is this green"
What it does
Inspects the current working directory, matches it against a project-type signature, and runs the corresponding verification commands. One pass/fail verdict with an error summary if anything breaks.
Defaults to fail-fast — the first failing command stops the sequence unless the user explicitly asks for a full sweep.
Project-Type Detection
| Signature file | Detected type | Verification commands |
|---|---|---|
pyproject.toml OR setup.py OR requirements.txt OR *.py at root |
Python | python -m py_compile $(git ls-files '*.py') → pytest -x if a tests/ dir exists |
package.json |
Node / JS | npm run build (if defined) → npm test (if defined) |
CMakeLists.txt |
C / C++ (CMake) | cmake --build build → optional ctest |
Cargo.toml |
Rust | cargo check → cargo test |
go.mod |
Go | go build ./... → go test ./... |
Makefile |
make | make -n (dry run) then make test if defined |
.uproject |
Unreal Engine 5 | SKIP — requires the Editor; report "UE5 project detected, manual verify required" |
A custom scripts/verify.sh or .verify file |
User-defined | Run it |
| No matches | Unknown | Report the directory contents and ask |
If multiple signatures match (monorepo), run them in parallel and aggregate results.
Output
═══════════════════════════════════════
VERIFY — <date>
═══════════════════════════════════════
PROJECT TYPE: <detected>
CWD: <absolute path>
CHECKS
[PASS] <command> <duration>
[FAIL] <command> <duration>
<first few lines of error>
[SKIP] <command> <reason>
VERDICT: GREEN | YELLOW | RED
NEXT ACTIONS (if RED):
1. <specific file:line or error type pointing to the likely cause>
- GREEN = all PASS
- YELLOW = some SKIP, no FAIL
- RED = any FAIL
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 · 82 lines · 73 tokens per session scan A 946d81044c43
verify is a skill published in the GitHub repository itsribbZ/Godspeed (1 stars, last pushed 2mo ago), licensed MIT. It adds 73 tokens to every session and 915 once invoked, about $0.0004 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
model-routing
Route work to the cheapest model tier that holds quality. Use when deciding which model or agent should handle a task, when the user asks about token economy / cost optimization, or when dispatching implementation, review, or test-run work to subagents.
review
5-pass structured code review — correctness, security, performance, readability, consistency.
alive:system-upgrade
Upgrade ALIVE to the current version. Handles v1/v2/v3.x source states, multi-surface aware (alive-mcp / Hermes / Codex), retroactive version detection, partial-failure resume, dry-run previews, and rollback inspection.
codex-test-gen
Generate unit tests for specified functions using Codex MCP.
brand-docx
Brand-aware Word engine. Use to (1) EXTRACT a company's brand from a Word template into a reusable "Brand Profile", (2) COMPREHEND the template with the model (optional), (3) VERIFY it, (4) GENERATE new on-brand .docx documents FROM a saved profile. Trigger on "extract our brand", "learn/match this template", "use our…
extract-resume
Parse a resume's uploaded PDF into structured JSON (basics, experience, projects, skills, education) and save it to the editor.