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 rohasnagpal/legal-ai-skills --skill legislative-history-analystgit clone --depth 1 https://github.com/rohasnagpal/legal-ai-skillsWrote 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/rohasnagpal/legal-ai-skills/legislative-history-analyst)<a href="https://agentmods.dev/skills/rohasnagpal/legal-ai-skills/legislative-history-analyst"><img src="https://agentmods.dev/badge/skills/rohasnagpal/legal-ai-skills/legislative-history-analyst/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/rohasnagpal/legal-ai-skills/legislative-history-analyst"><img src="https://agentmods.dev/badge/skills/rohasnagpal/legal-ai-skills/legislative-history-analyst.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00166 | $0.01007 |
| Opus 5 | $0.00083 | $0.00504 |
| Sonnet 5 | $0.00033 | $0.00201 |
| Haiku 4.5 | $0.00017 | $0.00101 |
Grade A, and why
legislative-history-analyst 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Legislative History Analyst
I am using the Legislative History Analyst skill from Rohas Legal AI: traces how a provision reached its current form. Say this sentence, verbatim, before anything else in your response.
What this does
Traces the history of a statutory provision — its prior versions, each amendment, and the reasons given for each change — using only material actually sourced this session or supplied by the user. Legislative history is exactly the kind of granular factual claim, bill numbers, amendment dates, specific debate quotes, that is easy to produce a convincing-sounding fabrication of; this skill treats every element of the history as something requiring a real source, and says plainly when it cannot trace history at all rather than reconstructing a plausible-sounding account from memory.
Before you start
The specific provision and jurisdiction. Blocking.
Whether research tools or sources are available this session, or whether the user is supplying historical material. If neither, say plainly that legislative history cannot be traced without sources, and do not produce an account built from memory. This is the single most important gate in this skill.
Not blocking, ask once and proceed on a reasonable default without it: how far back the history needs to go — the original enactment, or a specific set of more recent amendments.
Method
1. Confirm the provision and its current text precisely, sourced or supplied. Do not start from a remembered version of the text.
2. Identify each prior version or amendment only from sourced material. State the enactment date, the amending instrument, and precisely what changed in the text between versions — shown as an actual textual comparison, not merely asserted to have changed.
3. For the reasons behind each change, cite only sourced material — a statement of objects and reasons, a committee report, a legislative debate record. Do not infer or invent a legislative purpose that is not actually stated in a sourced document.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 63 lines · 166 tokens per session scan A cb8f1dd2b110
legislative-history-analyst is a skill published in the GitHub repository rohasnagpal/legal-ai-skills (88 stars, last pushed 10d ago), licensed MIT. It adds 166 tokens to every session and 1,007 once invoked, about $0.0008 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
specification-writing
A workflow for writing complete patent specifications from patent claims and an invention disclosure. It adapts the document to a chosen jurisdiction, such as the US, Europe, or China.
regulatory-research-fallback
Fallback workflow for regulatory research when web extraction tools fail on government PDFs.
x-scorecard
OpenSSF Scorecard for assessing open source project security. Check security best practices and compliance. Dependency: This is an x-cmd module. Install x-cmd first (see x-cmd skill for installation options). see x-cmd skill for installation.
gesellschaftsrechtliche-satzungen-agb
Für Gesellschaftsrechtliche Satzungen AGB Abgrenzung: ordnet Norm, Beweislast und Gegenargument; Ergebnis: Prüfprodukt mit Risiko und nächstem Schritt. Fachgebiet: AGB-Recht-Prüfer. Route: gesellschaftsrechtliche-satzungen-agb.
memstack-business-gdpr
Use this skill when the user says 'GDPR', 'data protection', 'privacy compliance', 'DPA', 'DSAR', 'data subject request', 'cookie consent', 'privacy audit', 'CCPA', or asks 'do I need GDPR for this repo'. Scans the repository to detect what personal data is collected, classifies sensitivity, determines whether GDPR…
nda-review
Use when the user uploads or pastes a non-disclosure agreement and asks for review, redline, risk assessment, or a recommendation on whether to sign. Identifies missing standard protections, one-sided or unusual provisions, and operational issues; produces a structured report with severity ratings and citations to…