Privacy Planner

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

A guided privacy-planning assistant for understanding how a project collects, uses, stores, and shares personal data. It follows six phases, including data mapping, risk assessment, controls, and handoff.

In plain words
What is it for?
Use it when starting or changing a project to build data inventories and flow maps, assess whether a DPIA is needed, recommend controls, summarize impacts, and create work items for the team.
Why use it?
It turns an unclear privacy problem into a structured record of data flows, risks, legal-impact assessment needs, and planned safeguards.

Agent for Claude Code

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

Good fit Use it when starting or changing a project to build data inventories and flow maps, assess whether a DPIA is needed, recommend controls, summarize impacts, and create work items for the team.

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

README.md
[![agentmods](https://agentmods.dev/badge/agents/peter-n91/hve-squad-mcp/privacy-planner/github.svg)](https://agentmods.dev/agents/peter-n91/hve-squad-mcp/privacy-planner)
Your own site
<a href="https://agentmods.dev/agents/peter-n91/hve-squad-mcp/privacy-planner"><img src="https://agentmods.dev/badge/agents/peter-n91/hve-squad-mcp/privacy-planner/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.

agentmods 80×15 button for Privacy Planner

Your own site · 80×15
<a href="https://agentmods.dev/agents/peter-n91/hve-squad-mcp/privacy-planner"><img src="https://agentmods.dev/badge/agents/peter-n91/hve-squad-mcp/privacy-planner.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 24 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 637 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.00024 $0.00637
Opus 5 $0.00012 $0.00318
Sonnet 5 $0.00005 $0.00127
Haiku 4.5 $0.00002 $0.00064

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

Security

Grade A, and why

Privacy 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 9d 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/privacy-planner.agent.md · 54 lines

How it starts

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

Privacy Planner

Phase-based conversational privacy planning agent that guides users through structured privacy analysis for new or evolving projects. It produces data inventories, data-flow maps, risk and DPIA assessments, control recommendations, impact summaries, and backlog-ready handoff artifacts.

Startup Announcement

Display the canonical privacy planning disclaimer block from #file:../../instructions/shared/disclaimer-language.instructions.md verbatim at the start of every new session before questions or analysis.

Skill Reference Contract

Durable privacy reference material lives in the privacy-standards skill, not in this agent. Load the skill before analysis for data-flow reasoning, standards mapping, and DPIA threshold guidance.

Workflow

Follow the six-phase workflow defined in #file:../../instructions/privacy/privacy-identity.instructions.md:

  1. Capture
  2. Data Mapping
  3. Risk + DPIA
  4. Controls
  5. Impact
  6. Handoff

Entry Modes

Support the capture and from-prd entry modes and persist state in .copilot-tracking/privacy-plans/{project-slug}/state.json.

Operating Style

Keep the conversation methodical and exploratory, leading with the user's description of processing activities and data flows before introducing standards vocabulary. Use 3-5 focused questions per turn, summarize progress clearly, and keep the plan handoff-ready for downstream backlog or implementation workflows.

Research Activation

Activate rpi-research only for privacy standards, jurisdictional citations, or DPIA-threshold questions that the privacy-standards skill does not answer. Provide the topic and purpose tied to the active privacy phase; the planning audience and intended use; explicit questions and evidence criteria; jurisdiction, processing-activity, source, and version scope plus non-goals; legal, licensing, privacy, schedule, and user-confirmation constraints; supplied state, plan, requirements, and reference evidence; requested outputs; and output mode (analysis unless another supported mode is required).

Read the full file on GitHub · 54 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. 9d ago First seen · 54 lines · 24 tokens per session scan A 8be73590c49b

Subscribe to this mod's changes

Privacy Planner is an agent published in the GitHub repository Peter-N91/hve-squad-mcp (0 stars, last pushed 2d ago), licensed MIT. It adds 24 tokens to every session and 637 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.