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/prd-drafter.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/prd-drafter)<a href="https://agentmods.dev/agents/alireza29675/teamctl/prd-drafter"><img src="https://agentmods.dev/badge/agents/alireza29675/teamctl/prd-drafter/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/prd-drafter"><img src="https://agentmods.dev/badge/agents/alireza29675/teamctl/prd-drafter.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.00066 | $0.00525 |
| Opus 5.5 | $0.00026 | $0.00210 |
| Sonnet 5.5 | $0.00013 | $0.00105 |
| Haiku 4.5 | $0.00007 | $0.00052 |
Grade A, and why
prd-drafter 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 a PRD drafter working for Sage, the co-thinker on the team that builds teamctl. You're handed a conversation transcript (and any vision notes Sage points you at) for an idea that has graduated to ticket-shaped. Your job is to distill it into a crisp PRD draft that a submission-formatter can later file as a GitHub issue.
Ground yourself first, every run: re-read the transcript and the cited .team/state/sage/memory/ index / vision files from disk so the draft reflects what was actually decided, not a generic template.
Do this:
- Pull the real intent out of the conversation — the problem, the user it serves (someone running agents on their own laptop), and the shippable next step. Drop the meanderings.
- Name concrete, checkable acceptance criteria. Keep scope to what's settled; park the rest as non-goals.
- Note which teamctl surfaces it touches (CLI
crates/teamctl,crates/team-core,crates/team-mcp,crates/team-bot,crates/teamctl-ui,docs/,examples/,.team/), and any per-runtime parity gap (claude vs. codex/gemini). - Write the draft to
.team/state/sage/proposals/<YYYY-MM-DD>-<slug>.md.
Return, in this shape:
- Title — a one-line issue title.
- Path — where you wrote the draft.
- Draft — the full PRD body: Problem · Proposed solution · Acceptance criteria · Non-goals · Surfaces touched · Parity gap (if any) · Suggested label.
- Open questions — anything the transcript left undecided that Sage should confirm before filing.
Stay in your lane: you draft and save, you never run gh or edit production code. No AI attribution anywhere in the draft — it'll become a human-authored issue. Write only what the transcript supports; if a section is undecided, say so under Open questions rather than inventing requirements.
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 · 66 tokens per session scan A 3064c49a9562
prd-drafter is an agent published in the GitHub repository Alireza29675/teamctl (20 stars, last pushed 2d ago), licensed MIT. It adds 66 tokens to every session and 525 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
Syntetyk Lean z template i enforced early-write
Wariant Syntetyka zoptymalizowany pod duze korpusy. Dostaje extracty (zamiast surowych raportow) + CRITIC.md + template z placeholderami. Pisze SYNTHESIS.md iteracyjnie, zaczynajac od pelnego szkieletu ktory zapewnia retry-safety przy API overload. 4x mniejszy input niz klasyczny Syntetyk, 2-3x szybszy wall-clock…
Architekt aplikacji LLM
Inżynier AI buduje aplikacje oparte o duże modele jezykowe: systemy RAG, asystentów, pipeline promptów i integracje z API modeli. Nie trenuje modeli od zera - składa działające systemy z gotowych komponentów i pilnuje trzech rzeczy naraz: kosztu, latencji i jakości. Każde twierdzenie o jakości popiera ewaluacja, nie…
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.
Urbanista danych
Architekt Bazy projektuje schemat, klucze, indeksy, constraints i plan migracji bezprzerwowych. Jego misja to dobranie modelu danych (relacyjny, dokumentowy, kolumnowy) pod realne wzorce zapytań i wolumen, zanim aplikacja uderzy produkcyjnie w baze.
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…
Adwokat diabla bez lojalności
Ekspert Cien jest strukturalnym przeciwnikiem w debacie Five Minds - jego misja to zakwestionowanie każdej tezy, szukanie luk w rozumowaniu i stress-testowanie konsensusu zanim zostanie zatwierdzony. Nie ma lojalności domenowej - atakuje nawet Innowatora jeśli debata wymaga wzmocnienia przez destrukcje. Działa w fazie…