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 prgit 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/pr)<a href="https://agentmods.dev/skills/0xrafasec/ai-workflow/pr"><img src="https://agentmods.dev/badge/skills/0xrafasec/ai-workflow/pr/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/pr"><img src="https://agentmods.dev/badge/skills/0xrafasec/ai-workflow/pr.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.00074 | $0.01797 |
| Opus 5.5 | $0.00030 | $0.00719 |
| Sonnet 5.5 | $0.00015 | $0.00359 |
| Haiku 4.5 | $0.00007 | $0.00180 |
Grade A, and why
pr 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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Open a pull request for the current branch. Assumes commits already exist (from /commit, /feature, /fix, or manual commits).
Parse Arguments
$ARGUMENTS may contain:
--draft— open the PR as a draft (GitHub's "Draft pull request" option). Use for work-in-progress where you want early CI feedback or a review conversation but aren't ready to merge.- No flags — open a normal, review-ready PR.
Guardrails
A few things that matter, and why:
- Don't force-push to
main/master. Force-pushing a shared branch rewrites history under everyone else's feet — it's the single most common way to destroy other people's work. If the user explicitly asks for it, surface the risk and confirm before proceeding. - Don't force-push any branch without explicit user confirmation. Even on feature branches, someone may have pulled or based work off it — ask first.
- Don't merge, request reviewers, add labels, or close issues as part of this skill. Those are human judgment calls that depend on team conventions and context this skill doesn't have. Open the PR; let the user drive the rest.
- Don't add Claude / Anthropic co-author tags in the PR body. Co-authorship belongs on individual commits (where configured), not repeated in PR descriptions where it just adds noise.
- If the working tree is dirty, stop and point the user at
/commit. This skill opens PRs; it doesn't commit. Mixing the two obscures what the PR actually contains.
Steps
-
Check preconditions in parallel:
git status git rev-parse --abbrev-ref HEAD git remote show origin | grep 'HEAD branch' # detect base branch (main/master)- Dirty tree? Stop and tell the user: "Working tree has uncommitted changes. Run
/commitfirst, then re-run/pr." - On
main/master? Stop and tell the user: "You're on<base>. Create a feature branch first." - Branch name doesn't match the trunk-based convention? (
feat/*,fix/*,refactor/*,docs/*,chore/*,test/*,perf/*,security/*) Warn the user and offer to rename before pushing. The convention lives in rootCLAUDE.md→ Trunk-Based Workflow. - Diff >200 lines? Run
git diff --stat <base>...HEAD -- . ':(exclude)**/tests/**' ':(exclude)**/*_test.*' ':(exclude)**/*.test.*' ':(exclude)**/test_*'; if the non-test diff exceeds ~200 lines, warn the user and suggest splitting. Proceed only if the user explicitly confirms ("ship it anyway") — this is a warning, not a hard block, since/prruns after commits already exist. - Record the base branch name (usually
main, sometimesmasterordevelop).
- Dirty tree? Stop and tell the user: "Working tree has uncommitted changes. Run
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 · 137 lines · 74 tokens per session scan A 377ade97c9ec
pr is a skill published in the GitHub repository 0xrafasec/ai-workflow (9 stars, last pushed 1mo ago), licensed MIT. It adds 74 tokens to every session and 1,797 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
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.