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.
npx skills add zgbrenner/agentcounsel --skill regulatory-exam-responsegit clone --depth 1 https://github.com/zgbrenner/agentcounselWrote 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/skills/zgbrenner/agentcounsel/regulatory-exam-response)<a href="https://agentmods.dev/skills/zgbrenner/agentcounsel/regulatory-exam-response"><img src="https://agentmods.dev/badge/skills/zgbrenner/agentcounsel/regulatory-exam-response/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/skills/zgbrenner/agentcounsel/regulatory-exam-response"><img src="https://agentmods.dev/badge/skills/zgbrenner/agentcounsel/regulatory-exam-response.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.00067 | $0.02962 |
| Opus 5 | $0.00034 | $0.01481 |
| Sonnet 5 | $0.00013 | $0.00592 |
| Haiku 4.5 | $0.00007 | $0.00296 |
Grade A, and why
Regulatory Exam Response 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 9d 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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Regulatory Exam Response
Purpose
Organize an incoming regulatory examination, information request, or inquiry into a structured response package for counsel. The skill inventories every request item verbatim, builds a request-item-to-owner-to-source tracker, frames scope and responsiveness questions as questions for counsel to decide, flags privilege and preservation issues for the appropriate specialist workflows, and drafts a cover-response skeleton with placeholders. It produces draft legal work product for attorney review — not legal advice, not a response strategy, and never a decision to narrow, withhold, or delay any response to a regulator.
Use When
- A regulator has sent an examination letter, an information or document request, a questionnaire, or a supervisory inquiry, and the response effort needs structure.
- A user asks to "organize this exam request," "build a tracker for this information request," or "get us ready to respond to the regulator."
- Counsel needs every request item inventoried, assigned an owner, and mapped to likely sources before deciding the response approach.
- A compliance or legal-operations team needs a repeatable intake-and-tracking process for recurring supervisory examinations.
- A first-pass screen is needed to spot enforcement-adjacent signals in an inquiry so counsel can be alerted immediately.
Required Inputs
- The full text of the examination letter, information request, or inquiry (uploaded or pasted). Do not organize a response from a description alone — the actual request document must be reviewed.
- The identity of the regulator (agency, division, and examiner or contact if stated) and the recipient entity.
- The date of receipt and any response date stated on the face of the request. Both are recorded as user-supplied and flagged
[deadline verification required]. - The business units, systems, and personnel implicated by the request, as known. Gaps are recorded as
[CONFIRM: ...]items, not assumed. - Optional: prior correspondence with the regulator on the same matter, and any existing exam-management or regulatory-response policy.
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.
- 9d ago First seen · 140 lines · 67 tokens per session scan A 2f463895cea5
Regulatory Exam Response is a skill published in the GitHub repository zgbrenner/agentcounsel (19 stars, last pushed 1mo ago), licensed MIT. It adds 67 tokens to every session and 2,962 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-09-03.
Other skills, from other repositories
performance-management
Runs performance systems that change behavior — expectations, feedback, review cycles, calibration, and handling underperformance. Use this to design or fix a review process, run calibration, write or coach on feedback, address sustained underperformance, or work out why reviews consume weeks and change nothing.
vendor-evaluation
Evaluate, select, and contract with vendors and SaaS tools. Use this skill when comparing alternatives, running an RFP, scoring vendors against criteria, negotiating contracts, planning a switch, or assessing a vendor's risk. Triggers on vendor evaluation, RFP, vendor selection, build vs buy, SaaS evaluation, vendor…
compliance-tracker
Track regulatory compliance for construction projects. Monitor permits, certifications, inspections, and regulatory requirements with automated alerts and reporting.
safety-inspection-checklist
Digital safety inspection checklists for construction sites. Generate, conduct, and track safety inspections with automated reporting and compliance monitoring.
delay-analysis
Analyze construction schedule delays for claims and recovery. Perform time impact analysis, identify delay causes, calculate damages, and document for disputes.
change-order-manager
Manage construction change orders from request to approval. Track costs, schedule impacts, and maintain audit trail for dispute prevention.