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.
npx agentmods add instructions/data-privacy-stack/presidio/recognizersgit clone --depth 1 https://github.com/data-privacy-stack/presidioWhat 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 | $0.02195 | $0.02195 |
| Opus 5 | $0.01097 | $0.01097 |
| Sonnet 5 | $0.00439 | $0.00439 |
| Haiku 4.5 | $0.00219 | $0.00219 |
Grade A, and why
presidio recognizers.instructions.md 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 today.
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 — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Recognizer changes
Rules for adding or modifying PII recognizers. When reviewing, lead with the highest-impact gaps in this order:
- Pattern accuracy. The pattern is as specific as the format allows, the
score is calibrated to the pattern alone, the context words are the right
ones, the checksum is correct where one exists (and none is invented where
it doesn't —
validate_resultmust not promote weak matches to 1.0), and the logic's source is documented, preferably an official specification. - Proper testing. A configuration-path test through
RecognizerRegistryProvider(the load-bearing rule below), exact-score assertions rather than ranges, a lookalike negative, and context-enhancement coverage. - Construction paths that disagree (direct vs.
add_recognizer()vs. YAML). - Changes to an existing recognizer's patterns, scores, or context made as a side effect of adding a new one — users depend on current detection behavior.
- Language/country-code mismatch; missing exports, YAML entry, or docs row.
Give specific, actionable feedback: cite the file and line and propose the concrete fix. Do not comment on formatting — Ruff and CI own that.
The load-bearing rule: test the configuration path
Most predefined recognizers ship enabled: false, so the default test run never
constructs them from configuration. Users, however, reach them exactly one way:
flipping enabled: true in a registry YAML. A recognizer that works when built
in Python can still be unreachable — or crash — when enabled in YAML.
Every new or changed recognizer needs at least one test that loads it through
RecognizerRegistryProvider and asserts detection:
def test_recognizer_loads_and_detects_when_enabled_in_yaml(tmp_path):
"""Detection must work through the path users actually configure."""
conf = tmp_path / "recognizers.yaml"
conf.write_text(
"""
supported_languages:
- en
recognizers:
- name: MyRecognizer
supported_languages:
- en
type: predefined
enabled: true
country_code: us
"""
)
registry = RecognizerRegistryProvider(conf_file=conf).create_recognizer_registry()
analyzer = AnalyzerEngine(registry=registry, nlp_engine=nlp_engine)
results = analyzer.analyze("Member ID ABC123456", language="en")
assert [result.entity_type for result in results] == ["MY_ENTITY"]
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.
- today First seen · 190 lines · 2,195 tokens per session scan A 09ecc435a408
presidio recognizers.instructions.md is an instructions file published in the GitHub repository data-privacy-stack/presidio (10,694 stars, last pushed yesterday), licensed MIT. It adds 2,195 tokens to every session, about $0.0110 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.
Other instructions, from other repositories
piighost CLAUDE.md
Instructions for Athroniaeth/piighost, covering claude.md, project overview, development commands, architecture and anonymization pipeline.
privacy-kit-cl AGENTS.md
Instructions for Yugoxc/privacy-kit-cl, covering agents.md — guía de integración para una ia, objetivo, paso 0 — detectar el terreno, paso 1 — instalar y configurar and paso 2 — implementar el store.
rizzo-pii CLAUDE.md
Instructions for Rizzo-AI-Academy/rizzo-pii, covering claude.md, cos'è questo progetto, ambiente — vincoli critici e non ovvi, mappa della repo and tassonomia: 22 tag (dettaglio in tassonomiatag.md).
pii-guard AGENTS.md
Instructions for danyuchn/pii-guard, covering agents.md, project overview, tech stack, architecture and commands.
datamimic AGENTS.md
Instructions for rapiddweller/datamimic, covering agents.md, when should an agent reach for datamimic?, tool selection, benchmarking local ollama models and authoring a new model.
docs_masked AGENTS.md
Instructions for kpshinnik/docs_masked, covering agents.md — правила работы в этом репозитории, инварианты, которые нельзя ломать, разработка, как добавить детектор and как добавить формат.