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 futuregerald/futuregerald-claude-plugin --skill fix-checkgit clone --depth 1 https://github.com/futuregerald/futuregerald-claude-pluginWrote 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/futuregerald/futuregerald-claude-plugin/fix-check)<a href="https://agentmods.dev/skills/futuregerald/futuregerald-claude-plugin/fix-check"><img src="https://agentmods.dev/badge/skills/futuregerald/futuregerald-claude-plugin/fix-check/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/futuregerald/futuregerald-claude-plugin/fix-check"><img src="https://agentmods.dev/badge/skills/futuregerald/futuregerald-claude-plugin/fix-check.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.00083 | $0.01197 |
| Opus 5.5 | $0.00033 | $0.00479 |
| Sonnet 5.5 | $0.00017 | $0.00239 |
| Haiku 4.5 | $0.00008 | $0.00120 |
Grade A, and why
fix-check 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 10d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 10d ago First seen · 79 lines · 83 tokens per session scan A 467281743396
fix-check is a skill published in the GitHub repository futuregerald/futuregerald-claude-plugin (5 stars, last pushed 4d ago), with no licence file. It adds 83 tokens to every session and 1,197 once invoked, about $0.0003 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-10-17.
Other skills, from other repositories
quality-gate
Orchestrates the QUALITY pipeline stage for egregore work items, running code review, unbloat, and test updates. Use when running quality checks before a PR.
plugin-review
Review plugin quality with tiered checks and dependency scoping. Use for PR and pre-release audits.
verification-quality
Truth scoring, code-quality verification, and automatic rollback with a high accuracy threshold. Use when validating agent output before it ships, gating changes on quality, or adding a verify-and-rollback safety loop.
aif-code-review
Review code for bugs, regressions, maintainability, reliability and verification gaps with evidence.
tsq-audit
A code-audit skill that reviews changed files and runs relevant verification checks. It produces a report grouped by severity across security, type safety, error handling, API compatibility, tests, and performance.
proving-change-safety
Find what a change could break beyond the diff, then prove the one fact it is safe because of by running real code. Apply when the user asks what a change could break, whether a small diff is safe to merge, or to prove a safety fact before shipping. Use subsystem-walkthrough for how it works. Use design-rationale for…