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 digipulse-engineering/GAAI-framework --skill remediate-failuresgit clone --depth 1 https://github.com/digipulse-engineering/GAAI-frameworkWrote 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/digipulse-engineering/gaai-framework/remediate-failures)<a href="https://agentmods.dev/skills/digipulse-engineering/gaai-framework/remediate-failures"><img src="https://agentmods.dev/badge/skills/digipulse-engineering/gaai-framework/remediate-failures/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/digipulse-engineering/gaai-framework/remediate-failures"><img src="https://agentmods.dev/badge/skills/digipulse-engineering/gaai-framework/remediate-failures.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.00043 | $0.00570 |
| Opus 5.5 | $0.00017 | $0.00228 |
| Sonnet 5.5 | $0.00009 | $0.00114 |
| Haiku 4.5 | $0.00004 | $0.00057 |
Grade A, and why
remediate-failures 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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 · 96 lines · 43 tokens per session scan A e56f86f0572e
remediate-failures is a skill published in the GitHub repository digipulse-engineering/GAAI-framework (163 stars, last pushed 6d ago), with no licence file. It adds 43 tokens to every session and 570 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-09-03.
Other skills, from other repositories
layerkit-fix-from-dry-run
Fix failed integration verification from logs, tests, and docs evidence; edit real package files, no invention.
aicrew-fix
Run the aicrew /fix fast bug fix flow in Codex (triage -> root cause -> TDD -> verify).
triage-issue
Investigate a reported bug to root cause, then emit a TDD-shaped fix plan as an issue artifact. Trigger when the user reports a bug, says "triage", asks for issue investigation, or wants a fix plan before code changes.
verify
Verify that a change really works before you claim completion.
impact-trace
For a change point (function / type / endpoint / SQL column), enumerate its real blast radius across six dimensions with a grep citation per row, then derive the regression test scope. Every impact-table row must trace to a real search hit — never a self-asserted claim.
debugging-livekit-agents
Drives a multi-turn conversation with a LiveKit agent running locally to see what it does. Use when the user says "test my agent", "try my agent", "does this work", "why did it call that tool", "it says the wrong thing when I ask X", "test this change", or whenever you have edited an agent and need to check how it…