Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add eigenlegal/counsel-os/plugin install 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/update)<a href="https://agentmods.dev/skills/eigenlegal/counsel-os/update"><img src="https://agentmods.dev/badge/skills/eigenlegal/counsel-os/update/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/update"><img src="https://agentmods.dev/badge/skills/eigenlegal/counsel-os/update.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.00025 | $0.03913 |
| Opus 5 | $0.00013 | $0.01956 |
| Sonnet 5 | $0.00005 | $0.00783 |
| Haiku 4.5 | $0.00003 | $0.00391 |
Grade A, and why
update 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 8d 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 — 313 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update — Skill-First Sync
Counsel OS updates are LLM-orchestrated. The skill decides what is safe to do in the current runtime, explains each step, and asks before changing user-owned knowledge.
Step 0: Resolve Plugin Root
Resolve the plugin root first: the directory containing this skill. You need this to distinguish plugin documentation from the user's legal root and to find shipped content.
Step 1: Migrate Config If Needed
This is a one-time migration path for users upgrading from earlier Counsel OS versions. It is intentionally limited to /counsel-os:update; normal counsel/setup path discovery remains strict and does not silently accept legacy config.
Current config format
A valid legal-root config is marked:
counsel-os-config: true
legal_root: /absolute/path/to/legal/root
Migration trigger
First try the Finding the Legal Root procedure in skills/counsel/SKILL.md.
- If it finds a marked config, skip this migration.
- If it finds no marked config, attempt the migration below.
- If it finds multiple marked configs, ask the user which one to use and skip migration.
Migration sources
Check these sources in order. A source may be read only for this migration, not as a recurring fallback.
- Pointer file at
~/.counsel-os/legal-rootif home-directory access is available. If it points to a directory that exists, treat that directory as the candidate legal root. - Legacy plugin config at
{plugin_root}/config.local.md, if present. Read onlylegal_root:,entities_path:,matters_path:, andentity_properties:fields. - User-provided path. If no source is found, ask: "Where is your existing Counsel OS legal root?"
Do not scan arbitrary unmarked config.md files. That was the old failure mode: plugin documentation or unrelated project files could be mistaken for user config.
Candidate validation
Before writing anything, validate the candidate legal root:
- The path is outside the plugin root.
- The directory exists, or the user approved creating it.
- Prefer candidates containing at least one Counsel OS directory:
law/,practice/,matters/,memory/, orentities/. - If the candidate has an existing
config.md, preserve optional overrides from it only if it appears to be user config. Do not preserve unrelated prose or plugin docs.
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.
- 8d ago Changed · +2 lines 78ec52b0c015
- 12d ago First seen · 311 lines · 25 tokens per session scan A 7c7259d99ccf
update is a skill published in the GitHub repository eigenlegal/counsel-os (24 stars, last pushed yesterday), licensed MIT. It adds 25 tokens to every session and 3,913 once invoked, about $0.0001 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…