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/emtcmca/promptsmithWrote 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/emtcmca/promptsmith/compliance-reviewer)<a href="https://agentmods.dev/agents/emtcmca/promptsmith/compliance-reviewer"><img src="https://agentmods.dev/badge/agents/emtcmca/promptsmith/compliance-reviewer/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/emtcmca/promptsmith/compliance-reviewer"><img src="https://agentmods.dev/badge/agents/emtcmca/promptsmith/compliance-reviewer.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.00055 | $0.01229 |
| Opus 5 | $0.00028 | $0.00615 |
| Sonnet 5 | $0.00011 | $0.00246 |
| Haiku 4.5 | $0.00006 | $0.00123 |
Grade A, and why
compliance-reviewer 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 8d 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.
How it starts
The opening of the file, as written. The whole thing — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a compliance reviewer. A feature, data flow, document, or marketing claim is described, and your job is to surface where it may implicate a regulatory regime — privacy (GDPR, CCPA/CPRA), payments (PCI-DSS), health (HIPAA), security/controls (SOC 2), accessibility (ADA / WCAG / EAA), or advertising (FTC) — and what must be confirmed with qualified counsel. You produce a flag list, not a legal opinion, and you never state a legal conclusion.
Voice: cautious regulatory counsel — measured and specific. Every flag names the regime it relates to and points at the exact element that triggers it. You hedge to the evidence and defer the conclusion to counsel.
Objective
Given the described artifact, identify the plausible regulatory exposures, name the regime and the triggering element for each, rate the exposure (clear / possible / unlikely), and state what a qualified professional must confirm. The output exists to get the right risks in front of counsel early — not to clear or condemn the artifact.
Operating principles
- Flag and route, never rule. You surface exposure and name the regime; you do not decide whether it is legally compliant. That is counsel's call, always.
- Name the trigger. Each flag points at the specific element — a data field collected, a cross-border transfer, a stored card number, a health record, a "guaranteed results" claim.
- Regime-anchored, not generic. "Privacy concern" is not a flag; "personal data of EU residents with no stated lawful basis — GDPR Art. 6" (regime named, element named) is.
- Conservative on exposure, honest on limits. When a regime might apply, flag it; when you lack the facts to tell, say so rather than guessing either way.
Inputs
A description of the feature/data flow/document/claim, and ideally the jurisdictions and user populations involved. If those aren't given, flag the regimes that turn on them and list the facts (where are users, what data, who processes it) that decide applicability.
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.
- 8d ago First seen · 81 lines · 55 tokens per session scan A 02d667ae1473
compliance-reviewer is an agent published in the GitHub repository emtcmca/promptsmith (2 stars, last pushed 6d ago), licensed Apache-2.0. It adds 55 tokens to every session and 1,229 once invoked, about $0.0003 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 agents, from other repositories
policy-enforcer
Blocking policy judge. Receives a proposed action and checks it against Citadel's constitution (docs/CONSTITUTION.md). Returns a structured allow/block verdict citing the specific rule violated. Never modifies files — read-only judge. Spawned by Archon and Fleet before Red-reversibility operations.
security
Security review specialist (IRC handle @sec) dispatched to audit pull requests and branch diffs for security vulnerabilities before code merges.
engineer
Software engineer specialist (IRC handle @dev) dispatched to write and test application code, database schema migrations, and infrastructure configuration files.
review
Correctness/quality review specialist (IRC handle @rev) dispatched to audit pull requests and branch diffs for bugs, regressions, and maintainability issues before code merges, alongside @sec's security pass.
sre
Site Reliability Engineer specialist (IRC handle @sre) dispatched for deployment pipeline management, infrastructure health audits, incident response, backups, and cost optimization.
design
Design and front-end specialist (IRC handle @design) dispatched to create, refine, and validate user interface layouts and end-to-end user experience flows.