presidio recognizers.instructions.md

Repository guidance for adding or changing Presidio recognizers, the rules that identify types of personal information such as phone numbers or ID numbers.

In plain words
What is it for?
Use it when changing detection patterns, confidence scores, context words, checksums, tests, exports, documentation, or language and country support.
Why use it?
It helps prevent inaccurate matches and ensures recognizers work through direct code, registration, and YAML configuration paths.

Instructions file for GitHub Copilot

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 instructions/data-privacy-stack/presidio/recognizers
Clone the repo
git clone --depth 1 https://github.com/data-privacy-stack/presidio

Made for: GitHub Copilot.

Per session 2,195 This file is loaded in full into every session.
When invoked 2,195 The same file — it is already loaded in full.
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.02195 $0.02195
Opus 5 $0.01097 $0.01097
Sonnet 5 $0.00439 $0.00439
Haiku 4.5 $0.00219 $0.00219

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

Security

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.

.github/instructions/recognizers.instructions.md · 190 lines

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:

  1. 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_result must not promote weak matches to 1.0), and the logic's source is documented, preferably an official specification.
  2. 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.
  3. Construction paths that disagree (direct vs. add_recognizer() vs. YAML).
  4. 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.
  5. 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"]

Read the full file on GitHub · 190 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. today First seen · 190 lines · 2,195 tokens per session scan A 09ecc435a408

Subscribe to this mod's changes

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.

Related

Other instructions, from other repositories