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 uk-agents/uk-legal-plugins --skill oc-statusgit clone --depth 1 https://github.com/uk-agents/uk-legal-pluginsWrote 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/uk-agents/uk-legal-plugins/oc-status)<a href="https://agentmods.dev/skills/uk-agents/uk-legal-plugins/oc-status"><img src="https://agentmods.dev/badge/skills/uk-agents/uk-legal-plugins/oc-status/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/uk-agents/uk-legal-plugins/oc-status"><img src="https://agentmods.dev/badge/skills/uk-agents/uk-legal-plugins/oc-status.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.00060 | $0.02136 |
| Opus 5 | $0.00030 | $0.01068 |
| Sonnet 5 | $0.00012 | $0.00427 |
| Haiku 4.5 | $0.00006 | $0.00214 |
Grade A, and why
oc-status 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 7d 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 — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/oc-status
To run weekly, set a recurring reminder to invoke /litigation-legal-uk:oc-status. Automated scheduling requires a scheduled-tasks integration, which is not bundled.
- Load
~/.claude/plugins/config/uk-legal-plugins/litigation-legal-uk/matters/_log.yaml, filter per default rules (or per flags). - Load
~/.claude/plugins/config/uk-legal-plugins/litigation-legal-uk/CLAUDE.md→ external solicitors directive style, signer defaults, budget posture. - Follow the workflow and reference below.
- For each matter in scope: read
matter.md+history.md, draft per-matter email. - Write markdown to
~/.claude/plugins/config/uk-legal-plugins/litigation-legal-uk/oc-status/[YYYY-MM-DD]/[slug].md. - If Gmail MCP authenticated: create Gmail drafts. Else: markdown-only, note in summary.
- Write
~/.claude/plugins/config/uk-legal-plugins/litigation-legal-uk/oc-status/[YYYY-MM-DD]/_summary.md— what ran, what was skipped and why.
External Solicitors Status
Purpose
Writing the same status-request email to external solicitors every week across 5–15 matters is mechanical cognitive tax. The content is consistent per matter (status, decisions pending, budget check). The audience is consistent (lead solicitor at the instructed firm). The tone is consistent (per house external-solicitors-directive style). A scheduled task drafts all of them; counsel reviews and sends.
Load context
~/.claude/plugins/config/uk-legal-plugins/litigation-legal-uk/matters/_log.yaml— the filtering and field source~/.claude/plugins/config/uk-legal-plugins/litigation-legal-uk/matters/[slug]/matter.md— matter context (current posture, open questions)~/.claude/plugins/config/uk-legal-plugins/litigation-legal-uk/matters/[slug]/history.md— recent events to inform what to ask about~/.claude/plugins/config/uk-legal-plugins/litigation-legal-uk/CLAUDE.md→ external solicitors directive style, signer name/email, budget posture
Filtering — which matters?
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.
- 7d ago First seen · 160 lines · 60 tokens per session scan A 494b72f076f9
oc-status is a skill published in the GitHub repository uk-agents/uk-legal-plugins (9 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 60 tokens to every session and 2,136 once invoked, about $0.0003 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
reply-triage
A sorting guide for creator replies, emails, and automation results. It puts incoming items into five priority groups and suggests what to do next.
brand-safety-compliance
Scans outbound copy or creator-submitted content for 6 compliance red lines — medical/efficacy, exaggeration/absolute, beauty-permanence, financial/income, fake-scarcity, fake-rapport — and returns a block/warn verdict with fix suggestions. Use when the user asks to check, scan, review, or vet copy before sending, or…
situate-what
Use when the user asks what is going on and needs a five-line summary of the session, branch, pull request, and ticket.
idea
Quick-capture an idea to the scratch inbox. Use when the user explicitly asks to capture: "capture this", "add to ideas", "don't let me forget", "log this idea", /memex:idea. Not for every "we should eventually..." aside -- most asides aren't capture-intent. Not for decisions (decisions.md) or state claims (closets…
ws
Create and run workstations - permanent areas for routine, repeated work (independent of projects). Actions - new WS, new subWS, new area, new routine, run, from project, list, overview. Hierarchy depth (2 or 3 levels) is fixed at creation.
disk-reclaim
Reclaim disk space through a proof-gated plan — clears regenerable caches, merges proved-redundant copies, and protects agent history.