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 rule-change-summarygit 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/rule-change-summary)<a href="https://agentmods.dev/skills/zgbrenner/agentcounsel/rule-change-summary"><img src="https://agentmods.dev/badge/skills/zgbrenner/agentcounsel/rule-change-summary/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/rule-change-summary"><img src="https://agentmods.dev/badge/skills/zgbrenner/agentcounsel/rule-change-summary.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.00035 | $0.02681 |
| Opus 5 | $0.00017 | $0.01340 |
| Sonnet 5 | $0.00007 | $0.00536 |
| Haiku 4.5 | $0.00003 | $0.00268 |
Grade A, and why
Rule Change Summary 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 — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rule Change Summary
Purpose
Produce a structured, attorney-ready summary of a regulatory rule change, proposed rule, interim final rule, or official guidance document, and identify its practical implications for a specific organization or practice area. The output captures what changed, who is affected, what new or modified obligations arise, and what implementation steps warrant attention — all grounded in the text actually provided.
This skill provides workflow discipline and output structure. It does not interpret regulations as legal advice or assert compliance conclusions.
Use When
- A user says "summarize this new rule," "what does this guidance require," or "what changed from the old rule."
- Counsel or a compliance team receives a final or proposed rule and needs a structured first-pass summary to brief leadership or begin gap analysis.
- An organization needs to understand effective dates, compliance deadlines, and who within the organization is affected.
- A user provides a Federal Register notice, agency guidance, proposed rule text, or similar official document and asks for its significance.
- Preliminary scoping is needed before commissioning a full compliance gap review (see
compliance-gap-matrix).
Required Inputs
- The official document: the full text of the rule, proposed rule, guidance, or notice — uploaded or pasted. This is mandatory. If it is not provided, stop and request it before proceeding. Do not summarize rules from model background knowledge alone.
- Organization description: a brief description of the organization's business, size, and the activities likely to be regulated, so the impact summary is relevant.
- Prior rule or baseline (if available): the text or description of the prior rule, if the user wants a "what changed" comparison. If not provided, flag that the comparison is limited to what the document itself states about changes.
- Jurisdiction and regulatory context: confirm which agency issued the document and in what jurisdiction (federal, state, foreign). Flag as
[CONFIRM]if not evident from the document.
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 · 149 lines · 35 tokens per session scan A 0026b127256e
Rule Change Summary is a skill published in the GitHub repository zgbrenner/agentcounsel (19 stars, last pushed 1mo ago), licensed MIT. It adds 35 tokens to every session and 2,681 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-03.
Other skills, from other repositories
cookie-consent-policy
Drafts publication-ready cookie policies, banner copy, and consent-flow language under GDPR/ePrivacy, CCPA/CPRA, and major U.S. state privacy laws. Converts a verified cookie inventory into enforceable policy sections with lawful-basis mapping, granular opt-in controls, withdrawal mechanics, and user-rights handling.…
cyber-law-compliance-summary
Produces structured cyber law compliance memoranda covering GDPR, CCPA, state privacy laws, and sector-specific regulations for US and EU operations. Includes Bluebook citations, jurisdiction comparison tables, penalty exposure, and regulatory trends. Use when advising on digital operations compliance, privacy program…
dsar-form
Drafts a GDPR- and CCPA-compliant Data Subject Access Request (DSAR) intake form for collecting requester information and processing privacy rights. Use when drafting DSAR forms, privacy rights request templates, or data subject rights workflows for EU/US-regulated organizations.
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.