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-history-tracergit 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-history-tracer)<a href="https://agentmods.dev/skills/zgbrenner/agentcounsel/regulatory-history-tracer"><img src="https://agentmods.dev/badge/skills/zgbrenner/agentcounsel/regulatory-history-tracer/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-history-tracer"><img src="https://agentmods.dev/badge/skills/zgbrenner/agentcounsel/regulatory-history-tracer.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.00078 | $0.02840 |
| Opus 5 | $0.00039 | $0.01420 |
| Sonnet 5 | $0.00016 | $0.00568 |
| Haiku 4.5 | $0.00008 | $0.00284 |
Grade A, and why
Regulatory History Tracer 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Regulatory History Tracer
Purpose
Trace the amendment history of a specific federal regulation — typically a single CFR section — to produce a date-stable history table the attorney can rely on. The trace records what the regulation said on each requested date, which Federal Register rulemakings amended it between dates, and which version was in effect at the date relevant to the matter. The skill produces draft legal work product for attorney review; it is not legal advice, and it does not determine which version of the regulation applies to any specific facts.
The most important disciplines this skill enforces:
- Date is load-bearing. Every version snapshot in the trace is anchored to a specific date — usually
[the date relevant to the matter], the date of conduct, and today's date. The skill never collapses "the regulation" into a single timeless text. - Codified text and rulemaking publication are different artifacts. The trace separates what the CFR said on this date (verified through
connectors/ecfr.md) from which Federal Register documents made that text possible (verified throughconnectors/federal-register.md). Each row of the history table cites both. - Codified is not operative. A regulation can be codified in the CFR but stayed by a court, enjoined, or pending vacatur. The trace records publication and codification only; operative status is a
[verify litigation]attorney-verification item that the skill does not attempt to resolve.
Use When
- A matter turns on what a regulation said on a specific date — the date of the conduct, the date of a transaction, a filing date, the effective date of a different rule.
- A litigation team needs to know which version of a CFR section governed during a contested period.
- A regulatory advice matter requires a side-by-side of past, current, and proposed versions of a section.
- A compliance assessment requires knowing which Federal Register documents amended a CFR section in a given window.
- A research workflow has identified a CFR citation but the version, effective date, and history must be locked down before the citation is used.
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 · 128 lines · 78 tokens per session scan A 3fe278f002d1
Regulatory History Tracer is a skill published in the GitHub repository zgbrenner/agentcounsel (19 stars, last pushed 1mo ago), licensed MIT. It adds 78 tokens to every session and 2,840 once invoked, about $0.0004 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
legal-research
A legal research skill for finding and analysing laws and court cases, including similar cases. It requires access to a reliable legal research database before producing a formal report.
document-fill
A document-filling assistant that uses a supplied template and case files to fill in forms, contracts, or legal documents. It also reports where each filled value came from and which details are missing.
contract-review
A contract-review workflow for agreements governed by Chinese law, United States law, or both. It examines clauses one by one and produces a list of legal-risk questions, with an optional marked-up Word document.
fedramp
Expert guidance for FedRAMP certification and compliance under CR26 (FedRAMP Consolidated Rules for 2026). Use this skill whenever a user asks about FedRAMP authorization, ATO (Authority to Operate), cloud security for federal government, NIST SP 800-53 controls, CSP compliance, or any of the core FedRAMP document…
eu-cra
Expert EU Cyber Resilience Act (CRA) advisor for Regulation (EU) 2024/2847 — mandatory cybersecurity and vulnerability handling requirements for all products with digital elements (PDEs) sold in the EU. Use this skill for gap analysis, product classification (Default / Class I / Class II), conformity assessment route…
aenderungsvorbehalt-308
Für Änderungsvorbehalt 308: ordnet Norm, Beweislast und Gegenargument; Ergebnis: Prüfprodukt mit Risiko und nächstem Schritt.