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 GlamgarOnDiscord/claude-saas-blueprint --skill fixgit clone --depth 1 https://github.com/GlamgarOnDiscord/claude-saas-blueprintWrote 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/glamgarondiscord/claude-saas-blueprint/fix)<a href="https://agentmods.dev/skills/glamgarondiscord/claude-saas-blueprint/fix"><img src="https://agentmods.dev/badge/skills/glamgarondiscord/claude-saas-blueprint/fix/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/glamgarondiscord/claude-saas-blueprint/fix"><img src="https://agentmods.dev/badge/skills/glamgarondiscord/claude-saas-blueprint/fix.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.00029 | $0.00320 |
| Opus 5 | $0.00015 | $0.00160 |
| Sonnet 5 | $0.00006 | $0.00064 |
| Haiku 4.5 | $0.00003 | $0.00032 |
Grade A, and why
fix 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 11d 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
Quand utiliser
- Message d'erreur clair avec fichier et ligne
- Bug de régression après un changement récent
- Erreur TypeScript ou lint à corriger
- Import cassé, variable undefined, prop manquante
Quand NE PAS utiliser
- Bug sans message d'erreur clair →
/debug - Bug qui nécessite de comprendre le flux complet →
/debug - Simple changement cosmétique →
/oneshot
Instructions
1. Comprendre (30 secondes)
- Lire le message d'erreur
- Identifier le fichier et la ligne
- Lire le fichier concerné
2. Fix (immédiat)
- Appliquer la correction minimale
- Ne PAS refactorer le code autour — juste le fix
3. Vérifier
tsc --noEmit- Exécuter le test du fichier modifié (s'il existe)
- Si le fix est dans un pattern qui pourrait se répéter → ajouter dans
rules/_learned.md
4. Done
- « Fix appliqué : [description en 1 ligne] »
Note
- Style / format : laisser ESLint, Prettier, Biome ou les hooks (
.claude/settings.json) faire le travail — pas de réécriture « cosmétique » via l’agent sauf demande explicite.
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.
- 11d ago First seen · 38 lines · 29 tokens per session scan A fce632c102e6
fix is a skill published in the GitHub repository GlamgarOnDiscord/claude-saas-blueprint (2 stars, last pushed 3mo ago), licensed MIT. It adds 29 tokens to every session and 320 once invoked, about $0.0001 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
systemic-issue-triage
Trigger: new issue, bug report, triage, backlog, issue flood, community report, root cause, dead-end, blocked user. Attack issues by root class, never one-by-one; fixes must shrink the system, not grow it.
issue-root-resolution
Trigger: root audit, atacar la raíz, issue roots, backlog roots, mechanism map, deletion-driven fix, resolver issues de raíz, close outdated issues. Audit and resolve issue clusters by verified root cause.
rdd-defect-workflow
Trigger: RDD, receipt-driven development, review authority, receipt/lineage, correction/recovery, delivery gate/kill switch, bounded review defects. Guide work.
debug-live
Guides root-cause investigations with debugging capabilities by setting breakpoints, starting a debug session, stepping through execution, inspecting variables, and tracing symptoms back to their origin. Prefer it for runtime bugs, failing tests, exceptions, crashes, hangs, wrong/null values, and unexpected output…
debug-helper
Help debug code by analyzing error messages, identifying root causes, and providing fix suggestions.
post-mortem
Diagnose instruction defects and optionally submit Rosetta GitHub issue.