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 agentmods add skills/paruff/ufawkesai/triggernpx skills add paruff/uFawkesAI --skill triggergit clone --depth 1 https://github.com/paruff/uFawkesAIWrote 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/paruff/ufawkesai/trigger)<a href="https://agentmods.dev/skills/paruff/ufawkesai/trigger"><img src="https://agentmods.dev/badge/skills/paruff/ufawkesai/trigger.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 | $0.00030 | $0.00324 |
| Opus 5 | $0.00015 | $0.00162 |
| Sonnet 5 | $0.00006 | $0.00065 |
| Haiku 4.5 | $0.00003 | $0.00032 |
Grade A, and why
rollback-triggering 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 3d 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
Skill: Rollback Triggering
Load trigger:
"load rollback-triggering skill"> DORA: Cap 5 (Operational Resilience) Token cost: Low
Purpose
Trigger a controlled deployment failure to test rollback behavior.
Responsibilities
- Inject invalid manifests
- Inject failing health checks
- Validate rollback trigger
Inputs
- Failure scenario
Outputs
rollback-trigger.json
Failure Injection Methods
| Method | Description |
|---|---|
| Invalid manifest | Deploy manifest with invalid YAML |
| Wrong image | Deploy non-existent image tag |
| Failing health check | Configure failing liveness probe |
| Resource exhaustion | Deploy with insufficient resources |
Validation Rules
- Failure injected successfully
- Rollback triggered by controller
- Previous version restored
Output Format
{
"skill": "rollback-triggering",
"status": "success",
"injection_method": "invalid_manifest",
"rollback_triggered": true,
"time_s": 30
}
Success Criteria
- Rollback triggered correctly
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.
- 3d ago First seen · 64 lines · 30 tokens per session scan A 067a4c896810
rollback-triggering is a skill published in the GitHub repository paruff/uFawkesAI (2 stars, last pushed 11d ago), licensed MIT. It adds 30 tokens to every session and 324 once invoked, about $0.0002 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
planning-with-files
Persistent file-based planning for multi-step AI-agent work. Keeps taskplan.md, findings.md, and progress.md on disk; lifecycle hooks inject selected project planning context. Automatic recovery reads project planning files only. Explicit session-catchup.py --metadata reads same-project local agent session records and…
infrastructure-overview
Top-level skill for the research template infrastructure layer. Use in Cursor, Claude Code, or similar agents when editing or importing anything under infrastructure/, understanding the two-layer architecture, or wiring build/validation/rendering/publishing. Covers module discovery, import patterns, thin…
template-academic-paper
Template-native manuscript planning, outline, drafting, revision, formatting, citation check, and AI-use disclosure routing. USE WHEN the user asks to write, outline, revise, format, or prepare a paper inside the Research Project Template.
template-code-development
Standards-compliant code for the Research Project Template — infrastructure or project src/, thin orchestrators, type hints, no mocks. USE WHEN implementing an algorithm, utility, analysis method, optimizer, new module in projects//src or infrastructure/, or user says add code following template architecture — even…
template-reproducibility-audit
Deterministic reproducibility audit — fixed seeds, regenerate-from-clean, double-run diff before Zenodo/arXiv/release. USE WHEN outputs drift between runs, "worked on my machine", need regenerate-from-clean proof, or pre-release reproducibility check — even without naming docs/prompts.
template-infrastructure-module
Add or extend generic infrastructure/ packages — Layer 1 modules with SKILL.md, AGENTS.md, tests in tests/infratests/, 60% coverage. USE WHEN new reusable package under infrastructure/, extending validation/rendering/llm, or skill manifest entry — even without infrastructuremodule prompt.