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 alebgl77/claude-inc --skill signature-requestgit clone --depth 1 https://github.com/alebgl77/claude-incWrote 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/alebgl77/claude-inc/signature-request)<a href="https://agentmods.dev/skills/alebgl77/claude-inc/signature-request"><img src="https://agentmods.dev/badge/skills/alebgl77/claude-inc/signature-request/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/alebgl77/claude-inc/signature-request"><img src="https://agentmods.dev/badge/skills/alebgl77/claude-inc/signature-request.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.00097 | $0.01183 |
| Opus 5 | $0.00048 | $0.00592 |
| Sonnet 5 | $0.00019 | $0.00237 |
| Haiku 4.5 | $0.00010 | $0.00118 |
Grade A, and why
signature-request 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 9d 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Signature Request — Signature Wrangler
"Route for signature"
The last gate before ink: nothing routes until the document proves it is actually ready to sign. Works on the final document plus deal facts from the user.
When to use
- "Contract's final — get it signed" — execution time
- "Set up the envelope for the MSA and SOW" — multi-document routing
- "Who signs first, us or them?" — signing-order call
- "It's signed — now what?" — filing and obligations follow-through
- Terms still moving? Back to
review-contract— nothing unfinalized enters this gate
Workflow
- Confirm the document is final: no tracked changes, no open comments, version confirmed by the deal owner. Not final → stop and say exactly what is still open.
- Run the pre-signature checklist: legal entity names exact (registry names, not brand names); signatory authority on both sides (name, title, basis); every exhibit and schedule attached and cross-referenced correctly; every blank filled — dates, amounts, addresses, notice emails; dates consistent (effective vs. signature vs. term start); counterparty details verified (entity number, registered address, signer identity).
- Fix or flag: mechanical defects (an empty notice address) get filled from known facts or asked; anything substantive reopens review — the gate never "signs around" a defect.
- Set the signing order: sequential when one signature depends on another (counterparty signs first so we execute last and control the effective date); parallel when signatures are independent and speed wins. Always state the why.
- Write envelope instructions portable to any e-sign tool: recipients (name, email, role, order), fields per signer (signature, date, title), CC-on-completion list, reminder cadence, expiration, and the message subject and body.
- Plan post-signature filing: where the executed copy lives, who receives copies, and the file-naming convention.
- Create obligations-calendar entries: renewal and opt-out deadlines, payment milestones, deliverables, notice windows — each with a date, an owner, and an alert lead time.
- Deliver the packet. Nothing is actually sent without explicit human confirmation.
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.
- 9d ago First seen · 83 lines · 97 tokens per session scan A 3cf3bf18fa7d
signature-request is a skill published in the GitHub repository alebgl77/claude-inc (14 stars, last pushed 6d ago), licensed MIT. It adds 97 tokens to every session and 1,183 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
google-workspace
Gmail, Calendar, Drive, Docs, Sheets via gws CLI or Python.
box
Box manages cloud files, sharing, search, and metadata.
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…
ima-skill
A unified IMA skill for managing personal notes and knowledge bases through the platform's APIs.
redact-pii
Redact personal data from a document through the connected Superlinked MCP edge before working with the content. Use when the user asks to redact, anonymize, scrub, de-identify, or remove PII/sensitive data from a document.
notes
A note-management skill for searching, reading, creating, and adding content to personal notes in IMA, a note and knowledge platform.