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 0xrafasec/ai-workflow --skill commitgit clone --depth 1 https://github.com/0xrafasec/ai-workflowWrote 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/0xrafasec/ai-workflow/commit)<a href="https://agentmods.dev/skills/0xrafasec/ai-workflow/commit"><img src="https://agentmods.dev/badge/skills/0xrafasec/ai-workflow/commit/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/0xrafasec/ai-workflow/commit"><img src="https://agentmods.dev/badge/skills/0xrafasec/ai-workflow/commit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00068 | $0.01418 |
| Opus 5.5 | $0.00027 | $0.00567 |
| Sonnet 5.5 | $0.00014 | $0.00284 |
| Haiku 4.5 | $0.00007 | $0.00142 |
Grade A, and why
commit 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.
How it starts
The opening of the file, as written. The whole thing — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Stage and commit the current working tree.
Guardrails
A few things that matter, and why:
- Keep commits focused — one concern per commit. A bug fix and a refactor, even if both are tiny, go in separate commits. This is what makes
git logandgit blameuseful later, and it's what lets reviewers (andgit revert) isolate one change without dragging in others. - Don't push, force-push, amend, reset, or touch the remote. Those belong to
/pror the user. This skill's job ends at the local commit — staying in that lane keeps the two operations reviewable independently. - Don't bypass pre-commit hooks with
--no-verify. Hooks exist to catch real problems (lint, types, secrets). If one fails, the commit didn't happen — fix the underlying issue and commit again. Do not--amendafter a hook failure: since the commit didn't land,--amendwould rewrite the previous commit, quietly overwriting earlier work. - Stage explicit paths, not
git add ./-A. Wildcards sweep in whatever's lying around —.env, credentials, build artifacts, half-finished scratch files. Naming paths explicitly keeps that stuff out. - Follow the global CLAUDE.md rule: "Split commits by logical concern; each commit leaves the codebase working."
Steps
-
Survey the working tree — run in parallel:
git status git diff --stat git log --oneline -10status+diff --statshow the full picture of what changed.log --oneline -10shows the repo's existing commit style so your messages match it.- If the tree is clean (nothing staged, nothing unstaged, no untracked relevant files), stop and tell the user there's nothing to commit.
-
Read the actual diffs — for any files where the nature of the change isn't obvious from the path, run
git diff <file>(orgit diff --cached <file>for already-staged changes) so you understand what each hunk does. Don't guess — a file namedauth.gocould contain a typo fix or a complete rewrite.
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 · 100 lines · 68 tokens per session scan A 346c4e325696
commit is a skill published in the GitHub repository 0xrafasec/ai-workflow (9 stars, last pushed 1mo ago), licensed MIT. It adds 68 tokens to every session and 1,418 once invoked, about $0.0003 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-08-31.
Other skills, from other repositories
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
repo-sync
Manage automatic Git syncing on macOS with repo-sync. Use only when the user explicitly invokes /repo-sync.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
engineer-bot-ops
A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…