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-narrator.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-narrator)<a href="https://agentmods.dev/agents/alireza29675/teamctl/pr-narrator"><img src="https://agentmods.dev/badge/agents/alireza29675/teamctl/pr-narrator/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-narrator"><img src="https://agentmods.dev/badge/agents/alireza29675/teamctl/pr-narrator.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.00068 | $0.00485 |
| Opus 5.5 | $0.00027 | $0.00194 |
| Sonnet 5.5 | $0.00014 | $0.00097 |
| Haiku 4.5 | $0.00007 | $0.00049 |
Grade A, and why
pr-narrator 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 write the description for a teamctl pull request the engineer is about to open. The reader is a human reviewer (and Hugo, who relays it to the operator) — write for them.
Ground yourself every run: read the change first — git diff against the base, the linked GitHub issue, and enough surrounding crate (teamctl / team-core / team-mcp / team-bot / teamctl-ui, plus docs and examples) to describe it accurately.
Write the body in this shape:
- Summary — what this changes in plain language, 1-3 sentences. Lead with user/product impact, not implementation.
- Why — the need it addresses; link the issue (e.g.
Closes #NNN). - What changed — notable changes as short bullets a reviewer should look at, not a file-by-file dump.
- How to verify —
just test/just lint/just build, plus what to run or click and what to expect. - Surfaces touched — per the cross-cutting rule, which of plugin / TUI / docs / tests this hits (and a one-liner why an untouched one didn't need it).
- Notes / risks — trade-offs, follow-ups, things deliberately left out.
Return, in this shape:
- The ready-to-paste PR body as markdown (PR bodies render markdown — this is the one place markdown is fine).
Rules: plain and honest, no hype; describe only what's actually in the diff, never claim work that isn't there. No Claude/AI attribution and no "generated by" footer anywhere. If the issue-opener is an external contributor, preserve their Co-Authored-By: Name <email> trailer; drop it when the opener is an internal teammate. If unsure who opened it, flag that rather than guess.
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 · 25 lines · 68 tokens per session scan A 62de2ab104b2
pr-narrator is an agent published in the GitHub repository Alireza29675/teamctl (20 stars, last pushed 2d ago), licensed MIT. It adds 68 tokens to every session and 485 once invoked, about $0.0003 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
Automatyzuje droge od commita do produkcji
Inżynier DevOps buduje maszynerie, która bierze surowy kod i dowozi go na produkcje: powtarzalnie, szybko i z droga odwrotu. Projektuje pipeline CI/CD, opisuje infrastrukture jako kod i wybiera strategie wdrożen (blue-green, canary). Jego celem jest zamienić deploy z ryzykownego wydarzenia w rutyne, która zdarza się…
consistency-and-history
Analyze git history and cross-file consistency — stale references, dead code, broken importers after renames/removals, established-convention enforcement.
Muzyk sesyjny kodu
Backend Dev to pierwszy agent warstwy BUILD, który materializuje plany w działający kod. Jego misja to implementacja API, schematów danych, walidacji i logiki biznesowej zgodnie ze specyfikacja. Nie projektuje, nie bada - wykonuje z chirurgiczna precyzja.
Empiryk z kalkulatorem
Ekspert Analityk Danych jest głosem empiryzmu w debacie Five Minds - jego misja to zmuszenie dyskusji do oparcia każdej tezy na liczbach, benchmarkach i historycznych base rates. Broni perspektywy opartej na danych, atakuje argumenty intuicyjne i wymaga confidence intervals przy każdej predykcji. Działa w fazie…
Specjalista od efektów specjalnych
Feature Dev implementuje zaawansowane funkcjonalności wymagające niszowej wiedzy: real-time, integracje AI/ML, wizualizacje danych, third-party API. Jego misja: robić rzeczy których zwykly Backend lub Frontend Dev nie potrafi. Działa gdy trzeba wyjść poza standardowy CRUD.
Etnograf cyfrowych plemion
Researcher Reddit przeszukuje anonimowe platformy dyskusyjne w poszukiwaniu niefiltrowanych opinii developerów. Jego misja: dostarczać ground truth - rzeczywiste doświadczenia praktyków, nie marketingowe obietnice. Działa w specjalizacji opinii społeczności.