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 suxrobGM/jobpilot --skill verifygit clone --depth 1 https://github.com/suxrobGM/jobpilotWrote 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/suxrobgm/jobpilot/verify)<a href="https://agentmods.dev/skills/suxrobgm/jobpilot/verify"><img src="https://agentmods.dev/badge/skills/suxrobgm/jobpilot/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/suxrobgm/jobpilot/verify"><img src="https://agentmods.dev/badge/skills/suxrobgm/jobpilot/verify.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00060 | $0.00212 |
| Opus 5.5 | $0.00024 | $0.00085 |
| Sonnet 5.5 | $0.00012 | $0.00042 |
| Haiku 4.5 | $0.00006 | $0.00021 |
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 1mo 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
Verify
Run from the repo root, in order. Stop at the first failure and report its output.
bun run cibun run knipbun --cwd=apps/api run typecheckbun --cwd=apps/web run typecheckbun --cwd=apps/api run testbun --cwd=packages/contracts run test- Only if the working tree or branch diff touches
apps/terminal/ortests/(git status --porcelain+git diff --name-only main...):dotnet test
Finish with a one-line pass/fail summary per step.
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.
- 1mo ago Changed 0c45290180e3
- 1mo ago Changed · +1 lines · +3 tokens per session 4d04462cc646
- 2mo ago First seen · 20 lines · 57 tokens per session scan A 4d730f6674a8
verify is a skill published in the GitHub repository suxrobGM/jobpilot (104 stars, last pushed 3d ago), licensed MIT. It adds 60 tokens to every session and 212 once invoked, about $0.0002 per session on Opus 5.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
precommit
Pre-commit checks — lint:fix -> build -> test.
precommit-fast
Quick pre-commit checks — lint:fix -> test.
vibe-cherry-pick-integration
Safely integrates commits from parallel agent branches using sequential cherry-pick. Use after parallel work completes in isolated branches or worktrees.
workflow
Run the complete 5-step development workflow: focus problem → prevent over-development → test-first (TDD) → document → smart commit. Use when starting a new feature, or when the user runs /workflow or asks for the full development flow.
shipyard-verification
Requires fresh verification evidence before any claim that work is complete, fixed, or passing. Use before committing, creating PRs, or moving to the next task. Also use when a status report contains words like "should", "probably", or "seems to", or expresses satisfaction ("Great!", "Done!") before verification…
vibe-pre-commit-audit
Scans staged changes for secrets, debug statements, TODOs without references, and other common commit mistakes. Use before creating any commit.