Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/sun2443/designer-skillsnpx agentmods add skills/sun2443/designer-skills/signature-requestWrote 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/sun2443/designer-skills/signature-request)<a href="https://agentmods.dev/skills/sun2443/designer-skills/signature-request"><img src="https://agentmods.dev/badge/skills/sun2443/designer-skills/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/sun2443/designer-skills/signature-request"><img src="https://agentmods.dev/badge/skills/sun2443/designer-skills/signature-request.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.00066 | $0.00794 |
| Opus 5.5 | $0.00026 | $0.00318 |
| Sonnet 5.5 | $0.00013 | $0.00159 |
| Haiku 4.5 | $0.00007 | $0.00079 |
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 13d 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.
This is a copy
100% identical to signature-request — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/signature-request -- E-Signature Routing
If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.
Prepare a document for electronic signature — verify completeness, set signing order, and route for execution.
Important: This command assists with legal workflows but does not provide legal advice. Verify documents are in final form before sending for signature.
Usage
/signature-request $ARGUMENTS
Prepare for signature: @$1
Workflow
Step 1: Accept the Document
Accept the document in any format:
- File upload: PDF, DOCX
- URL: Link to a document in ~~cloud storage or ~~CLM
- Reference: "The Acme Corp MSA we finalized yesterday"
Step 2: Pre-Signature Checklist
Before routing for signature, verify:
## Pre-Signature Checklist
- [ ] Document is in final, agreed form (no open redlines)
- [ ] All exhibits and schedules are attached
- [ ] Correct legal entity names on signature blocks
- [ ] Dates are correct or left blank for execution date
- [ ] Signature blocks match the authorized signers
- [ ] Any required internal approvals have been obtained
- [ ] Document has been reviewed by appropriate counsel
Step 3: Configure Signing
Gather signing details:
- Signers: Who needs to sign? (names, emails, titles)
- Signing order: Sequential or parallel?
- Internal approval: Does anyone need to approve before the counterparty signs?
- CC recipients: Who should receive a copy of the executed document?
Step 4: Route for Signature
If ~~e-signature is connected:
- Create the signature envelope/request
- Set signing fields and order
- Add any required initials or date fields
- Send for signature
If not connected:
- Generate a signing instruction document
- Provide the document formatted for wet signature or manual e-sign
- List all signers with contact information
Output
## Signature Request: [Document Title]
### Document Details
- **Type**: [MSA / NDA / SOW / Amendment / etc.]
- **Parties**: [Party A] and [Party B]
- **Pages**: [X]
### Pre-Signature Check: [PASS / ISSUES FOUND]
[List any issues that need attention before sending]
### Signing Configuration
| Order | Signer | Email | Role |
|-------|--------|-------|------|
| 1 | [Name] | [email] | [Party A Authorized Signatory] |
| 2 | [Name] | [email] | [Party B Authorized Signatory] |
### CC Recipients
- [Name] — [email]
### Status
[Sent for signature / Ready to send / Issues to resolve first]
### Next Steps
- [What to expect after sending]
- [Expected turnaround time]
- [Follow-up if not signed within X days]
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.
- 13d ago First seen · 105 lines · 66 tokens per session scan A bf702fbe7d21
signature-request is a skill published in the GitHub repository sun2443/designer-skills (0 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 66 tokens to every session and 794 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to signature-request, differing in 0 lines, and is treated as a copy.
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
Formats and structurally validates 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…
legal-hold
Issue, refresh, release, or report on legal holds — drafts the hold notice as .docx, updates legalhold fields in log.yaml, and calendars the next refresh. Use when the user says "issue a hold", "refresh hold", "release hold", or asks for a portfolio-wide hold status report.
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
A workflow for creating Chinese application materials for software copyright registration from a real software project.
employment-contract-templates
Create employment contracts, offer letters, and HR policy documents following legal best practices. Use when drafting employment agreements, creating HR policies, or standardizing employment documentation.