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 TalonT-Org/AutoSkillit --skill analyze-prsgit clone --depth 1 https://github.com/TalonT-Org/AutoSkillitWrote 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/talont-org/autoskillit/analyze-prs)<a href="https://agentmods.dev/skills/talont-org/autoskillit/analyze-prs"><img src="https://agentmods.dev/badge/skills/talont-org/autoskillit/analyze-prs.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.00045 | $0.04597 |
| Opus 5 | $0.00023 | $0.02299 |
| Sonnet 5 | $0.00009 | $0.00919 |
| Haiku 4.5 | $0.00005 | $0.00460 |
Grade A, and why
analyze-prs 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 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.
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 — 433 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR Analysis Skill
Analyze all open PRs targeting a base branch, determine a safe merge order, assess
complexity, and produce machine-readable output for the merge-prs recipe.
When to Use
- At the start of a
merge-prsrun - User wants to understand which PRs can be merged safely and in what order
- User says "analyze PRs", "order PRs", or "assess PR complexity"
Critical Constraints
NEVER:
- Merge, close, or modify any PR
- Modify any source code files
- Create files outside
{{AUTOSKILLIT_TEMP}}/merge-prs/directory - Run subagents in the background (
run_in_background: trueis prohibited)
ALWAYS:
- Use subagents to fetch PR data in parallel
- Use
model: "sonnet"when spawning all subagents via the Task tool - Abort clearly if
ghCLI is not authenticated - Include every open PR targeting base_branch in the output — no PR is silently dropped (blocked PRs appear in ci_blocked_prs / review_blocked_prs arrays, not in the ordered prs list)
- Default to parallel batch processing: When multiple PRs are present, ALWAYS process all analysis tasks (diff fetching, overlap computation, complexity tagging) using parallel subagent batches. Processing PRs one-at-a-time without an explicit user instruction to do so is the wrong default. Up to 8 PRs should be processed in a single parallel batch; launch additional batches for larger sets.
Arguments
{base_branch} [merge_queue_data_path=<path>]
base_branch— the base branch to list PRs against (e.g.,main)merge_queue_data_path(optional) — absolute path to a JSON file containing pre-fetched merge queue data (produced byfetch_merge_queue_datarun_python step). When provided and present, read from file instead of calling GitHub GraphQL API inline.
Workflow
Step 0: Authenticate and List PRs
Run:
gh pr list --base {base_branch} --state open --json number,title,headRefName,author,body,additions,deletions,changedFiles --limit 100
If zero PRs are returned: write a summary to terminal and exit cleanly with an empty
pr_order_{ts}.json (zero PRs, no integration branch needed).
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 · 433 lines · 45 tokens per session scan A 3002667e166d
analyze-prs is a skill published in the GitHub repository TalonT-Org/AutoSkillit (5 stars, last pushed 9d ago), licensed MIT. It adds 45 tokens to every session and 4,597 once invoked, about $0.0002 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-pr-workflow
Prepare a GitHub pull request from a feature branch — branch hygiene, commit shape, title/body, verification notes, screenshots for UI work, and replies to review comments.
resolve-pr-comments
This skill should be used when user asks to "address PR comments", "resolve PR feedback", "handle review comments", "fix PR issues", "respond to PR review", or explicitly invokes "resolve-pr-comments".
review-pr
This skill should be used when user asks to "review a PR", "review pull request", "review this pr", "code review this PR", "check PR.
developer_pr_prep
Prepare branches, diffs, tests, and GitHub PR text from Developer Studio.
code-review-github
GitHub PR workflow orchestration for code review — list PRs, post comments, apply labels, and guarded auto-merge.
codeflow-maintainer
OpenClaw-only maintainer PR workflow modes and skills. For OpenCoven/coven PR creation, redirect to skills/pr-agent, the Coven PR Readiness Agent.