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 commands/superdocsapp/superdocs-plugin/superdocs-setupgit clone --depth 1 https://github.com/superdocsapp/superdocs-pluginWhat 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.00037 | $0.01199 |
| Opus 5 | $0.00018 | $0.00600 |
| Sonnet 5 | $0.00007 | $0.00240 |
| Haiku 4.5 | $0.00004 | $0.00120 |
Grade A, and why
superdocs-setup 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 yesterday.
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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SuperDocs setup (Cursor)
This walkthrough is for Cursor. It configures the MCP server via a
SUPERDOCS_API_KEYshell environment variable and thenpx mcp-remotestdio bridge — the flow Cursor uses.On Claude Code, do NOT follow these steps. The Claude Code plugin authenticates differently: install with
claude plugin marketplace add superdocsapp/superdocs-pluginthenclaude plugin install superdocs@superdocs-plugin, and you'll be prompted for yoursk_API key once at install time. It's stored securely in your OS keychain — there's noSUPERDOCS_API_KEYenv var to set and nothing to restart. See the README or docs.
You are helping the user set up SuperDocs in Cursor for the first time. SuperDocs is a structured-document editor — it gives the user 38 MCP tools and 4 workflow prompts for editing, drafting, summarizing, and exporting documents. It exports to .docx, PDF, HTML, Markdown, and plain text, and ingests .pdf, .docx, .txt, .rtf, .md, .html, and .htm. The MCP server connects via a stdio bridge (npx mcp-remote) using an sk_ API key the user holds in the SUPERDOCS_API_KEY environment variable.
Walk the user through this setup interactively. Be helpful, concise, and verify each step before moving on.
Step 1 — Get a free SuperDocs API key
Tell the user:
- Open
https://use.superdocs.app - Sign in (free, no credit card required — Google Sign-In or email/password)
- Click the gear icon → Settings → API Keys tab → Create
- Copy the full
sk_...key (it's shown once; if they lose it they can regenerate)
Free plan includes 500 AI operations per month.
Wait for them to confirm they have the key copied.
Step 2 — Detect the user's shell + set the env var
Detect the shell with: echo $SHELL
Based on the result, append the export line to the right config file:
| Shell | Config file | Command |
|---|---|---|
| zsh (default on macOS) | ~/.zshrc |
echo 'export SUPERDOCS_API_KEY=sk_THEIR_KEY' >> ~/.zshrc && source ~/.zshrc |
| bash | ~/.bashrc (Linux) or ~/.bash_profile (macOS) |
same pattern |
| fish | ~/.config/fish/config.fish |
set -Ux SUPERDOCS_API_KEY sk_THEIR_KEY |
| Windows PowerShell | $PROFILE |
[System.Environment]::SetEnvironmentVariable('SUPERDOCS_API_KEY', 'sk_THEIR_KEY', 'User') |
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.
- yesterday First seen · 87 lines · 37 tokens per session scan A 6d7b38715231
superdocs-setup is a command published in the GitHub repository superdocsapp/superdocs-plugin (1 stars, last pushed 10d ago), licensed MIT. It adds 37 tokens to every session and 1,199 once invoked, about $0.0002 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 commands, from other repositories
open-agreements
Help the user fill a standard legal agreement template and produce a DOCX file.
worktree-start
Set up an isolated worktree so you can work on a branch without affecting other agents or the main checkout.
brand-extract
Extract a Brand Profile from an Office template.
brand-list
List saved Brand Profiles.
tech-spec
Turn a feature/refactor/porting task into a structured spec (ТЗ) under docs/ (local-only, gitignored).
worktree-done
Wrap up work in a worktree: commit, push, open a PR, then cleanly remove the worktree.