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 RyosukeSAMA/github-ai --skill fix-and-verifygit clone --depth 1 https://github.com/RyosukeSAMA/github-aiWrote 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/ryosukesama/github-ai/fix-and-verify)<a href="https://agentmods.dev/skills/ryosukesama/github-ai/fix-and-verify"><img src="https://agentmods.dev/badge/skills/ryosukesama/github-ai/fix-and-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/ryosukesama/github-ai/fix-and-verify"><img src="https://agentmods.dev/badge/skills/ryosukesama/github-ai/fix-and-verify.svg" alt="Reviewed on agentmods" width="80" 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.00038 | $0.00208 |
| Opus 5.5 | $0.00015 | $0.00083 |
| Sonnet 5.5 | $0.00008 | $0.00042 |
| Haiku 4.5 | $0.00004 | $0.00021 |
Grade A, and why
fix-and-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
Fix and Verify
Work as Hephaestus and keep the change scoped to the reported behavior.
Workflow
- Identify the observed behavior, expected behavior, and likely execution path.
- Inspect the relevant code and tests when they are available.
- State the most likely root cause before changing code.
- Implement the smallest change that preserves surrounding contracts.
- Add or update a focused regression test when the risk justifies it.
- Run the narrowest meaningful checks, then broaden only when shared behavior changed.
- Report the changed files, verified commands, and any unverified residual risk.
Never claim a command passed unless its output was actually available. If local file or terminal tools are unavailable, return a precise patch or code block and the exact verification commands the user should run.
What ships with it
2 files 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.
- 1mo ago First seen · 23 lines · 38 tokens per session scan A bcdd7ac50633
fix-and-verify is a skill published in the GitHub repository RyosukeSAMA/github-ai (5 stars, last pushed today), licensed MIT. It adds 38 tokens to every session and 208 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-31.
Other skills, from other repositories
ast-grep
AST-aware structural code search and rewrite via ast-grep.
systematic-debugging
4-phase root cause debugging: understand bugs before fixing.
hermes-s6-container-supervision
Modify or debug s6 services in the Hermes Docker image.
node-inspect-debugger
Debug Node.js via --inspect + Chrome DevTools Protocol CLI.
module-regression
Govern cross-module regression in large repositories with a REGRESSION.md ledger that records each module's downstream consumers and executable acceptance command. After a change, run the changed module and every affected downstream command, and use observed exit codes as regression evidence under the project's…
agent-introspection-debugging
Structured self-debugging workflow for AI agent failures using capture, diagnosis, contained recovery, and introspection reports. Use when an agent run fails and you need a reproducible diagnosis instead of a retry.