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 paruff/uFawkesAI --skill commit-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/commit-validation)<a href="https://agentmods.dev/skills/paruff/ufawkesai/commit-validation"><img src="https://agentmods.dev/badge/skills/paruff/ufawkesai/commit-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.00027 | $0.00362 |
| Opus 5 | $0.00014 | $0.00181 |
| Sonnet 5 | $0.00005 | $0.00072 |
| Haiku 4.5 | $0.00003 | $0.00036 |
Grade A, and why
gitops-commit-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 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: GitOps Commit Validation
Load trigger:
"load gitops-commit-validation skill"> DORA: Cap 4 (CI/CD Automation) Token cost: Low
Purpose
Validate that OBS produces correct Git commits.
Responsibilities
- Validate commit messages
- Validate file structure
- Validate diff correctness
Inputs
- GitOps repo
Outputs
commit-validation.json
Commit Message Convention
chore(deploy): update <service> to <version>
- Updated image tag to v1.3.0
- Updated image digest to sha256:abc123
- Affected environments: dev, staging, prod
Validation Rules
- Commit message follows convention
- Files changed correctly
- Diff shows correct changes
- No unintended changes
- Commit signed (if required)
Output Format
{
"skill": "gitops-commit-validation",
"status": "pass | fail",
"commit": {
"sha": "abc123",
"message_valid": true,
"files_changed": 3,
"diff_correct": true,
"unintended_changes": 0
}
}
Success Criteria
- Correct commit structure
- Commit message follows convention
- No unintended changes
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 · 73 lines · 27 tokens per session scan A ef3828bbc585
gitops-commit-validation is a skill published in the GitHub repository paruff/uFawkesAI (2 stars, last pushed 15d ago), licensed MIT. It adds 27 tokens to every session and 362 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-09-03.
Other skills, from other repositories
ship
Use when a change is ready to land. Runs the full sequence — branch, quality gate, commit, push, PR — so nothing gets skipped.
publish-to-github
Use this skill when the user is ready to push their local AI skill or rule repository to GitHub for the first time. This includes running git init and the initial commit, creating the GitHub repository via the gh CLI or manual browser steps, setting the repository description and Topics tags, and confirming the push…
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a semantic version bump…
git-advanced-workflows
Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.
chinese-commit-conventions
A Chinese-language guide to Conventional Commits, a format for writing consistent Git commit messages, plus related changelog, commit-checking, and commit-helper configuration.
work-unit-commits
Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.