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 eigenlegal/counsel-os --skill law-refreshgit clone --depth 1 https://github.com/eigenlegal/counsel-osWrote 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/eigenlegal/counsel-os/law-refresh)<a href="https://agentmods.dev/skills/eigenlegal/counsel-os/law-refresh"><img src="https://agentmods.dev/badge/skills/eigenlegal/counsel-os/law-refresh/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/eigenlegal/counsel-os/law-refresh"><img src="https://agentmods.dev/badge/skills/eigenlegal/counsel-os/law-refresh.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 14 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00112 | $0.01433 |
| Opus 5 | $0.00056 | $0.00717 |
| Sonnet 5 | $0.00022 | $0.00287 |
| Haiku 4.5 | $0.00011 | $0.00143 |
Grade A, and why
law-refresh 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 12d 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Law Refresh — User-Owned Content
You are refreshing the legal currency of law files the USER owns. This skill never touches plugin-managed law content — that is refreshed upstream by the plugin maintainers (see docs/law-refresh-runbook.md in the plugin repo) and reaches the vault through /counsel-os:update.
The method is verify-and-patch, not rewrite: find perishable claims, verify them against primary sources, patch only what changed, and attest what was reviewed. Calibrated on the upstream refresh pipeline (2026-06).
Step 0: Resolve Paths and Scope
- Resolve
{legal_root}via the Finding the Legal Root procedure inskills/counsel/SKILL.md. - Read
{legal_root}/config.mdforlaw_management:. - Classify every file under
{legal_root}/law/:- User-owned if ANY of: (a)
law_management: useris set in config.md (everything is user-owned); (b) the file's frontmatter containsmanaged-by: user; (c) the file's area does not exist in the plugin'sknowledge/law/(a custom area the user created). - Plugin-managed otherwise.
- User-owned if ANY of: (a)
- Scope = user-owned files only. If the user asks to refresh a plugin-managed area, decline and explain: it is refreshed upstream with source verification and arrives via
/counsel-os:update. If they want to own it anyway, the deliberate fork is: addmanaged-by: userto the file's frontmatter — update will stop syncing it permanently, and this skill will maintain it from then on. Make sure they understand the trade (they take over its maintenance forever). - If nothing is user-owned, say so and stop — the user's whole library is maintained upstream.
Report the scope before doing any work: N user-owned files in M areas, and why each is in scope.
Step 1: Extract Perishable Claims
For each in-scope file, extract the claims that can go stale: effective dates, dollar thresholds and penalty figures, rule statuses (proposed / final / enjoined / vacated / rescinded), case postures, "no law yet" / "pending" assertions, named-bill statuses, agency-guidance citations.
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.
- 12d ago First seen · 68 lines · 112 tokens per session scan A 5edc18dea93e
law-refresh is a skill published in the GitHub repository eigenlegal/counsel-os (24 stars, last pushed yesterday), licensed MIT. It adds 112 tokens to every session and 1,433 once invoked, about $0.0006 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-08-30.
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…