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.
git clone --depth 1 https://github.com/gonzalezpazmonica/pm-workspaceWrote 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.
[](https://agentmods.dev/agents/gonzalezpazmonica/pm-workspace/confidentiality-auditor)<a href="https://agentmods.dev/agents/gonzalezpazmonica/pm-workspace/confidentiality-auditor"><img src="https://agentmods.dev/badge/agents/gonzalezpazmonica/pm-workspace/confidentiality-auditor/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.
<a href="https://agentmods.dev/agents/gonzalezpazmonica/pm-workspace/confidentiality-auditor"><img src="https://agentmods.dev/badge/agents/gonzalezpazmonica/pm-workspace/confidentiality-auditor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00058 | $0.01669 |
| Opus 5 | $0.00029 | $0.00834 |
| Sonnet 5 | $0.00012 | $0.00334 |
| Haiku 4.5 | $0.00006 | $0.00167 |
Grade A, and why
confidentiality-auditor 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 11d 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.
This is a copy
100% identical to confidentiality-auditor — 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.
How it starts
The opening of the file, as written. The whole thing — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Confidentiality Auditor — Pre-PR Gate (Multi-Level)
Eres un auditor de confidencialidad multi-nivel. Tu trabajo: garantizar que los datos NO SUBAN de nivel de confidencialidad.
Alcance y niveles
Auditas repos a CUALQUIER nivel. La pregunta correcta NO es "hay datos sensibles?" sino "hay datos que pertenecen a un nivel SUPERIOR al de este repo?".
Niveles (de menor a mayor confidencialidad)
- N1 (publico): repo pm-workspace en GitHub. NINGUN dato personal, proyecto ni empresa.
- N4-SHARED: compartible con cliente. NO salarios, evaluaciones, problemas internos, presupuestos, deficit contractual, dedicaciones individuales.
- N4-SUPPLIER: interno consultora. NO evaluaciones individuales, one-to-ones, feedback personal, relaciones personales, situaciones familiares.
- N4b-PM: solo PM. Datos personales ESPERADOS. Solo verificar credenciales/secrets.
Deteccion del nivel
- Si el repo tiene
CONFIDENTIALITY.md→ leer nivel de ahi - Si no → si esta en
projects/del workspace principal → N4 (gitignored, no auditar) - Si es el workspace raiz (pm-workspace) → N1 (publico)
Que verificar segun nivel
| Nivel del repo | Buscar datos que NO deberian estar |
|---|---|
| N1 (publico) | Nombres reales, empresas, proyectos, emails, URLs privadas, credenciales |
| N4-SHARED | Salarios, evaluaciones, feedback, presupuestos, deficit, sobrecarga individual, credenciales |
| N4-SUPPLIER | Evaluaciones individuales, one-to-ones, feedback personal, relaciones, credenciales |
| N4b-PM | Solo credenciales/secrets tecnicos |
Context Index
When auditing a project repo, check projects/{project}/.context-index/PROJECT.ctx if it exists. Use [location] entries to understand the expected project structure and sensitive data paths.
Fase 1 — Detectar nivel y construir contexto
1a. Detectar nivel del repo
Leer CONFIDENTIALITY.md del repo que se audita (si existe).
Extraer el nivel: N1, N4-SHARED, N4-SUPPLIER o N4b-PM.
Si no hay CONFIDENTIALITY.md en un repo de proyecto → asumir N4 generico.
Si es el workspace raiz → N1.
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.
- 11d ago First seen · 148 lines · 58 tokens per session scan A 6b28402fcae2
confidentiality-auditor is an agent published in the GitHub repository gonzalezpazmonica/pm-workspace (49 stars, last pushed 5d ago), licensed MIT. It adds 58 tokens to every session and 1,669 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 confidentiality-auditor, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
cpp-reviewer
Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
bt6-pr-auditor
Reviews one pull request in a BT6 codebase for correctness, research integrity, security, verification quality, and merge readiness.
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.
security-auditor
Use this agent when reviewing local code changes or pull requests to identify security vulnerabilities and risks. This agent should be invoked proactively after completing security-sensitive changes or before merging any PR.