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 docusealco/docuseal-agent-skills --skill docuseal-cligit clone --depth 1 https://github.com/docusealco/docuseal-agent-skillsWrote 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/docusealco/docuseal-agent-skills/docuseal-cli)<a href="https://agentmods.dev/skills/docusealco/docuseal-agent-skills/docuseal-cli"><img src="https://agentmods.dev/badge/skills/docusealco/docuseal-agent-skills/docuseal-cli/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/docusealco/docuseal-agent-skills/docuseal-cli"><img src="https://agentmods.dev/badge/skills/docusealco/docuseal-agent-skills/docuseal-cli.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 40 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 44 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- medium Rogue Agent · line 5 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00081 | $0.01459 |
| Opus 5.5 | $0.00032 | $0.00584 |
| Sonnet 5.5 | $0.00016 | $0.00292 |
| Haiku 4.5 | $0.00008 | $0.00146 |
Grade A, and why
docuseal-cli 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 2mo 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Protocol
Rules for agents:
- Supply ALL required flags — the CLI will not prompt for missing parameters.
- Output is always JSON.
- Use
-d key=value(bracket notation) or-d '{"..": ".."}'(JSON) for body and array parameters.
Authentication
Set environment variables:
DOCUSEAL_API_KEY— API key (required). Get yours at https://console.docuseal.com/apiDOCUSEAL_SERVER—global(default),europe, or full URL for self-hosted (e.g.https://docuseal.yourdomain.com)
Available Commands
| Command Group | What it does |
|---|---|
templates |
list, retrieve, update, archive, create-pdf, create-docx, create-html, clone, merge, update-documents |
submissions |
list, retrieve, update, archive, create, send-emails, create-pdf, create-docx, create-html, documents |
submitters |
list, retrieve, update |
Read the matching reference file for detailed flags and examples.
Common Mistakes
| # | Mistake | Fix |
|---|---|---|
| 1 | Forgetting -d template_id=<id> on submissions create |
--template-id is a flag; submitters and other body params go via -d |
| 2 | Passing a plain file path as a URL | --file accepts a local path; for remote files use -d "documents[0][file]=https://..." |
| 3 | Expecting array params as comma-separated | Arrays use bracket notation: -d "template_ids[]=1" -d "template_ids[]=2" |
| 4 | Using templates create-pdf without a Pro plan |
Commands marked (Pro) require a DocuSeal Pro subscription |
| 5 | Sending to multiple recipients with submissions create |
Use submissions send-emails --emails [email protected],[email protected] for bulk; submissions create is per-submitter |
Security
The CLI accepts user-provided file paths, remote URLs (documents[0][file]=https://...), and HTML content as template input. This is by design — all content originates from the authenticated user and is sent directly to the DocuSeal API over HTTPS. The CLI does not fetch, render, or execute remote content locally; it passes references to the server for processing. No user input is interpolated into shell commands.
What ships with it
6 files 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.
- 2mo ago Changed · +17 lines 8047bbe4793a
- 2mo ago First seen · 113 lines · 81 tokens per session scan A cd3c89a5271a
docuseal-cli is a skill published in the GitHub repository docusealco/docuseal-agent-skills (9 stars, last pushed 4d ago), licensed MIT. It adds 81 tokens to every session and 1,459 once invoked, about $0.0003 per session on Opus 5.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
data-policy
Use when building internal data-governance machinery: a retention schedule (period, lawful basis, expiry action, system where deletion runs), an Art. 6 lawful-basis register, an Art. 30 ROPA, or a consent capture/withdrawal model. NOT the public privacy notice or DSAR handling (that is gdpr-privacy), NOT SOC 2 posture…
analiz-html-report
Use when you write or revise the analiz deliverable - the ONE self-contained HTML report (spec and plan as sections) a human reviews passage by passage.
jetson-link-docs
Bind pre-downloaded Jetson reference docs (developer guide, design guide, pinmux, schematics) into the active profile documents block. Use after staging docs on disk; not for downloading.
requirements-document
Use when a product decision or feature needs a written record - what to capture in a task document (PRD, decision record) and where to attach it, since TaskTrooper has no epic.
generate-fillable-contract-html
A generator for Chinese HTML templates with fill-in fields for contracts, quotations, and authorization letters. The fields are marked so a later HTML-to-Word conversion can identify and fill them.
ask-household-record
Answer questions about the connected person's own trusts, LLCs, properties, and policies from their X1 record, with the document and page behind each answer, and build that record one document at a time. Use when someone asks what their trust, operating agreement, K-1, or policy says, who owns what, which entity…