meeting-confidentiality-judge

meeting-confidentiality-judge is an agent for Claude Code from gonzalezpazmonica/pm-workspace. It costs 64 tokens per session (1,274 once invoked), scanned A, a copy of meeting-confidentiality-judge, MIT.

A privacy check performed after meeting notes have been extracted from a transcript. It decides whether each proposed piece of information is public, confidential, sensitive or unclear before it is written into project files.

In plain words
What is it for?
Use it with meeting-extraction workflows to review proposed Markdown updates, block confidential or sensitive content, allow public information and flag ambiguous items for a project manager.
Why use it?
It prevents private meeting information and personal details from being copied into shared project documents. Unclear cases are sent for human review instead of being silently accepted.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter; mentions OpenCode.

Part of the pm-workspace plugin — 124 commands, 75 agents shipped together

Good fit Use it with meeting-extraction workflows to review proposed Markdown updates, block confidential or sensitive content, allow public information and flag ambiguous items for a project manager.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/gonzalezpazmonica/pm-workspace/meeting-confidentiality-judge
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/gonzalezpazmonica/pm-workspace

Made for: Claude Code.

Or install pm-workspace, the plugin that ships this one along with the rest of its 124 commands, 75 agents.

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 meeting-confidentiality-judge

README.md
[![agentmods](https://agentmods.dev/badge/agents/gonzalezpazmonica/pm-workspace/meeting-confidentiality-judge/github.svg)](https://agentmods.dev/agents/gonzalezpazmonica/pm-workspace/meeting-confidentiality-judge)
Your own site
<a href="https://agentmods.dev/agents/gonzalezpazmonica/pm-workspace/meeting-confidentiality-judge"><img src="https://agentmods.dev/badge/agents/gonzalezpazmonica/pm-workspace/meeting-confidentiality-judge/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 meeting-confidentiality-judge

Your own site · 80×15
<a href="https://agentmods.dev/agents/gonzalezpazmonica/pm-workspace/meeting-confidentiality-judge"><img src="https://agentmods.dev/badge/agents/gonzalezpazmonica/pm-workspace/meeting-confidentiality-judge.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 64 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,274 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 100% copy Near-identical to another mod 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.00064 $0.01274
Opus 5 $0.00032 $0.00637
Sonnet 5 $0.00013 $0.00255
Haiku 4.5 $0.00006 $0.00127

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

Security

Grade A, and why

meeting-confidentiality-judge 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 12d 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.

Origin

This is a copy

100% identical to meeting-confidentiality-judge — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/agents/meeting-confidentiality-judge.md · 130 lines

How it starts

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

Eres un juez independiente de confidencialidad. Tu unico trabajo es proteger la privacidad de las personas en reuniones transcritas. Recibes la extraccion de datos de una reunion y verificas que ningun dato confidencial se filtre a los ficheros del proyecto.

Que recibes

  1. Transcripcion original (fragmentos relevantes)
  2. Datos extraidos (bloques PERFIL, NEGOCIO, NOTAS PM)
  3. Segmentos marcados como confidenciales por el extractor
  4. Propuesta de escritura — que se va a escribir en cada fichero .md

Tu veredicto

Para CADA dato propuesto para escritura, clasificar:

Clasificacion Significado Accion
PUBLICO OK para escribir en ficheros del proyecto Permitir
CONFIDENCIAL Dato que el interlocutor pidio que fuera secreto BLOQUEAR
SENSIBLE Dato personal delicado aunque no se pidio secreto BLOQUEAR
AMBIGUO No esta claro si es confidencial Marcar para PM

Senales de confidencialidad explicita

Detectar en la transcripcion original cualquiera de estas senales:

  • "esto es confidencial" / "esto queda entre nosotros"
  • "no lo pongas" / "no lo apuntes" / "no lo registres"
  • "off the record" / "entre tu y yo"
  • "guardame el secreto" / "con discrecion"
  • "no quiero que esto salga" / "no se lo digas a nadie"
  • "esto no puede llegar a..." / "que no se entere..."
  • Cambio de tono: bajar la voz, pausas antes de confesar algo
  • "te lo digo a ti como PM pero..." / "en confianza..."
  • Cualquier variante coloquial equivalente en espanol

Senales de confidencialidad implicita (datos sensibles)

Aunque NO se pida secreto, estos datos son sensibles por defecto:

  • Problemas de salud mental o fisica
  • Situaciones legales personales (divorcios, denuncias)
  • Quejas sobre salario o condiciones laborales especificas
  • Busqueda activa de empleo / intenciones de dejar la empresa
  • Conflictos personales con nombre y apellido fuera del ambito laboral
  • Datos de salud de familiares
  • Orientacion sexual, religion, ideologia politica
  • Adicciones o problemas personales graves

Read the full file on GitHub · 130 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. 12d ago First seen · 130 lines · 64 tokens per session scan A 69ea816f8a27

Subscribe to this mod's changes

meeting-confidentiality-judge is an agent published in the GitHub repository gonzalezpazmonica/pm-workspace (49 stars, last pushed 6d ago), licensed MIT. It adds 64 tokens to every session and 1,274 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to meeting-confidentiality-judge, differing in 0 lines, and is treated as a copy.