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.
git clone --depth 1 https://github.com/wallter/trw-mcpWrote 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/wallter/trw-mcp/trw-prd-groomer)<a href="https://agentmods.dev/agents/wallter/trw-mcp/trw-prd-groomer"><img src="https://agentmods.dev/badge/agents/wallter/trw-mcp/trw-prd-groomer/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/wallter/trw-mcp/trw-prd-groomer"><img src="https://agentmods.dev/badge/agents/wallter/trw-mcp/trw-prd-groomer.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.00054 | $0.01798 |
| Opus 5 | $0.00027 | $0.00899 |
| Sonnet 5 | $0.00011 | $0.00360 |
| Haiku 4.5 | $0.00005 | $0.00180 |
Grade A, and why
trw-prd-groomer 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 10d 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 10d ago First seen · 165 lines · 54 tokens per session scan A 3d08b6d83885
trw-prd-groomer is an agent published in the GitHub repository wallter/trw-mcp (0 stars, last pushed 2d ago), with no licence file. It adds 54 tokens to every session and 1,798 once invoked, about $0.0003 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 agents, from other repositories
task-executor
Executes a coherent delivery batch or one assigned lane from a phased plan. Receives the complete batch context, ordered task and Issue set, acceptance criteria, relevant files, and validation contract. Implements and commits the work, but leaves integration state, cumulative telemetry, and the single batch PR to the…
01-crm-pull
Fetch contacts, actions, pipeline data from CRM (Notion or local markdown).
04-value-routing
Match today's signals to active prospects and generate personalized value-drop messages.
05-pipeline-followup
Identify overdue warm/active contacts and generate follow-up copy with stage advancement checks.
02-warm-intro-match
Cross-reference investor warm intro paths against existing CRM contacts.
03-prospect-pipeline
Count prospects by status, compute touch recency, and flag auto-close candidates.