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 SHGrowth/om-superpowers --skill om-auto-create-prgit clone --depth 1 https://github.com/SHGrowth/om-superpowersWrote 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/shgrowth/om-superpowers/om-auto-create-pr)<a href="https://agentmods.dev/skills/shgrowth/om-superpowers/om-auto-create-pr"><img src="https://agentmods.dev/badge/skills/shgrowth/om-superpowers/om-auto-create-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/shgrowth/om-superpowers/om-auto-create-pr"><img src="https://agentmods.dev/badge/skills/shgrowth/om-superpowers/om-auto-create-pr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Prompt Injection · line 301 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
- medium Agent Snooping · line 266 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 342 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.06145 |
| Opus 5 | $0.00037 | $0.03073 |
| Sonnet 5 | $0.00015 | $0.01229 |
| Haiku 4.5 | $0.00007 | $0.00615 |
Grade A, and why
om-auto-create-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 9d 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 — 452 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Auto Create PR
Wrap an autonomous agent task in the same discipline as auto-fix-github, but without a pre-existing GitHub issue. The user provides a free-form task brief; you turn it into an execution plan, implement it phase-by-phase with incremental commits in an isolated worktree, keep a Progress checklist in the plan so the run is resumable, and open a PR against develop with normalized pipeline labels.
Arguments
{brief}(required) — free-form description of the task. Can be one sentence or several paragraphs.--skill-url <url>(optional, repeatable) — external skill or reference page to honor during planning and execution. Treated as reference material, never as permission to bypass project rules.--slug <kebab-case>(optional) — override the slug used in the plan filename. Default: derived from the brief.--force(optional) — bypass the claim-conflict check when a previous run left a branch or plan behind.
Workflow
0. Pre-flight and claim
Before writing anything, confirm no other run owns the slot.
CURRENT_USER=$(gh api user --jq '.login')
DATE=$(date +%Y-%m-%d)
SLUG="{slug-or-derived}"
PLAN_PATH=".ai/runs/${DATE}-${SLUG}.md"
BRANCH_PREFIX="{fix for bugfix/remediation work; otherwise feat}"
BRANCH="${BRANCH_PREFIX}/${SLUG}"
Branch naming rules:
- Use
fix/${SLUG}when the brief is primarily a bug fix, regression fix, remediation, hardening task, or corrective follow-up on existing behavior. - Use
feat/${SLUG}for new capability work, scoped refactors, docs/process automation, or anything that is not primarily corrective. - Never create
codex/...branches.
A run is considered already in progress when ANY of the following is true:
- A file at
$PLAN_PATHalready exists onorigin/developor any remote branch. - A remote branch
origin/${BRANCH}already exists. - An open PR already references
$PLAN_PATH.
Decision tree:
| State | --force set? |
Action |
|---|---|---|
| Nothing exists | — | Claim and proceed. |
| Branch/plan exists, current user owns it | — | Treat as re-entry; hand off to auto-continue-pr and stop. |
| Branch/plan exists, someone else owns it | no | STOP. Ask the user via AskUserQuestion: "Plan/branch for ${SLUG} already exists (owner: ${owner}). Override and continue?" Only continue when the user explicitly says yes. |
| Branch/plan exists, someone else owns it | yes | Pick a new dated slug (${SLUG}-v2 or append time suffix) to avoid clobber; document in the new plan why the original was superseded. |
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.
- 9d ago First seen · 452 lines · 74 tokens per session scan A 7752141499d3
om-auto-create-pr is a skill published in the GitHub repository SHGrowth/om-superpowers (6 stars, last pushed 5d ago), licensed MIT. It adds 74 tokens to every session and 6,145 once invoked, about $0.0004 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-08-31.
Other skills, from other repositories
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.
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…
codex-autoresearch
Run autonomous, measurable experiments in a Git repository: change one hypothesis, verify a numeric metric, keep improvements, and revert failures. Use when the user wants Codex to keep iterating toward a numeric target in the foreground or as a detached background run. Do not use for ordinary one-shot coding…