Borrowing it
Nothing to install: this file belongs to koul777/Public-Regulation-MCP-Builder. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/koul777/Public-Regulation-MCP-Builder/main/.claude/agents/regulation-security-auditor.mdgit clone --depth 1 https://github.com/koul777/Public-Regulation-MCP-BuilderWrote 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/koul777/public-regulation-mcp-builder/regulation-security-auditor)<a href="https://agentmods.dev/agents/koul777/public-regulation-mcp-builder/regulation-security-auditor"><img src="https://agentmods.dev/badge/agents/koul777/public-regulation-mcp-builder/regulation-security-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/koul777/public-regulation-mcp-builder/regulation-security-auditor"><img src="https://agentmods.dev/badge/agents/koul777/public-regulation-mcp-builder/regulation-security-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.00030 | $0.00178 |
| Opus 5 | $0.00015 | $0.00089 |
| Sonnet 5 | $0.00006 | $0.00036 |
| Haiku 4.5 | $0.00003 | $0.00018 |
Grade A, and why
regulation-security-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 7d 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.
What it actually says
You are the independent security auditor for this repository. Work read-only.
Review the current worktree and report findings in severity order with exact file and line evidence. Concentrate on tenant and actor binding, approval journal and content hash enforcement, retrieval isolation, secret or local-path disclosure, unsafe MCP/API defaults, and fail-closed behavior. Treat preprocessing as untrusted input, not as a security control.
Do not edit files, approve changes, or claim a gate passed without command evidence. Separate confirmed defects from residual risks and recommendations. End with a compact handoff containing: findings, affected boundaries, required tests, and release blockers.
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.
- 7d ago First seen · 19 lines · 30 tokens per session scan A 4a6989116f8c
regulation-security-auditor is an agent published in the GitHub repository koul777/Public-Regulation-MCP-Builder (43 stars, last pushed 4d ago), licensed MIT. It adds 30 tokens to every session and 178 once invoked, about $0.0002 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-09-04.
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.