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 agentmods add skills/soulcodex/agentic/pull-request-automationnpx skills add soulcodex/agentic --skill pull-request-automationgit clone --depth 1 https://github.com/soulcodex/agenticWhat 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 | $0.00065 | $0.01056 |
| Opus 5 | $0.00032 | $0.00528 |
| Sonnet 5 | $0.00013 | $0.00211 |
| Haiku 4.5 | $0.00006 | $0.00106 |
Grade A, and why
pull-request-automation 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 2d 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 — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pull Request Automation Skill
Step 1 — Audit Current PR Workflow
Check what already exists:
- Is there a
.github/pull_request_template.md? - Is there a
.github/CODEOWNERSfile? - Are there existing labelling or size-check actions?
- Are branch protection rules configured for
main?
Step 2 — PR Description Template
Create .github/pull_request_template.md:
## Summary
<!-- What does this PR do? Why? -->
## Changes
<!-- Bullet list of key changes -->
## Test Plan
- [ ] Unit tests added / updated
- [ ] Manual testing performed: <describe steps>
- [ ] Breaking changes documented
## Related Issues
Closes #
Keep the template short — the goal is consistency, not bureaucracy.
Step 3 — Auto-Labelling
Use actions/labeler to apply labels automatically based on changed file paths:
# .github/labeler.yml
frontend:
- changed-files:
- any-glob-to-any-file: "src/features/**"
backend:
- changed-files:
- any-glob-to-any-file: "internal/**"
docs:
- changed-files:
- any-glob-to-any-file: "docs/**"
infrastructure:
- changed-files:
- any-glob-to-any-file: "deployments/**"
# .github/workflows/labeler.yml
name: Label PR
on: [pull_request_target]
jobs:
label:
runs-on: ubuntu-latest
steps:
- uses: actions/labeler@v5
with:
repo-token: ${{ secrets.GITHUB_TOKEN }}
Step 4 — CODEOWNERS
Define ownership in .github/CODEOWNERS. GitHub requests reviews from owners
automatically when their files are touched:
# Global fallback
* @org/platform-team
# Frontend
/src/features/ @org/frontend-team
# Infrastructure
/deployments/ @org/infra-team
/build/ @org/infra-team
# Database migrations
/internal/infrastructure/migrations/ @org/dba-team
Step 5 — PR Size Check
Flag PRs that are too large to review effectively. Add a size-check action:
# .github/workflows/pr-size.yml
name: PR Size Check
on: [pull_request]
jobs:
size:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
with: { fetch-depth: 0 }
- name: Check PR size
run: |
LINES=$(git diff --stat origin/${{ github.base_ref }}...HEAD | tail -1 | grep -oE '[0-9]+ insertions' | grep -oE '[0-9]+' || echo 0)
if [ "$LINES" -gt 500 ]; then
echo "::warning::PR adds $LINES lines. Consider splitting into smaller PRs."
fi
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.
- 2d ago First seen · 169 lines · 65 tokens per session scan A 4ce09126a9d9
pull-request-automation is a skill published in the GitHub repository soulcodex/agentic (10 stars, last pushed 2d ago), licensed MIT. It adds 65 tokens to every session and 1,056 once invoked, about $0.0003 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
github-multi-repo
Multi-repository coordination, synchronization, and architecture management across many GitHub repos. Use when changes span several repositories, keeping repos in sync, or planning cross-repo architecture and dependency work.
issue
Use when starting a chain from a GitHub issue — turning an issue URL or number into a triaged, planned, dispatched, and reviewed pull request. Classifies the thread (bug → root-cause discipline, feature → plan chain, question → drafted reply), synthesizes a spec from the issue's own acceptance criteria, then runs the…
pr
Use when reviewing an incoming GitHub pull request — runs the multi-level (L1-L5) audit against the PR's real diff range, posts findings as one batched review (inline, summary, or local-only), offers the standard fix chain on NEEDSFIX, and optionally merges. The maintainer-side counterpart to /hyperflow:issue. Trigger…
research-repository
Build a repository that makes findings findable, reusable, and cumulative across teams. Use when the same research keeps getting redone. For synthesising one study, use affinity-diagram.
survey-design
Design unbiased survey instruments — question wording, scales, and sampling — to measure attitudes at scale. Use when you need quantitative breadth. For behavioural experiments, use a-b-test-design (prototyping-testing).
design-negotiation
Advocate for design quality, scope, and timeline with partners and leadership using evidence and shared goals. Use in the conversation itself. For the commercial vocabulary behind it, use business-design (ux-strategy).