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.
git 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/commands/paruff/ufawkesai/release)<a href="https://agentmods.dev/commands/paruff/ufawkesai/release"><img src="https://agentmods.dev/badge/commands/paruff/ufawkesai/release/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/commands/paruff/ufawkesai/release"><img src="https://agentmods.dev/badge/commands/paruff/ufawkesai/release.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.00039 | $0.02757 |
| Opus 5.5 | $0.00016 | $0.01103 |
| Sonnet 5.5 | $0.00008 | $0.00551 |
| Haiku 4.5 | $0.00004 | $0.00276 |
Grade A, and why
release 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.
How it starts
The opening of the file, as written. The whole thing — 317 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release
Invoke when: Tests passing + review approved on a releasable increment. Cadence: weekly (Thursday) or on a completed increment — not chosen by relevance. DORA: AI Capability 4: Strong version control practices + Core: Continuous Delivery Token cost: Low–Medium
This is a command, not a skill: it runs on a calendar, so it is invoked
deliberately (/release) rather than selected by skill relevance.
Trigger Conditions
| Trigger | Description |
|---|---|
| Weekly cadence | Thursday: if increment is shippable, release it |
| Feature complete | All acceptance criteria from discovery-brief.md met |
| Hotfix | Change fail rate event resolved, patch ready |
| Documentation release | No code change required — doc, Dojo lab, or decision post counts |
Pre-conditions
- All tests passing (
test-report.md:status: pass) - Code review approved (
review-report.md:status: approved) - Evidence gate passed (
verification-report.md: noverified_falseclaims) - Cross-validation passed (
.agents/logs/cross-validation-report.md:status: pass) - Infra changes only: deployment readiness confirmed by the human releaser — no
deliveryagent or skill exists in this repository, so this is a human check by design - CHANGELOG.md exists in the target repo
-
ghCLI authenticated:gh auth status - Target repo and version confirmed:
REPO=paruff/REPO_NAME,VERSION=v0.x.y
Load trigger:
"load release skill"> DORA: AI Capability 4: Strong version control practices + Core: Continuous Delivery Token cost: Low
Purpose
Make "one new thing a week" a checklist execution, not a creative decision each time. Source material is written once (README "What This Is" + "Status" sections) and reformatted four times: CHANGELOG entry, GitHub Release notes, dev.to post, LinkedIn post. The fifth output — ufawkes.dev stack page update — is a one-line front matter change.
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 Changed 2b1b7aa1dfd9
- 14d ago First seen · 317 lines · 39 tokens per session scan A 5c9ec57cfe00
release is a command published in the GitHub repository paruff/uFawkesAI (2 stars, last pushed today), licensed MIT. It adds 39 tokens to every session and 2,757 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-28.
Other commands, from other repositories
customer-changelog-check
Audit whether user-visible changes in the current session have matching CHANGELOG.md entries; report MISSING with suggested lines; --fix auto-appends.
rollback
Restore the previous Cloudflare deployment and verify recovery. Fires when a deploy broke prod and you need the last-good version back.
OPSX: Archive
Archive a completed change in the experimental workflow.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
release-plan
A release-planning command for a software change. It documents the release scope, rollback plan, gradual or full rollout, and monitoring before waiting for human approval.
rally-merge-pr
You are merging the current branch's PR and syncing the feature branch with main. Follow each step exactly.