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 agentmods add skills/psd401/psd-claude-plugins/docusign-managernpx skills add psd401/psd-claude-plugins --skill docusign-managergit clone --depth 1 https://github.com/psd401/psd-claude-pluginsWrote 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/psd401/psd-claude-plugins/docusign-manager)<a href="https://agentmods.dev/skills/psd401/psd-claude-plugins/docusign-manager"><img src="https://agentmods.dev/badge/skills/psd401/psd-claude-plugins/docusign-manager.svg" alt="Measured on agentmods" 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 | $0.00077 | $0.02080 |
| Opus 5 | $0.00039 | $0.01040 |
| Sonnet 5 | $0.00015 | $0.00416 |
| Haiku 4.5 | $0.00008 | $0.00208 |
Grade A, and why
docusign-manager 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 3d 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 — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DocuSign Manager
Read-only export and archive skill for migrating from DocuSign to Documenso + n8n.
Configuration
- API: DocuSign eSignature REST API v2.1
- Auth: JWT Grant (RSA-signed assertion → access token, 1-hour expiry, auto-refresh)
- Base URI: Auto-discovered via
/oauth/userinfo(varies by account: na1, na2, na3, eu, au) - Rate Limits: 3,000 calls/hour, 500 per 30 seconds
- Scripts:
plugins/psd-productivity/skills/docusign-manager/scripts/
All scripts use bun and read credentials from secrets.js (env vars → Geoffrey .env).
Required Secrets
| Secret | Description |
|---|---|
DOCUSIGN_INTEGRATION_KEY |
Integration key (client ID) from DocuSign admin |
DOCUSIGN_USER_ID |
User ID (GUID) of the API user |
DOCUSIGN_ACCOUNT_ID |
Account ID (GUID) |
DOCUSIGN_RSA_KEY_PATH |
Path to RSA private key file (PEM format) |
DOCUSIGN_ENVIRONMENT |
production or demo (default: production) |
See references/docusign-jwt-setup.md for credential setup instructions.
Command Reference
Account
| Command | Script | Description |
|---|---|---|
/docusign status |
bun health_check.js |
Test JWT auth, show account info |
Templates
| Command | Script | Description |
|---|---|---|
/docusign list-templates |
bun list_templates.js |
List all templates |
/docusign list-templates '{"search":"permission"}' |
bun list_templates.js '{"search":"permission"}' |
Search templates |
/docusign get-template <id> |
bun get_template.js <id> |
Full template with fields/recipients |
/docusign export-template <id> |
bun export_template.js <id> |
Export as Documenso-compatible JSON |
/docusign export-templates |
bun export_all_templates.js |
Export ALL templates with manifest |
/docusign download-template <id> |
bun download_template.js <id> |
Download template PDF(s) + Documenso field mapping |
PowerForms
| Command | Script | Description |
|---|---|---|
/docusign list-powerforms |
bun list_powerforms.js |
List all PowerForms (self-service links) |
/docusign get-powerform <id> |
bun get_powerform.js <id> |
PowerForm details with migration hints |
What ships with it
18 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.
- references/docusign-api-reference.md 4.8 KB
- references/docusign-jwt-setup.md 3.5 KB
- references/docusign-migration-guide.md 9.4 KB
- scripts/bulk_download.js 8.8 KB runs code
- scripts/docusign_client.js 5.3 KB runs code
- scripts/download_audit.js 2.2 KB runs code
- scripts/download_document.js 2.0 KB runs code
- scripts/download_template.js 5.2 KB runs code
- scripts/export_account.js 3.9 KB runs code
- scripts/export_all_templates.js 2.9 KB runs code
- scripts/export_template.js 5.3 KB runs code
- scripts/get_envelope.js 1.7 KB runs code
- scripts/get_powerform.js 2.1 KB runs code
- scripts/get_template.js 2.3 KB runs code
- scripts/health_check.js 1.5 KB runs code
- scripts/list_envelopes.js 1.9 KB runs code
- scripts/list_powerforms.js 948 B runs code
- scripts/list_templates.js 1.3 KB runs code
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.
- 3d ago First seen · 175 lines · 77 tokens per session scan A c9c5d3727a86
docusign-manager is a skill published in the GitHub repository psd401/psd-claude-plugins (2 stars, last pushed 3d ago), licensed MIT. It adds 77 tokens to every session and 2,080 once invoked, about $0.0004 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…