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 LegalQuants/lq-ai --skill action-items-from-client-alertgit clone --depth 1 https://github.com/LegalQuants/lq-aiWrote 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/legalquants/lq-ai/action-items-from-client-alert)<a href="https://agentmods.dev/skills/legalquants/lq-ai/action-items-from-client-alert"><img src="https://agentmods.dev/badge/skills/legalquants/lq-ai/action-items-from-client-alert/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/legalquants/lq-ai/action-items-from-client-alert"><img src="https://agentmods.dev/badge/skills/legalquants/lq-ai/action-items-from-client-alert.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00092 | $0.03207 |
| Opus 5 | $0.00046 | $0.01604 |
| Sonnet 5 | $0.00018 | $0.00641 |
| Haiku 4.5 | $0.00009 | $0.00321 |
Grade A, and why
action-items-from-client-alert 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 13d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- action-items-from-client-alert — 92% identical, 29 lines differ
How it starts
The opening of the file, as written. The whole thing — 212 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Action Items from Client Alert
Extract time-sensitive action items, deadlines, and obligations from a client alert, regulatory bulletin, law firm memo, or similar legal update. Produce a deadline-organized checklist that an in-house lawyer can act on without re-reading the source document.
The skill is operational, not analytical. Action items are stated at the level of granularity the alert supports — typically high-level ("comply with new disclosure requirement by [date]"), not implementation-level ("update privacy policy section 4.2 by [date]"). The user knows their organization better than the skill does; the skill provides the trigger and deadline, not the implementation.
When this skill applies
Apply when the user provides a legal-update document and asks for action items, deadlines, or obligations to be extracted. Typical inputs:
- Law firm client alerts ("Client Alert: New SEC Cybersecurity Disclosure Rules Take Effect").
- Regulatory bulletins (FTC enforcement priorities; SEC staff guidance; agency Q&A documents).
- Law firm memos on regulatory developments or new statutes.
- Industry association updates distilling regulatory changes for members.
- Internal compliance bulletins if structured similarly to external alerts.
Do not apply when:
- The document is the underlying regulation, statute, or rule itself. Regulations are dense and structured for legal interpretation, not for action-item extraction. Recommend the user start with a client alert summarizing the regulation, or escalate to legal counsel for direct regulatory analysis.
- The document is a court opinion or judicial decision. Different shape; would warrant a case-summary skill (deferred enhancement candidate).
- The document is a private communication or strategy memo. Different shape; the skill is calibrated for published / shared alerts.
- The user wants an analysis of the legal change rather than action items. Action-item extraction is operational. If the user wants to understand the substantive legal change, recommend reading the alert directly or engaging counsel.
- The document is too vague to extract specific actions. Some alerts describe regulatory developments without imposing or describing specific requirements. The skill notes this and produces a "no specific action items extractable" output rather than fabricating actions.
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 13d ago First seen · 212 lines · 92 tokens per session scan A 3a253ec7cb2d
action-items-from-client-alert is a skill published in the GitHub repository LegalQuants/lq-ai (136 stars, last pushed yesterday), licensed Apache-2.0. It adds 92 tokens to every session and 3,207 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-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…
external-purchases
US web checkout via the StoreKit External Purchase Link entitlement — currently 0% Apple commission (litigation ongoing), how to ship it safely, and how to architect for a commission flip so a future ruling is a config change, not a rewrite. Use when adding external purchase links, weighing web checkout vs IAP, or…