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-skills --skill lq-board-document-reviewgit clone --depth 1 https://github.com/LegalQuants/lq-skillsWrote 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-skills/lq-board-document-review)<a href="https://agentmods.dev/skills/legalquants/lq-skills/lq-board-document-review"><img src="https://agentmods.dev/badge/skills/legalquants/lq-skills/lq-board-document-review/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-skills/lq-board-document-review"><img src="https://agentmods.dev/badge/skills/legalquants/lq-skills/lq-board-document-review.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.00068 | $0.01958 |
| Opus 5 | $0.00034 | $0.00979 |
| Sonnet 5 | $0.00014 | $0.00392 |
| Haiku 4.5 | $0.00007 | $0.00196 |
Grade A, and why
lq-board-document-review 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 12d 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LQ Board Document Review Protocol
You are conducting a formal governance review. Be rigorous, concise, and structured. Partners read these findings at 06:30. No filler.
Operating Principles
- Governance first, prose second. Every finding must identify an accountability consequence — not just a stylistic flaw.
- Trace every assertion to source. For each finding, cite the specific Section, Schedule row, or cell reference. Never paraphrase without a citation.
- Distinguish severity honestly. A missing defined term is not the same as a Policy-vs-Matrix threshold conflict. Over-calling severity destroys the report's value at the board table.
- Never silently accept edits. All amendments must be proposed as tracked changes. The human reviewer approves.
Privilege Treatment
Board papers, board minutes, resolutions, committee terms of reference, related party transaction policies, and the work product produced by this skill (tracked-change redlines, the Reconciliation Log, and the findings slide) are privileged governance work product. Treat them as such by default.
- Confirm before invoking external tools. Do not call any external tool — web fetch, search, third-party MCP, file transmission outside the working documents, or any network-egressing action — until the user has explicitly confirmed that doing so will not breach legal professional privilege, board confidentiality, or any applicable NDA. If in doubt, ask and halt.
- Label working drafts. Treat each output as a working draft for the named reviewer. The user is expected to apply their firm's standard privilege marking ("Privileged & Confidential — Prepared at the Direction of Counsel" or equivalent) before circulation. Do not strip or alter any existing privilege headers/footers in the source document.
- No external transmission by default. Do not upload, paste, summarise, or otherwise transmit the document or any extract to a system outside the user's local working environment without explicit per-instance confirmation.
- Privilege survives the skill. Findings, redlines, and the slide carry the same privilege status as the input. Do not produce a "sanitised" or "public" version unless the user expressly asks for one and confirms the privilege implications.
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.
- 12d ago First seen · 119 lines · 68 tokens per session scan A 1b88b292b7cb
lq-board-document-review is a skill published in the GitHub repository LegalQuants/lq-skills (54 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 68 tokens to every session and 1,958 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-08-30.
Other skills, from other repositories
EU AI Act Documentation
What compliance documentation to produce under the EU AI Act — Annex IV technical documentation, EU declaration of conformity, risk-management file, data-governance records, and GPAI training-data summary — and how to structure it.
achieving-cmmc-level-2-compliance
Prepare a defense-contractor environment for CMMC Level 2 certification: scope CUI and FCI, implement the 110 NIST SP 800-171 Rev 2 security requirements across 14 families, compute the SPRS score with the DoD Assessment Methodology, manage a compliant POA&M, and ready the organization for a C3PAO assessment. Use when…
implementing-gdpr-data-protection-controls
The General Data Protection Regulation (EU) 2016/679 (GDPR) is the EU's comprehensive data protection law governing the collection, processing, storage, and transfer of personal data. This skill cover.
implementing-pci-dss-compliance-controls
PCI DSS 4.0.1 establishes 12 requirements across 6 control objectives for organizations that store, process, or transmit cardholder data. With PCI DSS 3.2.1 retiring April 2024 and 51 new requirements.
audit-export
Export the full CocoAudit trail as a stakeholder-ready compliance document.
compliance
Use when scoping which regulatory frameworks bind a business — SOC 2, ISO 27001, HIPAA, PCI DSS, EU AI Act, DORA, NIS2 — building a control register with owners and evidence, or standing up the cadence that keeps it audit-ready. NOT drafting privacy-policy/ROPA/DPA or ToS text (that is gdpr-privacy, terms-conditions)…