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 parisgroup-ai/imersao-ia-setup --skill pr-lifecyclegit clone --depth 1 https://github.com/parisgroup-ai/imersao-ia-setupWrote 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/parisgroup-ai/imersao-ia-setup/pr-lifecycle)<a href="https://agentmods.dev/skills/parisgroup-ai/imersao-ia-setup/pr-lifecycle"><img src="https://agentmods.dev/badge/skills/parisgroup-ai/imersao-ia-setup/pr-lifecycle/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/parisgroup-ai/imersao-ia-setup/pr-lifecycle"><img src="https://agentmods.dev/badge/skills/parisgroup-ai/imersao-ia-setup/pr-lifecycle.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.00121 | $0.01913 |
| Opus 5 | $0.00060 | $0.00957 |
| Sonnet 5 | $0.00024 | $0.00383 |
| Haiku 4.5 | $0.00012 | $0.00191 |
Grade A, and why
pr-lifecycle 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 11d 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 — 216 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR Lifecycle
End-to-end PR management: triage → analyze → validate → merge.
This skill works from whatever package/repo directory you're in — gh commands resolve the repo automatically (single-repo or monorepo).
Merge Strategy
Always squash merge. When a repo uses semantic-release on main, squash produces one clean conventional commit per PR. Feature branch WIP stays out of main. Rollback = revert one commit.
The squash commit message must follow conventional commits: feat(scope): description.
Commands
Parse the user's intent to determine which command to run. If the user says "merge PR #42", run the full merge pipeline. If they say "what PRs are open", run status. If ambiguous, default to status.
status — PR Dashboard
- Detect repo:
gh repo view --json nameWithOwner -q .nameWithOwner - List PRs:
gh pr list --state open --json number,title,author,createdAt,updatedAt,labels,reviewDecision,statusCheckRollup,headRefName,isDraft - Present summary table:
| # | Title | Author | Age | Reviews | CI | Draft | |----|-------------------|--------|-----|--------------|--------|-------| | 42 | feat(composites)… | user | 3d | APPROVED | pass | No | | 38 | fix(theme):… | user | 7d | CHANGES_REQ | fail | No | - Flag issues:
- Stale: no update > 7 days
- Blocked: failing CI or changes requested
- Ready: approved + CI passing → suggest merge
analyze <PR#> — Deep Analysis
Understand what a PR does and whether it's safe.
- Fetch PR metadata:
gh pr view <PR#> --json title,body,author,state,reviewDecision,statusCheckRollup,mergeable,baseRefName,headRefName,additions,deletions,changedFiles - Fetch diff stats:
gh pr diff <PR#> --stat - Identify affected package(s) from file paths
- Do a thorough code-review pass on the PR for code analysis
- Summarize:
- Scope: files changed, lines +/-
- Package(s) affected
- Review verdict
- Approval status
- CI status
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.
- 11d ago First seen · 216 lines · 121 tokens per session scan A 5e1e9543d439
pr-lifecycle is a skill published in the GitHub repository parisgroup-ai/imersao-ia-setup (1 stars, last pushed 28d ago), licensed MIT. It adds 121 tokens to every session and 1,913 once invoked, about $0.0006 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
pr-triage
PR triage: audit open PRs, deep review selected ones, draft and post review comments. Args: "all" to review all, PR numbers to focus (e.g. "42 57"), "en"/"fr" for language, no arg = audit only in French.
pr-workflow
Prepares branches and PRs for clean, reviewable merges.
Independent Review Synthesis
A review tool that combines findings from multiple human or AI code reviews and checks them against the diff, surrounding code, tests, and prior findings.
triage-report
Drain the .review/ report queue. Resolves un-triaged scan/audit reports (producer-agnostic — check-docs-consistency and any other scanner), dispatches the triage-report subagent (Sonnet) one report at a time for per-finding dispositions (promote / patch / dup / needs-investigation / dismiss), then the gateway absorbs…
GitHubレビューコメント対応（修正案つき）
A review workflow for handling comments on a GitHub pull request, which is a proposed code change. It groups comments by importance, records what remains unresolved, and prepares replies and small fix plans.
fresh-eyes-review
This skill should be used as a mandatory final sanity check before git commit, PR creation, or declaring work done. Triggers on "commit", "push", "PR", "pull request", "done", "finished", "complete", "ship", "deploy", "ready to merge". Catches security vulnerabilities, logic errors, and business rule bugs that slip…