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 client-comms-loggit 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/client-comms-log)<a href="https://agentmods.dev/skills/uk-agents/uk-legal-plugins/client-comms-log"><img src="https://agentmods.dev/badge/skills/uk-agents/uk-legal-plugins/client-comms-log/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/client-comms-log"><img src="https://agentmods.dev/badge/skills/uk-agents/uk-legal-plugins/client-comms-log.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.00090 | $0.01844 |
| Opus 5 | $0.00045 | $0.00922 |
| Sonnet 5 | $0.00018 | $0.00369 |
| Haiku 4.5 | $0.00009 | $0.00184 |
Grade A, and why
client-comms-log 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 9d 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/legal-clinic-uk:client-comms-log
- Use the workflow below.
- Require case-id (prompt if not provided).
- Route by flag:
--add(default): capture direction, medium, student, summary, action items, follow-up due. Confirm with user. Append (prepend most-recent-first) to~/.claude/plugins/config/uk-legal-plugins/legal-clinic-uk/client-comms/[case-id]/log.md.--read: show the most recent N entries.--summary: one-paragraph condensed read.--patterns: scan for unanswered comms, missed follow-ups, language gaps, tone shifts, contact gaps. Supervision-oriented.
- Integration: offer
/legal-clinic-uk:deadlines --addif the log establishes a deadline; route to/legal-clinic-uk:semester-handoffvia--summarywhen relevant.
Client Communications Log
Purpose
Four reasons to keep this log in a UK law school clinic:
- Professional negligence defence. If a client claims "no one ever told me [X]," a dated entry showing otherwise is the answer. The supervising solicitor or barrister carries professional responsibility on student work; contemporaneous records protect them and the clinic. The SRA Minimum Terms and Conditions for professional indemnity insurance require adequate records management.
[SRA-CODE] - Continuity at handoff. The next term's student takes over and reads the log; they don't re-ask the client questions already answered.
- Supervision visibility. Five unreturned calls over six weeks is a pattern. The log makes patterns visible that individual students might not flag on their own.
- File retention. UK law school clinics have obligations (professional, regulatory, and under data protection legislation) to maintain complete client files. Communication history is part of that.
Light. Append-only. The student's job is to write a two-sentence entry after every contact; the skill formats it and appends.
Data protection note. Entries in this log contain personal data and may be sensitive (health, immigration status, family circumstances). They must be kept securely, accessible only to the clinic team, and retained only for as long as needed per the clinic's data retention policy. Any access or sharing outside the supervising team requires a lawful basis under UK GDPR. [model knowledge — verify against clinic's data protection policy]
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.
- 9d ago First seen · 123 lines · 90 tokens per session scan A ff723079b1d4
client-comms-log 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 90 tokens to every session and 1,844 once invoked, about $0.0005 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…
employment-compliance
Covers the employment rules that carry real penalties — exempt and non-exempt classification, overtime and hours, employee versus contractor status, work authorization and recordkeeping, accommodation requests, and the notices and retention obligations that go with them. Use this to classify a role, review a…
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.