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 camilooscargbaptista/cto-toolkit --skill pr-descriptiongit clone --depth 1 https://github.com/camilooscargbaptista/cto-toolkitWrote 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/camilooscargbaptista/cto-toolkit/pr-description)<a href="https://agentmods.dev/skills/camilooscargbaptista/cto-toolkit/pr-description"><img src="https://agentmods.dev/badge/skills/camilooscargbaptista/cto-toolkit/pr-description.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.00109 | $0.02264 |
| Opus 5 | $0.00055 | $0.01132 |
| Sonnet 5 | $0.00022 | $0.00453 |
| Haiku 4.5 | $0.00011 | $0.00226 |
Grade A, and why
pr-description 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 8d 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 — 210 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR Description Writer
You are a senior staff engineer writing PR descriptions that respect your reviewers' time and make the review process efficient. A great PR description answers three questions before the reviewer even looks at the code: what changed, why it changed, and what should I pay attention to.
Directive: Before writing any PR description, read the quality-standard protocol at /sessions/vigilant-blissful-darwin/mnt/skills/quality-standard/SKILL.md. Apply its self-verification, edge case awareness, and quality gates to your description before delivery.
Process
Step 1: Gather Context
Run these commands to understand the full scope of changes:
# Get the base branch (usually main or develop)
git symbolic-ref refs/remotes/origin/HEAD 2>/dev/null | sed 's@^refs/remotes/origin/@@' || echo "main"
# See all commits on this branch
git log --oneline $(git merge-base HEAD origin/main)..HEAD
# See the full diff against base
git diff origin/main...HEAD --stat
git diff origin/main...HEAD
If the diff is very large (>1000 lines), also run git diff origin/main...HEAD --stat separately to get the file-level overview first, then read the most important files individually.
Mandatory Analysis Before Writing
Before you write a single word of the PR description, complete these checks:
Lines Changed Count
- Count the total lines changed (additions + deletions)
- If >400 lines: Suggest splitting the PR into smaller, focused changesets. Explain the decomposition strategy (e.g., "data model changes first, then API layer, then UI components")
- Large PRs are harder to review, harder to bisect, and riskier to rollback
Risk Level Assessment
- Identify the risk level of this change:
- LOW: Configuration changes, documentation updates, non-functional refactors, simple bug fixes with tests
- MEDIUM: New feature code with unit and integration tests, non-critical path changes
- HIGH: Core business logic changes, database migrations, authentication/authorization changes, payment/money handling, data structure changes affecting multiple services, breaking API changes
- Write this assessment in the PR description for reviewers
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 210 lines · 109 tokens per session scan A 2766ade4424b
pr-description is a skill published in the GitHub repository camilooscargbaptista/cto-toolkit (7 stars, last pushed 5mo ago), licensed MIT. It adds 109 tokens to every session and 2,264 once invoked, about $0.0005 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
create-pr
Generate pull request descriptions, changelogs, and PR templates from git changes.
github
A writing guide for GitHub issues, pull requests, code reviews, and release notes in Zhin projects. GitHub is a service where teams track bugs, discuss changes, review code, and publish project updates.
pr-summarizer
Generate clear, complete pull request descriptions from a diff or commit list. Use when user needs to write a PR description, wants to document a change, or asks for a commit summary.
merge-to-main
Babysit a PR through CI — create, monitor, fix failures, merge when green.
github-cli
Automate GitHub workflows using the gh CLI for pull requests, issues, releases, actions, and repository management. Use when interacting with GitHub beyond basic git operations.
git-workflow
Git workflow conventions: conventional commits, branch naming, PR templates, merge strategy, and changelog generation. Use when creating commits, branches, or pull requests.