Borrowing it
Nothing to install: this file belongs to Nosmoht/talos-mcp-server. 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/Nosmoht/talos-mcp-server/main/.claude/agents/senior-plan-reviewer.mdgit clone --depth 1 https://github.com/Nosmoht/talos-mcp-serverWrote 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/nosmoht/talos-mcp-server/senior-plan-reviewer)<a href="https://agentmods.dev/agents/nosmoht/talos-mcp-server/senior-plan-reviewer"><img src="https://agentmods.dev/badge/agents/nosmoht/talos-mcp-server/senior-plan-reviewer/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/nosmoht/talos-mcp-server/senior-plan-reviewer"><img src="https://agentmods.dev/badge/agents/nosmoht/talos-mcp-server/senior-plan-reviewer.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.00030 | $0.00715 |
| Opus 5 | $0.00015 | $0.00358 |
| Sonnet 5 | $0.00006 | $0.00143 |
| Haiku 4.5 | $0.00003 | $0.00072 |
Grade A, and why
senior-plan-reviewer 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 11d 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.
How it starts
The opening of the file, as written. The whole thing — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior engineer reviewing proposed plans before implementation begins. Your job is to catch problems early — before any code is written.
Evaluation Heuristics
Evaluate the plan for completeness, risk, and architectural alignment. Pay particular attention to:
- Scope: Is this one bounded logical change? Does it identify all files that will change?
- Risk: Are error paths and edge cases considered? Are there breaking API surface changes?
- Test strategy: Does it describe how the change will be tested using project patterns (
safeH(), table-driven tests)? - Architecture: Does it respect existing package boundaries (
internal/tools/,internal/prompts/,internal/resources/,internal/talos/)?
These are heuristics, not a rigid checklist. Flag anything that would cause implementation problems even if it doesn't fit neatly into a category.
Output Format
Produce a review artifact file at .claude/reviews/<change-id>/plan-review.md with this exact YAML frontmatter:
---
change-id: <semantic-slug from the plan>
review-type: plan-review
reviewer-role: senior-plan-reviewer
status: <approved if zero findings, changes-requested otherwise>
timestamp: <ISO 8601>
reviewed-scope:
- <list of files or "full plan">
findings: []
---
## Notes
<!-- Optional context or rationale -->
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.
- 11d ago First seen · 83 lines · 30 tokens per session scan A 04ac80195256
senior-plan-reviewer is an agent published in the GitHub repository Nosmoht/talos-mcp-server (3 stars, last pushed 17d ago), licensed MIT. It adds 30 tokens to every session and 715 once invoked, about $0.0002 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
security-engineer
Use this agent when implementing comprehensive security solutions across infrastructure, building automated security controls into CI/CD pipelines, or establishing compliance and vulnerability management programs. Invoke for threat modeling, zero-trust architecture design, security automation implementation, and…
devops-engineer
Use this agent when building or optimizing infrastructure automation, CI/CD pipelines, containerization strategies, and deployment workflows to accelerate software delivery while maintaining reliability and security.
eks-recon-cicd
EKS CI/CD and GitOps reconnaissance subagent.
eks-recon-cluster-insights
EKS Cluster Insights reconnaissance subagent.
eks-recon-networking
EKS networking reconnaissance subagent.
intent-translator
Converts natural-language service intents into Nephio-compatible Kubernetes resource manifests.