risk-security-analyst

A combined risk and security analyst examines what could fail, be attacked, or expose data in a proposed change.

In plain words
What is it for?
Use it to review dependencies, breaking changes, failure scenarios, attack paths, vulnerabilities, and possible mitigations.
Why use it?
It brings operational risks, such as dependency failures and difficult migrations, together with security risks in one assessment.

Agent

Install

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.

agentmods
npx agentmods add agents/teammanagementplugin/claude-plugin/risk-security-analyst
Clone the repo
git clone --depth 1 https://github.com/TeamManagementPlugin/claude-plugin
Per session 38 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 850 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00038 $0.00850
Opus 5 $0.00019 $0.00425
Sonnet 5 $0.00008 $0.00170
Haiku 4.5 $0.00004 $0.00085

Measured yesterday against content hash 017ca9ff1f97, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

plugin/agents/risk-security-analyst.md · 89 lines

How it starts

The opening of the file, as written. The whole thing — 89 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

Read the full file on GitHub · 89 lines

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.

  1. yesterday First seen · 89 lines · 38 tokens per session scan A 017ca9ff1f97

Subscribe to this mod's changes

risk-security-analyst is an agent published in the GitHub repository TeamManagementPlugin/claude-plugin (4 stars, last pushed 26d ago), licensed MIT. It adds 38 tokens to every session and 850 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.