What is set-up-my-legal-info?

A shared company information file for legal work, covering your company structure, ownership, current agreements, templates, and known risks. It is created through a short question-and-answer process and updated when those facts change.

Use it to set up or update the legal background needed for contract drafting, trademark checks, compliance reviews, and answers to legal questions.

It prevents you from repeating the same company background every time you ask for legal help and gives later drafts and reviews the right context. It preserves existing information and changes only what is new or outdated.

set-up-my-legal-info — Skill for Claude Code and Codex by akiotanaka84

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 akiotanaka847/qaio-desktop --skill set-up-my-legal-info

Clone the repo

git clone --depth 1 https://github.com/akiotanaka847/qaio-desktop

Made for: Claude Code, Codex.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/akiotanaka847/qaio-desktop/set-up-my-legal-info/github.svg)](https://agentmods.dev/skills/akiotanaka847/qaio-desktop/set-up-my-legal-info)

Your own site

<a href="https://agentmods.dev/skills/akiotanaka847/qaio-desktop/set-up-my-legal-info"><img src="https://agentmods.dev/badge/skills/akiotanaka847/qaio-desktop/set-up-my-legal-info/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/akiotanaka847/qaio-desktop/set-up-my-legal-info"><img src="https://agentmods.dev/badge/skills/akiotanaka847/qaio-desktop/set-up-my-legal-info.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 64 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,261 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.

Model	Per session	Once invoked
Fable 5.1	$0.00064	$0.01261
Opus 5	$0.00032	$0.00630
Sonnet 5	$0.00013	$0.00252
Haiku 4.5	$0.00006	$0.00126

Measured 12d ago against content hash 1998dc8e3e67, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

set-up-my-legal-info 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.

store/agents/legal/.agents/skills/set-up-my-legal-info/SKILL.md · 72 lines

How it starts

The opening of the file, as written. The whole thing — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Set Up My Legal Info

This is the foundation document this agent reads before every substantive task. The skill creates or updates it through a short conversation with the user.

When to use

"set up my legal context" / "draft the legal context doc" / "build shared legal doc".
"update legal context" / "our cap table changed, fix doc" / "just executed Acme MSA, add to standing agreements".
Called implicitly by any other skill needing shared context when doc missing - only after confirming with user.

Steps

Read config. Load config/entity.json, config/posture.json, config/templates.json, config/profile.json. If any missing, ask ONE missing piece just-in-time using plain language (best-modality hint: connected app > file drop > URL > paste).
Read existing doc if present. If legal-context.md exists, read so run is update, not rewrite. Preserve founder-sharpened parts; change only stale or new.
Pull cap table + standing agreements if sources connected. If cap-table tool connected (composio search cap-table - Carta / Pulley / other), pull current snapshot (founder stake, option pool, priced round terms), capture source + last update date. Do not invent numbers. If nothing connected, ask founder for one-line snapshot, mark source "self-reported".
Ask minimum just-in-time questions. Interview covers only what config didn't answer:
- Cap table snapshot (if no Carta/Pulley linked) - founder stake, option pool, priced-round terms.
- Standing agreements in force - customer / vendor / contractor / investor summaries (1 line each, not full text).
- Open risks - un-filed 83(b)? unsigned CIIAA? expired DPA? undocumented contractor IP? Anything founder knows unresolved.
- Escalation rules - anything founder wants always escalated (e.g. "always flag > $50K ACV deals").
Draft doc (~400-600 words, direct, verb-led). Structure, in order:
1. Entity - name, state, entity type, formation date, authorized shares, par value, registered agent, incorporated via. Mark TBD for anything missing.
2. Cap table snapshot - last update date, source (Carta / Pulley / spreadsheet / self-reported), founder stake, option pool, priced-round terms (if any).
3. Standing agreements - bulleted list by category (customers, vendors, contractors, investors). One line per agreement: counterparty, type, effective date, term / auto-renewal, key obligations. Summary only, not full text.
4. Template stack - pointers to current NDA / MSA / consulting / offer / DPA templates. Each with version + last-reviewed date. Mark none if founder has no template for that kind.
5. Open risks - bulleted. Each with severity (low / med / high) + one-line description. Escalate severity high in dashboard.
6. Founder risk posture - stance (aggressive / middle / conservative) + clause-level color from config/posture.json. Keep verbatim founder notes where given.
7. Escalation rules - what I will and won't handle without human lawyer. Default floor: anything over $100K ACV, any non-standard indemnity, any IP going out, any cell at major × likely on 5×5 severity×likelihood read.

Read the full file on GitHub · 72 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.

12d ago First seen · 72 lines · 64 tokens per session scan A 1998dc8e3e67

Subscribe to this mod's changes

set-up-my-legal-info is a skill published in the GitHub repository akiotanaka847/qaio-desktop (2 stars, last pushed 8d ago), licensed MIT. It adds 64 tokens to every session and 1,261 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-31.

Legal and compliance setup

AI Governance Cold-Start Interview

Use when an AI-governance practice group is adopting AgentCounsel and needs to configure its practice profile by answering a structured interview covering jurisdictions, client context, escalation thresholds, output preferences, source documents, standard positions, review requirements, and prohibited assumptions.

zgbrenner/agentcounsel · 58 tokens

Antitrust / Competition Cold-Start Interview

Use when an antitrust / competition practice group is adopting AgentCounsel and needs to configure its practice profile by answering a structured interview covering jurisdictions, client context, escalation thresholds, output preferences, source documents, standard positions, review requirements, and prohibited…

zgbrenner/agentcounsel · 60 tokens

Bankruptcy and Restructuring Cold-Start Interview

Use when a bankruptcy and restructuring practice group is adopting AgentCounsel and needs to configure its practice profile by answering a structured interview covering jurisdictions, client context, escalation thresholds, output preferences, source documents, standard positions, review requirements, and prohibited…

zgbrenner/agentcounsel · 61 tokens

Corporate Cold-Start Interview

Use when a corporate practice group is adopting AgentCounsel and needs to configure its practice profile by answering a structured interview covering jurisdictions, client context, escalation thresholds, output preferences, source documents, standard positions, review requirements, and prohibited assumptions.

zgbrenner/agentcounsel · 54 tokens

Employment Cold-Start Interview

Use when an employment practice group is adopting AgentCounsel and needs to configure its practice profile by answering a structured interview covering jurisdictions, client context, escalation thresholds, output preferences, source documents, standard positions, review requirements, and prohibited assumptions.