audit-pii

audit-pii is a command for coding agents from rohitg00/awesome-claude-code-toolkit. It costs 0 tokens per session (151 once invoked), scanned A, original, Apache-2.0.

A command that scans source code, configuration, and data stores for personally identifiable information (PII), such as information that can identify a person.

In plain words
What is it for?
Use it to create a PII inventory, identify exposure risks, and guide remediation work.
Why use it?
It helps find sensitive data that may be exposed or insufficiently protected, including real production data in tests.

Command

Part of the data-privacy plugin — 2 commands shipped together

About the project

Awesome Claude Code Toolkit is a curated collection of extensions and configuration for Claude Code, including agents, skills, commands, plugins, hooks, rules, templates, MCP configurations, and companion apps. It is for Claude Code users who want ready-made workflows and integrations for different development tasks. The catalogue add-ons are selected components from this toolkit.

rohitg00/awesome-claude-code-toolkit · 2,587 stars · on GitHub

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 commands/rohitg00/awesome-claude-code-toolkit/audit-pii
Clone the repo
git clone --depth 1 https://github.com/rohitg00/awesome-claude-code-toolkit

Or install data-privacy, the plugin that ships this one along with the rest of its 2 commands.

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 audit-pii

README.md
[![agentmods](https://agentmods.dev/badge/commands/rohitg00/awesome-claude-code-toolkit/audit-pii.svg)](https://agentmods.dev/commands/rohitg00/awesome-claude-code-toolkit/audit-pii)
Your own site
<a href="https://agentmods.dev/commands/rohitg00/awesome-claude-code-toolkit/audit-pii"><img src="https://agentmods.dev/badge/commands/rohitg00/awesome-claude-code-toolkit/audit-pii.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 151 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.00000 $0.00151
Opus 5 $0.00000 $0.00076
Sonnet 5 $0.00000 $0.00030
Haiku 4.5 $0.00000 $0.00015

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

Security

Grade A, and why

audit-pii 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.

plugins/data-privacy/commands/audit-pii.md · 31 lines

What it actually says

Scan the codebase and data stores for personally identifiable information (PII) exposure risks.

Steps

  1. Define PII categories to scan for:
  2. Scan source code:
  3. Scan configuration:
  4. Check data flow:
  5. Verify protection measures:
  6. Generate a PII inventory map.
  7. Recommend remediation for each exposure risk.

Format

PII Audit: <project>
PII Types Found: <list>
Exposure Risks:
  [HIGH] <location>: <PII type> - <risk description>

Rules

  • Treat all personal data as sensitive until classified otherwise.
  • Check test data and fixtures for real PII from production.
  • Log access to PII for audit compliance.
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 · 31 lines · 0 tokens per session scan A c53313b6ea3f

Subscribe to this mod's changes

audit-pii is a command published in the GitHub repository rohitg00/awesome-claude-code-toolkit (2,587 stars, last pushed 3mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 151 tokens. 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-09-03.