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 agentmods add skills/protomated/protomated-plugins-official/intake-summarynpx skills add protomated/protomated-plugins-official --skill intake-summarygit clone --depth 1 https://github.com/protomated/protomated-plugins-officialWrote 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/protomated/protomated-plugins-official/intake-summary)<a href="https://agentmods.dev/skills/protomated/protomated-plugins-official/intake-summary"><img src="https://agentmods.dev/badge/skills/protomated/protomated-plugins-official/intake-summary.svg" alt="Measured on agentmods" 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 | $0.00057 | $0.01558 |
| Opus 5 | $0.00028 | $0.00779 |
| Sonnet 5 | $0.00011 | $0.00312 |
| Haiku 4.5 | $0.00006 | $0.00156 |
Grade A, and why
intake-summary 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 4d 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 — 216 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/intake-summary — Intake Summary Processor
⚠️ AI-ASSISTED DRAFT — ATTORNEY REVIEW REQUIRED This output was generated by an AI assistant. It has not been reviewed by a licensed attorney. Review all facts, dates, and claims before relying on this summary or sharing it with anyone. This is not legal advice.
Convert raw intake notes into a structured case brief. The output becomes the intake-summary.md file at the top of the matter folder — the anchor document every other skill reads from.
Invocation
/intake-summary [matter folder path]
/intake-summary [paste raw notes here]
Workflow
Step 1 — Collect raw intake data
Option A — From a matter folder: Use the Filesystem connector to locate the matter folder. Look for:
- Any
.md,.txt, or.docxintake file - Raw notes from a consultation
- A completed intake form (PDF or text)
Option B — From pasted notes: If the attorney pastes notes directly, accept them as-is and proceed.
If neither is available, ask the attorney to provide or paste the intake information. Prompt with the fields below.
Step 2 — Extract and structure the information
Identify and organize the following fields from the raw notes. Mark any field as [Not provided] if absent — do not infer or fabricate.
Parties:
- Client full name, date of birth (if relevant), address, phone, email
- Counterparty / adverse party name, address, known contact info
- Relevant third parties (insurers, employers, witnesses)
Matter:
- Practice area / claim type (personal injury, contract dispute, family law, employment, etc.)
- Brief factual summary: what happened, when, where, who was involved
- Date of incident or triggering event
- Prior legal action (existing case number, prior attorneys, settlements)
Damages or Relief Sought:
- Claimed injuries, losses, or damages (itemize if notes permit)
- Type of relief requested (monetary, injunctive, declaratory)
Deadlines and Statutes of Limitations:
- Applicable statute of limitations (flag if attorney has not addressed this — it is a critical malpractice risk)
- Any known filing deadlines, response deadlines, or hearing dates
- Contract deadlines or notice requirements
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.
- 4d ago First seen · 216 lines · 57 tokens per session scan A f79d66b6f0f8
intake-summary is a skill published in the GitHub repository protomated/protomated-plugins-official (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 57 tokens to every session and 1,558 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.
Other skills, from other repositories
html-ppt-zhangzara-stencil-tablet
A workplace-safety compliance review for a manufacturing regulator — findings, the evidence chain, and the corrective mandate. Built as a decision-grade policy briefing deck for regulator, plant leadership.
treatment-plans
Format and structurally validate local treatment-plan documentation after clinical decisions have already been supplied and verified by authorized licensed professionals. Use for source traceability, clinician-authored intervention records, goals and checkpoints, shared-decision records, reconciliation handoffs, and…
handbook-updates
Diff a proposed handbook change against the current version, flag ripple effects and state supplement impacts. Use when user says "update the handbook", "add this to the handbook", "handbook change", or has a policy ready for insertion.
software-copyright-materials
Generate guided Chinese software copyright application materials from a real project. Use this skill when the user asks for 软件著作权, 软著申请资料, 软著代码材料, 操作手册, 申请表信息, or wants Word/TXT materials for software copyright registration. The workflow analyzes the imported project, extracts real source code, creates Markdown drafts…
legal-writer
Legal document drafting -- contracts, memos, briefs, complaints, demand letters, opinions, discovery, settlements, ToS, privacy policies. Full pipeline: document structure, per-section writing, Bluebook citation, case law lookup (CourtListener API), regulation lookup (eCFR API), DOCX output, and TDD-style verification…
iflytek-contract-intelligence-review
Use when user asks to review contracts, detect contract risks, or perform compliance checks. 合同智能审核 - 对合同扫描件、图片合同、双语合同进行完整审核。 覆盖 OCR 识别、条款分析、风险检测、合规校对、翻译摘要全流程。 适用于法务审核、采购合同审查、供应链合规检查等场景。 关键词：合同审核、风险检测、条款分析、合规校对、contract review、risk detection。.