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 gabrieldabbah/genesis --skill generate-prgit clone --depth 1 https://github.com/gabrieldabbah/genesisWrote 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/gabrieldabbah/genesis/generate-pr)<a href="https://agentmods.dev/skills/gabrieldabbah/genesis/generate-pr"><img src="https://agentmods.dev/badge/skills/gabrieldabbah/genesis/generate-pr.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.00092 | $0.04620 |
| Opus 5 | $0.00046 | $0.02310 |
| Sonnet 5 | $0.00018 | $0.00924 |
| Haiku 4.5 | $0.00009 | $0.00462 |
Grade C, and why
generate-pr scanned grade C with 1 finding 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 7d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
gitleaks dir "$TREE" --no-banner --redact --exit-code 1; echo "exit=$?"; rm -rf "$TREE" How it starts
The opening of the file, as written. The whole thing — 336 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate a Pull Request
When this skill runs
Only when the operator invokes it — /generate-pr, or an explicit request to open or fill a PR in their
own words. A pull request exists for one purpose: promoting the working branch to the branch that releases.
A PR is never opened on an agent's own initiative — not to trigger CI, not to summarise a branch, not because
the work looks finished. Reading PR state to answer a question (gh pr list) is ordinary; creating one is not.
Pushing to the working branch is a separate act under its own rule (the git-commit skill) and never implies a
PR.
Overview
Produce a fully-filled pull request — every applicable section of
.github/pull_request_template.md, every checkbox the
evidence supports — and open or update the PR.
Portability
Every command here is POSIX shell and runs on macOS, Linux, WSL2 and Git Bash — no GNU-only flags, so BSD userland on macOS behaves identically. On native Windows without Git for Windows, Claude Code runs commands through PowerShell, which cannot execute them; translate them or install Git for Windows.
git is required. gh is optional — without it, or unauthenticated, the skill writes the finished body to
out/pr-body.md and prints the command to run, which is also how you test it without opening a real PR.
jq is optional and every use below has a fallback, because neither macOS nor Windows ships it.
Branch policy — read it, do not assume it
Repositories differ: trunk-based, a long-lived integration branch, short-lived feature branches, Git Flow. Establish this repository's flow before opening anything, from what the repository actually says:
git rev-parse --abbrev-ref HEAD # where you are
git branch -a --format='%(refname:short)' # what exists
git symbolic-ref --short refs/remotes/origin/HEAD 2>/dev/null # the remote's default branch
grep -rniE 'branch|pull request' CLAUDE.md CONTRIBUTING.md .github/*.md 2>/dev/null | head
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.
- 7d ago First seen · 336 lines · 92 tokens per session scan C 81c8de73cba5
generate-pr is a skill published in the GitHub repository gabrieldabbah/genesis (4 stars, last pushed 1mo ago), licensed MIT. It adds 92 tokens to every session and 4,620 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
pr-watch
Local PR watcher. Monitors CI status, automatically fixes failing checks by reading failure logs and applying targeted fixes, then optionally merges when all checks pass. Local CLI analog to Claude Code's cloud auto-fix feature.
deploy-steward
Mainline deploy steward. Consumes ready PRs, owns a lease on mainline landing, refreshes PR state, updates stale branches, waits for CI and deploy gates, merges or queues one candidate at a time, and opens repair tasks for failures.
merge-review
Reviews pending fleet worktree merges before they're accepted. Reads the merge-check queue, detects file-level conflicts between branches, proposes a safe merge order, and surfaces reconciliation plans for overlapping changes.
create-pull-request
Use when asked to create or update a PR, revise its description, or link issue references to its body. Not for multi-PR stacks: use gate-and-merge. Not for releases: use git-workflow-and-versioning.
commit-push-pr
Use when asked to commit, push a feature branch, and open or update a pull request with gh in one pass. Not for a push with no PR: use commit-push. Not for a PR body alone: use create-pull-request.
commit
Use when asked to commit changes, create a typed branch, format history for a changelog, or rewrite messages of HEAD or an unpushed range. Not for pushing or a PR: use commit-push or commit-push-pr.