Borrowing it
Nothing to install: this file belongs to Alireza29675/teamctl. 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/Alireza29675/teamctl/main/.claude/agents/pr-summarizer.mdgit 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/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/agents/alireza29675/teamctl/pr-summarizer"><img src="https://agentmods.dev/badge/agents/alireza29675/teamctl/pr-summarizer.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.00090 | $0.00511 |
| Opus 5.5 | $0.00036 | $0.00204 |
| Sonnet 5.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 1mo 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.
- 1mo 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 2d ago), licensed MIT. It adds 90 tokens to every session and 511 once invoked, about $0.0004 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 agents, from other repositories
Inspektor jakości z checklista
QA Quality to audytor jakości kodu i zgodności ze specyfikacja. Jego misja: zweryfikować czy artefakt robi to co powinien, czy testy pokrywają scenariusze, czy kod jest czytelny i wydajny. Działa równolegle do QA Security ale z całkowicie inna perspektywa - poprawność zamiast bezpieczeństwa.
Archeolog działajacego kodu
Researcher GitHub przeszukuje repozytoria open-source w poszukiwaniu działajacego kodu, architektury i wzorców. Jego misja: dostarczać dowody w formie kodu, nie opinie. Unika 90% porzuconych projektów i rekomenduje TOP 5 z health scoreami.
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…
claude-codebase-context
Internal Claude subagent for codebase-aware code review — quality patterns, CLAUDE.md compliance, git history analysis, and documentation coverage. Has native codebase access (Read, Grep, Glob, Bash) to compare against project conventions, read rule files, and inspect commit history. Launched automatically by council…
bug-detector
Bug detection agent for CI: analyzes PR diffs for logic errors, null/undefined handling, race conditions, off-by-one errors, and edge cases. Uses git blame for historical context.
code-simplifier
Code quality agent for CI: identifies code duplication, unnecessary complexity, dead code, readability issues, and opportunities for simplification in PR diffs.