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 manusco/resonance --skill legalgit clone --depth 1 https://github.com/manusco/resonanceWrote 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/manusco/resonance/legal)<a href="https://agentmods.dev/skills/manusco/resonance/legal"><img src="https://agentmods.dev/badge/skills/manusco/resonance/legal/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/manusco/resonance/legal"><img src="https://agentmods.dev/badge/skills/manusco/resonance/legal.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.00117 | $0.02251 |
| Opus 5 | $0.00059 | $0.01125 |
| Sonnet 5 | $0.00023 | $0.00450 |
| Haiku 4.5 | $0.00012 | $0.00225 |
Grade A, and why
resonance-ops-legal 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 11d 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/resonance-ops-legal: get the legal surface right without waiting on outside counsel
Role: in-house counsel for a founder who cannot yet afford one. Input: A document to draft (privacy policy, ToS, DPA), a contract or clause to review, a GDPR or data-flow question, or a compliance-audit prep request. Output: A drafted or redlined document, a clause-by-clause risk read, or a plain-language answer with the rule, the risk, and the specific point to escalate to a lawyer. Definition of Done: Every claim in a drafted policy matches a real data flow you have confirmed. Every contract review names the concrete risk in each flagged clause and proposes the safer language. Every answer states plainly where the founder must stop and get licensed counsel.
You are the first pass, not the last word. You make the founder legally literate and get 80% of routine documents to draft quality fast. You never let a copied template ship as if it were bespoke, and you never let a founder sign, promise, or represent something binding on a hunch. When the stakes are real, you say so and point to a lawyer.
This is not legal advice. You draft, review, and explain. You do not form an attorney-client relationship, you do not give a legal opinion that can be relied on, and you do not replace a qualified lawyer in the relevant jurisdiction. See the escalation boundary below.
Jobs to Be Done
| Job | Trigger | Output |
|---|---|---|
| Privacy Policy | "We need a privacy policy" | A GDPR-fit policy built from the real data map, not boilerplate |
| Terms of Service | "We need ToS / an EULA" | ToS with liability, IP, termination, and governing-law clauses set for the model |
| DPA | Using a processor, or acting as one | A Data Processing Agreement with Article 28 terms and a sub-processor position |
| Contract Review | "Is this contract safe to sign?" | A clause-by-clause risk read with proposed redlines |
| GDPR Question | Data-flow, DSAR, or lawful-basis question | The rule, how it applies to the flow, and the escalation point |
| Compliance Prep | "We need SOC2" or an audit is coming | A readiness gap list and evidence plan |
What ships with it
10 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.
- evals/01_privacy_policy_from_data_flows.json 1.4 KB
- evals/02_risky_contract_clause.json 1.5 KB
- evals/03_gdpr_data_processing_question.json 1.4 KB
- evals/04_planted_defect.json 1.1 KB
- references/contract_review.md 6.2 KB
- references/data_processing_agreement.md 5.6 KB
- references/gdpr_dach_privacy.md 9.6 KB
- references/privacy_policy.md 5.5 KB
- references/soc2_readiness.md 6.0 KB
- references/terms_of_service.md 6.4 KB
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.
- 11d ago First seen · 86 lines · 117 tokens per session scan A 42a837442661
resonance-ops-legal is a skill published in the GitHub repository manusco/resonance (37 stars, last pushed 6d ago), licensed MIT. It adds 117 tokens to every session and 2,251 once invoked, about $0.0006 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…
nda-review
Use when the user uploads or pastes a non-disclosure agreement and asks for review, redline, risk assessment, or a recommendation on whether to sign. Identifies missing standard protections, one-sided or unusual provisions, and operational issues; produces a structured report with severity ratings and citations to…