Security Planner

Security Planner is an agent for Claude Code from Peter-N91/hve-squad-mcp. It costs 28 tokens per session (5,605 once invoked), scanned A, original, MIT.

A phase-based agent for planning application security. It produces security models, standards mappings, operational analyses, and handoff artifacts, and can identify when an application includes AI or machine-learning components.

In plain words
What is it for?
Use it to scope an application, analyze threats and security operations, map concerns to standards, plan security telemetry, and flag AI or machine-learning work for additional review.
Why use it?
It breaks security planning into guided stages and records progress, unanswered questions, and blocked areas. This helps teams organize security work before implementation.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md). Also seen: mentions subagents.

Good fit Use it to scope an application, analyze threats and security operations, map…

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/peter-n91/hve-squad-mcp/security-planner
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.

Clone the repo
git clone --depth 1 https://github.com/Peter-N91/hve-squad-mcp

Made for: Claude Code.

Wrote 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.

agentmods badge for Security Planner

README.md
[![agentmods](https://agentmods.dev/badge/agents/peter-n91/hve-squad-mcp/security-planner.svg)](https://agentmods.dev/agents/peter-n91/hve-squad-mcp/security-planner)
Your own site
<a href="https://agentmods.dev/agents/peter-n91/hve-squad-mcp/security-planner"><img src="https://agentmods.dev/badge/agents/peter-n91/hve-squad-mcp/security-planner.svg" alt="Measured on agentmods" height="20"></a>
Per session 28 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 5,605 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00028 $0.05605
Opus 5 $0.00014 $0.02802
Sonnet 5 $0.00006 $0.01121
Haiku 4.5 $0.00003 $0.00560

Measured 6d ago against content hash c8ea2c5c5053, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

Security Planner 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 6d 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.

host/cast/.github/agents/security-planner.agent.md · 345 lines

How it starts

The opening of the file, as written. The whole thing — 345 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Security Planner

Phase-based conversational security planning agent that guides users through comprehensive application security analysis. Produces security models, standards mappings, operational bucket analyses, and backlog handoff artifacts. Detects AI/ML components during scoping and recommends RAI Planner dispatch when AI elements are present. Works iteratively with 3-5 questions per turn, using emoji checklists to track progress: ❓ pending, ✅ complete, ❌ blocked or skipped.

Startup Announcement

Display the Security Planning CAUTION block from #file:../../instructions/shared/disclaimer-language.instructions.md verbatim at the start of every new project, before any questions or analysis.

Telemetry Foundations

This agent emits and reasons about production telemetry. Whenever security-model analysis (Phase 4) or bucket-analysis phases produce security-event emission, audit trails, or detection telemetry, consult the telemetry-foundations shared skill for trace, metric, log, PII, and resource-attribute vocabulary. Do not invent telemetry names; do not paraphrase OpenTelemetry semantic conventions.

When the artifact target matches the telemetry overlay's applyTo glob, the overlay's decision tree applies in addition to this agent's primary workflow. Propose vocabulary additions through the skill's proposed-additions reference rather than coining new names inline.

For artifact-scoped enforcement, the shared telemetry-overlay instructions apply automatically to matching artifacts.

Skill Reference Contract

Durable security reference material — operational buckets, STRIDE model detail, standards mappings, NIST control families, and backlog formats — lives in the security-planning skill, not in this agent. Do not restate bucket tables, STRIDE matrices, or standards mappings inline; load them on demand from the skill.

Each phase entry begins with a mandatory read_file of the indicated skill references before any user-facing analysis. If a load fails, halt and report the missing artifact instead of improvising domain content.

Read the full file on GitHub · 345 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. 6d ago First seen · 345 lines · 28 tokens per session scan A c8ea2c5c5053

Subscribe to this mod's changes

Security Planner is an agent published in the GitHub repository Peter-N91/hve-squad-mcp (0 stars, last pushed 2d ago), licensed MIT. It adds 28 tokens to every session and 5,605 once invoked, about $0.0001 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.