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 Mimirs402/bountyverdict --skill route-github-agent-checksgit clone --depth 1 https://github.com/Mimirs402/bountyverdictWrote 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/mimirs402/bountyverdict/route-github-agent-checks)<a href="https://agentmods.dev/skills/mimirs402/bountyverdict/route-github-agent-checks"><img src="https://agentmods.dev/badge/skills/mimirs402/bountyverdict/route-github-agent-checks.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.1 | $0.00060 | $0.01124 |
| Opus 5 | $0.00030 | $0.00562 |
| Sonnet 5 | $0.00012 | $0.00225 |
| Haiku 4.5 | $0.00006 | $0.00112 |
Grade A, and why
route-github-agent-checks 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 7d 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Route Agent Decision Checks
Choose exactly one bounded live check, validate its unpaid x402 challenge, and use the typed result as a decision gate. Do not buy a broad bundle when one endpoint answers the task.
Select the check
| Need | Product | Method and path | Maximum | Operating skill |
|---|---|---|---|---|
| Assess one public bounty issue | BountyVerdict | POST /api/bounty-preflight |
50,000 atomic USDC | preflight-github-bounties |
| Rank 2–10 public bounty issues | BountyVerdict Portfolio | POST /api/portfolio |
400,000 atomic USDC | preflight-github-bounties |
| Audit repository coding-agent instructions | HarnessVerdict | POST /api/repository-agent-instructions-audit |
30,000 atomic USDC | audit-agent-harness |
| Audit one public skill before installation | SkillVerdict | POST /api/skill |
60,000 atomic USDC | preflight-agent-skills |
| Diagnose one public GitHub Actions run | RunVerdict | POST /api/github-actions-run-diagnosis |
40,000 atomic USDC | diagnose-github-actions |
| Decide whether one completed failed run merits a retry | FlakeVerdict | POST /api/github-actions-flake-retry-gate |
70,000 atomic USDC | classify-github-flakes |
| Gate a tools/list catalog change | MCPDriftVerdict | POST /api/mcp-drift |
20,000 atomic USDC | check-mcp-tool-drift |
Use RunVerdict when the root cause or next repair action is unknown. Use FlakeVerdict only for the narrower retry-versus-investigate decision. Use MCPDriftVerdict only with complete inline 2025-11-25 protocol snapshots; never use it to connect to or invoke a catalog-serving endpoint. If no row fits, do not purchase; find a more relevant service.
Resolve the live contract
- Read
https://mimirs402.github.io/bountyverdict/agent-manifest.json. - Require
statusto equalactive,production_apito equal the exact originhttps://bountyverdict-agent-production.mimirslab.workers.dev, and the selected product entry to match the table above. - Require that product's
skill_urlto equalhttps://mimirs402.github.io/bountyverdict/skills/<OPERATING-SKILL>/SKILL.md, using the operating-skill name from the table. Read it and follow its product-specific input validation, challenge validation, result interpretation, and retry rules. - Inspect the product's free
sampleand<production_api>/openapi.jsonbefore paying.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 7d ago First seen · 54 lines · 60 tokens per session scan A 3b213339812b
route-github-agent-checks is a skill published in the GitHub repository Mimirs402/bountyverdict (1 stars, last pushed 1mo ago), licensed MIT. It adds 60 tokens to every session and 1,124 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
bellwether
Bring the current PR to a mergeable state: CI green, all review comments resolved, no merge conflicts. Self-contained — watches CI, fixes issues, watches again until merge-ready. Use when the user wants to keep a PR green, auto-fix CI, resolve review comments, or says "get this merged".
GitHub Actions CI Patterns
Use this skill when adding or debugging GitHub Actions workflows and you want repeatable CI behavior, minimal permissions, and clear failure logs.
aw-author
Author, validate, and improve GitHub Agentic Workflow (gh-aw) markdown files. Use when the user wants to create a new workflow, validate an existing workflow, improve a workflow, or debug workflow issues. Triggers on: "aw-author", "agentic workflow", "gh-aw workflow", "workflow markdown", "workflow frontmatter"…
aw-daily
Fully autonomous daily pipeline for the aw-author plugin. Executes intelligence research (web search + GitHub activity queries), posts to Discussions, performs gap analysis against reference files, creates issues, implements changes on develop branch, creates PR, requests review, and auto-merges. Designed for…
gh-aw-report
Daily intelligence reporting for the GitHub Agentic Workflows (gh-aw) ecosystem. Executes 8+ targeted web searches, synthesizes findings into a structured Markdown report, updates the persistent knowledge base, and optionally posts to GitHub Discussions. Triggers on: "aw-report", "gh-aw report", "intelligence sweep"…
ai-debt-audit
Scan a repository for AI-generated technical, cognitive, and intent debt. Use when the user asks to audit a codebase for AI/vibe-coding risk, check for issues an AI coding assistant may have introduced (disabled RLS, hardcoded secrets, missing auth checks, SSTI, debug mode left on), assess technical debt after heavy…