Borrowing it
Nothing to install: this file belongs to CES-Ltd/TitanX. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/CES-Ltd/TitanX/main/.claude/skills/pr-automation/SKILL.mdgit clone --depth 1 https://github.com/CES-Ltd/TitanXWrote 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/ces-ltd/titanx/pr-automation)<a href="https://agentmods.dev/skills/ces-ltd/titanx/pr-automation"><img src="https://agentmods.dev/badge/skills/ces-ltd/titanx/pr-automation/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/ces-ltd/titanx/pr-automation"><img src="https://agentmods.dev/badge/skills/ces-ltd/titanx/pr-automation.svg" alt="Reviewed on agentmods" width="80" 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.00056 | $0.08153 |
| Opus 5.5 | $0.00022 | $0.03261 |
| Sonnet 5.5 | $0.00011 | $0.01631 |
| Haiku 4.5 | $0.00006 | $0.00815 |
Grade A, and why
pr-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 2mo 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 — 793 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR Automation
Orchestrate the full PR automation lifecycle using a label-based state machine. Each invocation performs at most one "heavy" action (review or fix), then exits. Pure skips continue within the same session to find the next eligible PR.
Announce at start: "I'm using pr-automation skill to process PRs."
Usage
/pr-automation
No arguments required. The daemon script scripts/pr-automation.sh manages the automation loop.
Configuration
TRUSTED_CONTRIBUTORS_TEAM: detected from REPO org (e.g. iOfficeAI/trusted-contributors)
CRITICAL_PATH_PATTERN: env var, default in scripts/pr-automation.conf
LARGE_PR_FILE_THRESHOLD: env var (default: 50), also in scripts/pr-automation.conf
PR_DAYS_LOOKBACK: env var (default: 7), also in scripts/pr-automation.conf
REPO is detected automatically at runtime — do not hardcode it:
REPO=$(gh repo view --json nameWithOwner --jq '.nameWithOwner')
ORG=$(echo "$REPO" | cut -d'/' -f1)
Label State Machine
| Label | Meaning | Terminal? |
|---|---|---|
bot:reviewing |
Review in progress (mutex) | No |
bot:ready-to-fix |
CONDITIONAL review done, waiting for bot to fix next session | No |
bot:fixing |
Fix in progress (mutex) | No |
bot:ci-waiting |
CI failed and author notified — snoozed until author pushes new commits | No |
bot:needs-rebase |
Merge conflict that bot cannot auto-resolve — author must rebase | No |
bot:needs-human-review |
Blocking issues — human must intervene | Yes |
bot:ready-to-merge |
Bot done, code is clean — human just needs to confirm and merge | Yes |
bot:done |
Auto-merged by bot | Yes |
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.
- 2mo ago First seen · 793 lines · 56 tokens per session scan A 7af82f201a39
pr-automation is a skill published in the GitHub repository CES-Ltd/TitanX (49 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 56 tokens to every session and 8,153 once invoked, about $0.0002 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-30.
Other skills, from other repositories
release
Prepare, approve, execute, and independently verify a versioned release through a project-owned exact-command profile.
github-issue-to-pr
Implement one scafld-governed repository issue with normal host tools, prove the tested change through its finalize wall, and optionally publish the exact pull request through scoped provider authority with readback.
github
Read or synchronize bounded GitHub issues, threads, and pull requests through the GitHub connector, with scoped authority and readback.
github-issue-triage
Read, analyze, and draft high-signal GitHub issue responses from bounded provider evidence without silently mutating the repository.
github-pr-review
Review one exact GitHub pull-request head from bounded changed-file patches and check evidence, producing source-line findings without posting or claiming tests ran.
revert
Undo edits a run made, by their call ids, together. Each file returns to what it held before them, all or none, and a file that changed since is refused, naming it.