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/state-validationnpx skills add paruff/uFawkesAI --skill state-validationgit 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/state-validation)<a href="https://agentmods.dev/skills/paruff/ufawkesai/state-validation"><img src="https://agentmods.dev/badge/skills/paruff/ufawkesai/state-validation.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.1 | $0.00036 | $0.00357 |
| Opus 5 | $0.00018 | $0.00179 |
| Sonnet 5 | $0.00007 | $0.00071 |
| Haiku 4.5 | $0.00004 | $0.00036 |
Grade A, and why
rollback-state-validation 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 6d 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 State Validation
Load trigger:
"load rollback-state-validation skill"> DORA: Cap 5 (Operational Resilience) Token cost: Low
Purpose
Validate that the cluster and GitOps repo return to a consistent state after rollback.
Responsibilities
- Validate GitOps commit history
- Validate cluster state
- Validate no drift
Inputs
- GitOps repo
- Cluster
Outputs
rollback-state.jsoncluster-diff.txt
Validation Rules
- GitOps commit history shows rollback
- Cluster state matches previous version
- No drift detected
- All pods running previous version
Output Format
{
"skill": "rollback-state-validation",
"status": "pass | fail",
"gitops_commits": {
"total": 10,
"rollback_commit": "def456",
"latest_version": "v1.2.3"
},
"cluster_state": {
"deployment_version": "v1.2.3",
"pods_running": 3,
"pods_ready": 3
},
"drift": "none"
}
Success Criteria
- No drift
- Correct rollback state
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.
- 6d ago First seen · 67 lines · 36 tokens per session scan A be2c8f9db233
rollback-state-validation is a skill published in the GitHub repository paruff/uFawkesAI (2 stars, last pushed 13d ago), licensed MIT. It adds 36 tokens to every session and 357 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
infrastructure-publishing
Skill for the publishing infrastructure module providing academic publishing workflows including BibTeX CLI citation generation, APA/MLA citation helper functions, DOI management, Zenodo publication, arXiv submission preparation, GitHub releases, PyPI and TestPyPI package distribution, static-site deployment to GitHub…
template-publish
Publishing scripts for DOI-bearing project releases, optional mirror uploads, PyPI release validation, post-publish verification, and publication export. Use with docs/guides/publication-runbook.md for standalone GitHub + Zenodo release workflows.
template-audit
Audit and quality-gate scripts for the template research framework. Covers documentation linting, filepath audits, mock-usage checking, template drift, and confidentiality / git-guard checks.
go-live
Use when a user wants an AI-built local project pushed to GitHub and deployed live on Vercel with the least friction, while keeping git, secrets, provider setup, and live proof explicit.
worktree
Set up parallel agent sessions on independent tasks via git worktrees. Use when asked to '/worktree', 'git worktree', 'parallel branches', 'isolated branch workspace', 'work on two things at once'.
prevu-flows
Use when the user wants to mirror their local dev to a Prevu environment so they can preview changes from their phone while AFK, or when they want to share an in-progress branch as a public preview URL for a teammate, designer, or PM. Mentions: AFK, mobile preview, phone preview, mirror dev, share preview, preview…