track-signing-status

track-signing-status is a skill for Codex from ZapSign/api-mcp. It costs 28 tokens per session (396 once invoked), scanned A, original, MIT.

A workflow for checking the current signing state of a ZapSign document, an electronic document-signing service. It reports the document status and each signer's status from the latest service response.

In plain words
What is it for?
Use it with a document token or search filters to find a document, inspect its authoritative details, summarize signer progress, and note any deadline.
Why use it?
It prevents guessing from messages or notifications and helps identify who has signed, refused, or still needs to sign.

Skill for Codex

Written for Codex: agents/openai.yaml present.

Good fit Use it with a document token or search filters to find a…

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/zapsign/api-mcp/track-signing-status
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 ZapSign/api-mcp --skill track-signing-status
Clone the repo
git clone --depth 1 https://github.com/ZapSign/api-mcp

Made for: 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.

agentmods badge for track-signing-status

README.md
[![agentmods](https://agentmods.dev/badge/skills/zapsign/api-mcp/track-signing-status.svg)](https://agentmods.dev/skills/zapsign/api-mcp/track-signing-status)
Your own site
<a href="https://agentmods.dev/skills/zapsign/api-mcp/track-signing-status"><img src="https://agentmods.dev/badge/skills/zapsign/api-mcp/track-signing-status.svg" alt="Measured on agentmods" height="20"></a>
Per session 28 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 396 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00028 $0.00396
Opus 5 $0.00014 $0.00198
Sonnet 5 $0.00006 $0.00079
Haiku 4.5 $0.00003 $0.00040

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

Security

Grade A, and why

track-signing-status 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 6d 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.

docs/submission/openai-skills/zapsign-mcp-plugin/skills/track-signing-status/SKILL.md · 30 lines

What it actually says

Track signing status

Use this skill when the user asks whether a ZapSign document is pending, signed, or refused, or wants a signer-by-signer status summary.

Workflow

  1. If the user provides a document token, call get_document with it.
  2. If no token is provided, call list_documents with the user's stated filters. Use status: pending for requests specifically about outstanding signatures. Paginate only when needed to locate the document.
  3. If multiple documents plausibly match, show their names, statuses, creation dates, and tokens, then ask the user which one to inspect.
  4. Call get_document for the selected token to retrieve the authoritative current document and signer details.
  5. Report:
    • Document name and overall status.
    • Each signer's name and current signing status.
    • Who is still pending, refused, or complete.
    • Any signing deadline present in the response.
  6. When useful, suggest a supported next step such as updating a signer or retrieving the current signing link, but do not perform a write action unless the user asks.

Rules

  • Do not infer that a signer completed signing from message history or notification delivery. Use the latest tool response.
  • Do not expose signer email addresses, phone numbers, document tokens, or signing links unless they are needed for the user's request.
  • File URLs in get_document responses expire after 60 minutes. Mention this when returning original_file or signed_file.
  • If the token is invalid or not found, ask the user to verify it or search with list_documents; do not fabricate a result.
  • This workflow is read-only. Never call update, delete, create, or notification tools unless the user separately requests that action.
Files

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.

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.

  1. 6d ago First seen · 30 lines · 28 tokens per session scan A ebb5d3b0be25

Subscribe to this mod's changes

track-signing-status is a skill published in the GitHub repository ZapSign/api-mcp (1 stars, last pushed 3d ago), licensed MIT. It adds 28 tokens to every session and 396 once invoked, about $0.0001 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.

Related

Other skills, from other repositories

specification-writing

A workflow for writing complete patent specifications from patent claims and an invention disclosure. It adapts the document to a chosen jurisdiction, such as the US, Europe, or China.

wanshuiyin/Auto-claude-code-research-in-sleep · 49 tokens

regulatory-research-fallback

Fallback workflow for regulatory research when web extraction tools fail on government PDFs.

HKUDS/OpenSpace · 20 tokens

x-scorecard

OpenSSF Scorecard for assessing open source project security. Check security best practices and compliance. Dependency: This is an x-cmd module. Install x-cmd first (see x-cmd skill for installation options). see x-cmd skill for installation.

x-cmd/x-cmd · 57 tokens

memstack-business-gdpr

Use this skill when the user says 'GDPR', 'data protection', 'privacy compliance', 'DPA', 'DSAR', 'data subject request', 'cookie consent', 'privacy audit', 'CCPA', or asks 'do I need GDPR for this repo'. Scans the repository to detect what personal data is collected, classifies sensitivity, determines whether GDPR…

cwinvestments/memstack · 121 tokens

gesellschaftsrechtliche-satzungen-agb

Für Gesellschaftsrechtliche Satzungen AGB Abgrenzung: ordnet Norm, Beweislast und Gegenargument; Ergebnis: Prüfprodukt mit Risiko und nächstem Schritt. Fachgebiet: AGB-Recht-Prüfer. Route: gesellschaftsrechtliche-satzungen-agb.

Klotzkette/claude-fuer-deutsches-recht · 69 tokens

nda-review

Use when the user uploads or pastes a non-disclosure agreement and asks for review, redline, risk assessment, or a recommendation on whether to sign. Identifies missing standard protections, one-sided or unusual provisions, and operational issues; produces a structured report with severity ratings and citations to…

LegalQuants/lq-ai · 79 tokens