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 portfolio-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/portfolio-status)<a href="https://agentmods.dev/skills/uk-agents/uk-legal-plugins/portfolio-status"><img src="https://agentmods.dev/badge/skills/uk-agents/uk-legal-plugins/portfolio-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/portfolio-status"><img src="https://agentmods.dev/badge/skills/uk-agents/uk-legal-plugins/portfolio-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.00063 | $0.01530 |
| Opus 5 | $0.00032 | $0.00765 |
| Sonnet 5 | $0.00013 | $0.00306 |
| Haiku 4.5 | $0.00006 | $0.00153 |
Grade A, and why
portfolio-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 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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/portfolio-status
- Load
~/.claude/plugins/config/uk-legal-plugins/litigation-legal-uk/CLAUDE.md→ risk calibration (defines how to read therisk:field). - Follow the workflow and reference below.
- Parse
~/.claude/plugins/config/uk-legal-plugins/litigation-legal-uk/matters/_log.yaml. Filter closed matters by default (include with--all). - Produce rollup: risk distribution, deadlines in next 14/30/60 days, matters with no update in >30 days, materiality totals, stage distribution.
- Flag anomalies — everything marked critical, overdue next_deadline, matters without external solicitors assigned where risk is medium or high.
Portfolio Status
Purpose
One read that answers: what do I own right now, what needs attention, and what's slipping? Output is scannable — designed for a counsel who has three minutes before their next call.
Load context
~/.claude/plugins/config/uk-legal-plugins/litigation-legal-uk/matters/_log.yaml— source of truth~/.claude/plugins/config/uk-legal-plugins/litigation-legal-uk/CLAUDE.md— risk calibration (to interpret risk/materiality fields correctly)
Flags & filters
Default: active matters only (exclude status: closed).
Flags:
--all— include closed--risk=high(orcritical/medium/low) — filter by risk band--stale— only matters withlast_updated> 30 days--type=employment— filter by matter type--owner=[name]— filter by business/HR/comms owner
The rollup
[WORK-PRODUCT HEADER — per plugin config ## Outputs — differs by role; see `## Who's using this`]
# Portfolio Status — [today]
**Active matters:** [N]
**Closed (ytd):** [N] *(shown only with --all)*
---
## By risk
| Risk | Count | Matters |
|---|---|---|
| Critical | [N] | [slugs] |
| High | [N] | [slugs] |
| Medium | [N] | [count only — expand with `--risk=medium`] |
| Low | [N] | [count only] |
## Upcoming CPR deadlines
| Within | Matters |
|---|---|
| 14 days | [slug — deadline — brief] |
| 15–30 days | [...] |
| 31–60 days | [...] |
*Overdue `next_deadline` flagged separately below. CPR deadlines computed from the log are leads — verify each against the court's case management directions and any applicable pre-action protocol before docketing.*
## Materiality
| Category | Count | Total exposure (midpoint, £) |
|---|---|---|
| Reserved | [N] | [£X] |
| Disclosed | [N] | [£X] |
| Monitored | [N] | — |
| None | [N] | — |
## By stage
[table: pre-action / pleadings / disclosure / witness statements / expert evidence / trial prep / settlement / appeal]
---
## ⚠️ Anomalies & flags
- **Overdue deadlines:** [list slugs where next_deadline has passed]
- **Stale (>30d no update):** [list]
- **Conflicts unresolved:** [list slugs with `conflicts.status in [pending, not-run]`]
- **Conflicts bypassed (override active):** [list slugs where `conflicts.override.by` is populated — permanent flag until manually cleared]
- **High/critical risk without external solicitors:** [list]
- **Reserved without last_updated in >60d:** [list] — reserve recalibration likely overdue
- **Hold not issued on active litigation:** [list]
- **Pre-action protocol compliance pending:** [list slugs where `pre_action_protocol` is set but no protocol compliance entry in history]
- **Missing fields:** [slug → field]
---
## Closing advice
[One or two sentences on what to look at first, if anything stands out. Not boilerplate — only if something truly stands out.]
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 First seen · 129 lines · 63 tokens per session scan A 65c24464d546
portfolio-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 63 tokens to every session and 1,530 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
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…
postgres
Use this skill for any PostgreSQL database work — table design, indexing, data types, constraints, extensions (pgvector, PostGIS, TimescaleDB), search, and migrations. Trigger when user asks to: Design or modify PostgreSQL tables, schemas, or data models Choose data types, constraints, indexes, or partitioning…
revenue-recognition
Determines when and how revenue is recognized — performance obligations, contract terms that change the answer, and the deal structures that create accounting problems. Use this to work out how a contract should be recognized, review a non-standard deal before it is signed, understand deferred revenue, or spot terms…
privacy-and-data-protection
Assesses and improves how personal data is collected, used, shared, and retained — data mapping, lawful basis, consent, processor agreements, subject rights, and breach obligations. Use this before launching anything that handles personal data, when adding a vendor that will process it, when a data subject request…
benefits-and-leave
Designs and runs employee benefits and leave — health and retirement plans, leave policy, cost and renewal, and the administration that keeps them compliant. Use this to design or review a benefits package, prepare for a renewal, write leave policy, handle a leave request, or decide what benefits are worth their cost.
compensation-and-leveling
Builds and maintains the leveling framework and pay structure — level definitions, salary bands, benchmarking, pay equity, and how raises and promotions are decided. Use this to design or revise leveling, set or adjust salary bands, benchmark against market, handle a compensation request or counteroffer, run a review…