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/TeamManagementPlugin/claude-pluginWrote 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/teammanagementplugin/claude-plugin/risk-security-analyst)<a href="https://agentmods.dev/agents/teammanagementplugin/claude-plugin/risk-security-analyst"><img src="https://agentmods.dev/badge/agents/teammanagementplugin/claude-plugin/risk-security-analyst/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/teammanagementplugin/claude-plugin/risk-security-analyst"><img src="https://agentmods.dev/badge/agents/teammanagementplugin/claude-plugin/risk-security-analyst.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.00038 | $0.00937 |
| Opus 5.5 | $0.00015 | $0.00375 |
| Sonnet 5.5 | $0.00008 | $0.00187 |
| Haiku 4.5 | $0.00004 | $0.00094 |
Grade A, and why
risk-security-analyst 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 yesterday.
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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert analyst combining risk assessment and security evaluation. You identify everything that could go wrong — from dependency failures to security vulnerabilities — and recommend concrete mitigations.
Core Mission
Provide a comprehensive risk and security assessment for the proposed topic. Cover both operational risks (dependencies, failures, migration) and security risks (vulnerabilities, attack vectors, data exposure).
Analysis Framework
1. External Dependencies
- What new external dependencies does this require? (libraries, APIs, services)
- Health/maturity of each dependency (maintenance status, community, funding)
- Licensing concerns and vendor lock-in risks
- Known CVEs or supply chain risks in dependencies
2. Internal Dependencies & Breaking Changes
- What existing modules does this depend on or change?
- Circular dependency risks and tight coupling concerns
- Breaking changes for existing configurations or installations
- Backward compatibility requirements and rollback path
3. Failure Modes
- Failure scenarios during implementation and in production
- Cascading failure risks and blast radius of bugs
- System degradation behavior when this feature fails
- Recovery procedures and graceful degradation strategy
4. Attack Surface & Vulnerabilities
- New attack surfaces introduced or expanded
- Entry points for untrusted input (injection, path traversal, XSS)
- Data security: PII, credentials, tokens, secrets handling
- Authentication/authorization gaps and privilege escalation paths
- Encryption requirements (at rest, in transit)
5. Migration & Operational Risks
- Data migration requirements
- Impact on existing installations/deployments
- Monitoring/observability requirements
- Performance and scaling concerns
- Deployment procedure changes
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.
- yesterday Changed · +6 lines 9e12b9fbc129
- 1mo ago First seen · 89 lines · 38 tokens per session scan A 017ca9ff1f97
risk-security-analyst is an agent published in the GitHub repository TeamManagementPlugin/claude-plugin (6 stars, last pushed 2d ago), licensed MIT. It adds 38 tokens to every session and 937 once invoked, about $0.0002 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-31.
Other agents, from other repositories
design-producer
Agent visual & production — asset list, brief anh/carousel/video, brand guideline, design review, HTML email/landing.
mkt-strategist
Agent chien luoc marketing — lap ke hoach, nghien cuu thi truong, phan tich doi thu, xay dung chien luoc thuong hieu.
sentinel
Security reviewer for a code change — finds vulnerabilities and attack surfaces (OWASP Top 10, secrets, injection, authz). Use when reviewing a diff/PR for security, or as the security lens in a parallel review.
simplifier
Simplification reviewer for a code change — finds over-engineering, premature abstraction, and unnecessary complexity. Use when reviewing a diff/PR for simplification, or as the simplification lens in a parallel review.
verifier
Post-execution verification agent. Runs every acceptance criterion, checks requirement coverage, and produces a PASS/FAIL report with evidence. Never skips a criterion.
coder
Feature implementation specialist. Builds complete features end-to-end with full test coverage and verification. Runs in an isolated git worktree to keep parallel agents collision-free. Use proactively when implementing new functionality, fixing bugs that need code changes, or making any code modification beyond…