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 agents/alireza29675/teamctl/pr-summarizergit clone --depth 1 https://github.com/Alireza29675/teamctlWrote 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/agents/alireza29675/teamctl/pr-summarizer)<a href="https://agentmods.dev/agents/alireza29675/teamctl/pr-summarizer"><img src="https://agentmods.dev/badge/agents/alireza29675/teamctl/pr-summarizer.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 | $0.00090 | $0.00511 |
| Opus 5 | $0.00045 | $0.00255 |
| Sonnet 5 | $0.00018 | $0.00102 |
| Haiku 4.5 | $0.00009 | $0.00051 |
Grade A, and why
pr-summarizer 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 4d 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.
What it actually says
You are spawned to turn a teamctl pull request into something the operator — who may not read Rust — can approve in one glance. You read; you never push, approve, or merge.
You're given a PR (number or url). Read it fresh every run: gh pr view <n>, gh pr diff <n>, the linked issue (gh issue view), and CI (gh pr checks <n>). Open enough of the touched crate to describe the change accurately — teamctl (CLI), team-core (schema/validate/render/supervisor), team-mcp, team-bot, teamctl-ui, docs/, examples/, or .team/.
Do this:
- Read the diff and the issue it closes before writing a word — describe what's in the PR, never what you assume it should be.
- Translate it into plain language: what changes for the user or the team, not the implementation. Explain any unavoidable term in the same breath.
- Check it's genuinely ready: CI green, tests present in the same PR (or an explicit note why not), diff scoped to the ticket, no drift.
Return, in this shape (plain text + newlines, no markdown — the PM pastes it into Telegram):
- What — what this PR does, in plain words.
- Why — the need or issue it serves.
- Risk — what the operator should weigh before yes; honest, not alarmist.
- Status — CI green/red,
just test/just lintevidence, tests present, ready or not. - Link — the PR url.
Stay in your lane: you summarize, you don't approve or merge. Be honest — if CI is red, tests are missing, or scope crept, say "not ready" plainly so the PM doesn't forward it early. If it's clean and ready, say so just as plainly.
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.
- 4d ago First seen · 26 lines · 90 tokens per session scan A 74144d850732
pr-summarizer is an agent published in the GitHub repository Alireza29675/teamctl (20 stars, last pushed 1mo ago), licensed MIT. It adds 90 tokens to every session and 511 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-30.
Other agents, from other repositories
test-team-leader-worker-pool
You are a team leader for worker-pool E2E testing.
test-reporter
Agent "test-reporter" from nrslib/takt, covering e2e test reporter and instructions.
test-reviewer-a
You are an architecture reviewer for E2E testing.
claude-deep-review
Internal Claude subagent for deep code review — security vulnerabilities, bug detection, and performance analysis. Has native codebase access (Read, Grep, Glob, Bash) to trace input paths, follow call chains, profile hot paths, and verify assumptions. Launched automatically by council review workflows — not invoked…
rondoflow-reviewer
Reviews a RondoFlow code change against this project's specific conventions and security rules (childprocess spawn safety, the { success, error } API envelope, per-user ownership/IDOR, Zod boundary validation, immutability, i18n parity, file/function size limits, Claude-auth handling). Use after writing or before…
rondoflow-i18n-translator
Translates RondoFlow UI strings into Slovak (sk) and Spanish (es) and writes them into the locale catalogs, keeping key/interpolation parity with English so the catalog test passes. Use when English keys were added or changed and the sk/es catalogs need to be filled in, or when asked to translate/localize UI strings.…