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 zgbrenner/agentcounsel --skill signature-routing-checklistgit clone --depth 1 https://github.com/zgbrenner/agentcounselWrote 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/zgbrenner/agentcounsel/signature-routing-checklist)<a href="https://agentmods.dev/skills/zgbrenner/agentcounsel/signature-routing-checklist"><img src="https://agentmods.dev/badge/skills/zgbrenner/agentcounsel/signature-routing-checklist/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/zgbrenner/agentcounsel/signature-routing-checklist"><img src="https://agentmods.dev/badge/skills/zgbrenner/agentcounsel/signature-routing-checklist.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.00051 | $0.01916 |
| Opus 5 | $0.00026 | $0.00958 |
| Sonnet 5 | $0.00010 | $0.00383 |
| Haiku 4.5 | $0.00005 | $0.00192 |
Grade A, and why
Signature Routing Checklist 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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Signature Routing Checklist
Purpose
Produce a draft pre-signature readiness review and signing-routing plan for a document that is believed to be in final form. The skill runs a completeness checklist, identifies the signers and the signing order, checks entity names for consistency, flags anything that must be resolved before the document is sent for execution, and assembles a routing plan.
This skill provides workflow discipline and structure. It produces draft work product for attorney review. This is not legal advice. A passing checklist is not authorization to execute; the skill never sends, transmits, or executes a document.
Use When
- A user says "is this ready to sign?", "set up signing for this contract," or "prepare this for signature."
- A document is believed final and needs a pre-execution completeness check and a routing plan.
- The user is verifying entity names, exhibits, and signature blocks before a document goes out for signature.
Required Inputs
- The document to be signed — uploaded, pasted, or precisely described.
- The intended signers — names, titles, the entity each signer binds, and whether each signer is understood to be internally authorized.
- Required internal approvals — which approvals the document needs and whether they have been obtained.
- Signing preferences — sequential or parallel signing order, and any CC recipients for the executed copy.
If the document is not provided, stop and request it. If signer information is incomplete, ask before producing the routing plan.
Do Not Use When
- The document is not in final form or has open redlines — resolve those first (use
redline-summaryorcontract-risk-review). - The user wants the agent to actually send the document for e-signature — this skill produces a routing plan and a checklist, not an execution action.
- Signing authority is genuinely in question — whether a person or entity can bind is a corporate-authority question; route it to
written-consentor to counsel. - The task is to review the document's terms for risk — use
contract-risk-reviewor the relevant contract-review skill.
What ships with it
1 file 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.
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 · 137 lines · 51 tokens per session scan A 44e4e2601bcb
Signature Routing Checklist is a skill published in the GitHub repository zgbrenner/agentcounsel (19 stars, last pushed 1mo ago), licensed MIT. It adds 51 tokens to every session and 1,916 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-09-03.
Other skills, from other repositories
performance-management
Runs performance systems that change behavior — expectations, feedback, review cycles, calibration, and handling underperformance. Use this to design or fix a review process, run calibration, write or coach on feedback, address sustained underperformance, or work out why reviews consume weeks and change nothing.
vendor-evaluation
Evaluate, select, and contract with vendors and SaaS tools. Use this skill when comparing alternatives, running an RFP, scoring vendors against criteria, negotiating contracts, planning a switch, or assessing a vendor's risk. Triggers on vendor evaluation, RFP, vendor selection, build vs buy, SaaS evaluation, vendor…
compliance-tracker
Track regulatory compliance for construction projects. Monitor permits, certifications, inspections, and regulatory requirements with automated alerts and reporting.
safety-inspection-checklist
Digital safety inspection checklists for construction sites. Generate, conduct, and track safety inspections with automated reporting and compliance monitoring.
delay-analysis
Analyze construction schedule delays for claims and recovery. Perform time impact analysis, identify delay causes, calculate damages, and document for disputes.
change-order-manager
Manage construction change orders from request to approval. Track costs, schedule impacts, and maintain audit trail for dispute prevention.