portfolio-status

portfolio-status is a skill for Claude Code from uk-agents/uk-legal-plugins. It costs 63 tokens per session (1,530 once invoked), scanned A, original, Apache-2.0.

A portfolio reporting workflow for active legal matters. It reads the portfolio log and summarises risk, upcoming court deadlines, stale records, financial materiality, stages, and unusual gaps.

In plain words
What is it for?
Use it to answer how many active matters exist, where risks are concentrated, and which deadlines are approaching. It can also include closed matters when requested.
Why use it?
It gives legal teams a single view of what needs attention across many matters. It helps reveal overdue deadlines, neglected updates, critical risks, and missing solicitor assignments.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: reads .claude/ paths; mentions CLAUDE.md.

Part of the litigation-legal-uk plugin — 16 skills, 1 agent shipped together

Good fit Use it to answer how many active matters exist, where risks are concentrated, and which deadlines are approaching. It can also include closed matters when requested.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/uk-agents/uk-legal-plugins/portfolio-status
Install

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.

Any agent
npx skills add uk-agents/uk-legal-plugins --skill portfolio-status
Clone the repo
git clone --depth 1 https://github.com/uk-agents/uk-legal-plugins

Made for: Claude Code.

Or install litigation-legal-uk, the plugin that ships this one along with the rest of its 16 skills, 1 agent.

Wrote 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.

agentmods badge for portfolio-status

README.md
[![agentmods](https://agentmods.dev/badge/skills/uk-agents/uk-legal-plugins/portfolio-status/github.svg)](https://agentmods.dev/skills/uk-agents/uk-legal-plugins/portfolio-status)
Your own site
<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.

agentmods 80×15 button for portfolio-status

Your own site · 80×15
<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>
Per session 63 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,530 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 8d ago against content hash 65c24464d546, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

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.

litigation-legal-uk/skills/portfolio-status/SKILL.md · 129 lines

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

  1. Load ~/.claude/plugins/config/uk-legal-plugins/litigation-legal-uk/CLAUDE.md → risk calibration (defines how to read the risk: field).
  2. Follow the workflow and reference below.
  3. Parse ~/.claude/plugins/config/uk-legal-plugins/litigation-legal-uk/matters/_log.yaml. Filter closed matters by default (include with --all).
  4. Produce rollup: risk distribution, deadlines in next 14/30/60 days, matters with no update in >30 days, materiality totals, stage distribution.
  5. 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 (or critical / medium / low) — filter by risk band
  • --stale — only matters with last_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.]

Read the full file on GitHub · 129 lines

Changes

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.

  1. 8d ago First seen · 129 lines · 63 tokens per session scan A 65c24464d546

Subscribe to this mod's changes

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.

Related

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…

crevideo/crevideo-reach · 139 tokens

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…

timescale/pg-aiguide · 197 tokens

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…

cbrock84/headcount · 69 tokens

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…

cbrock84/headcount · 86 tokens

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.

cbrock84/headcount · 68 tokens

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…

cbrock84/headcount · 75 tokens