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/tmoody1973/pasteup/setupgit clone --depth 1 https://github.com/tmoody1973/pasteupWhat 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.00020 | $0.00483 |
| Opus 5 | $0.00010 | $0.00242 |
| Sonnet 5 | $0.00004 | $0.00097 |
| Haiku 4.5 | $0.00002 | $0.00048 |
Grade A, and why
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.
What it actually says
Run guided setup for the pasteup plugin. The user may have passed their Gemini API key as an argument: $ARGUMENTS
Follow these steps in order:
-
Status check. Run:
python "${CLAUDE_PLUGIN_ROOT}/scripts/setup.py" --checkShow the user a one-line summary of what is present and what is missing.
-
Install Python packages if any are missing:
python "${CLAUDE_PLUGIN_ROOT}/scripts/setup.py" --deps -
ffmpeg. If missing, install it for their OS (brew, apt, or winget as reported by the check). If installation needs elevated permissions the user has not granted, give them the exact one-line command to run themselves.
-
API key.
- If a key was passed in $ARGUMENTS, write it immediately:
This writes it to apython "${CLAUDE_PLUGIN_ROOT}/scripts/setup.py" --write-key THE_KEY.envfile in the current project with owner-only permissions and adds.envto.gitignoreautomatically. - If no key was passed and none was found by the check, tell the user: get a free key at https://aistudio.google.com/apikey (sign in, click "Create API key", copy it), then either paste it here in chat or run
/pasteup:setup THEIR_KEY. When they paste it, write it with the same--write-keycommand. Mention once, briefly, that pasting a key in chat stores it in this conversation's history, and that setting it in a.envfile themselves is the more private option; do not belabor the point. - Never print the key back in full. Refer to it as "your key ending in ...XXXX".
- If a key was passed in $ARGUMENTS, write it immediately:
-
Verify. Run the check again and confirm everything reports OK. Then tell the user they are ready and show two example first prompts:
- Paste a reference image and say "analyze this"
- Or: "Make a 10s vertical collage stop-motion ad for [their thing]"
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 · 35 lines · 20 tokens per session scan A bcfb3a579172
setup is a command published in the GitHub repository tmoody1973/pasteup (2 stars, last pushed 1mo ago), licensed MIT. It adds 20 tokens to every session and 483 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.
Other commands, from other repositories
spec-research
需求 → 约束集(并行探索 + OPSX 提案).
spec-design
Create comprehensive technical design for a specification.
release
Ship a stable cmux release built by CI: bump version, update changelog, open a PR, merge, tag, then GitHub Actions builds, signs, and publishes.
plan
Create a structured task-by-task implementation plan for a feature and write it to docs/superpowers/plans/.
sdd-setup
Onboarding wizard — DocLanguage, Memory Bank, architecture snapshot, working agreements (quality gate, TDD working mode).
notebook-query
Query the notebook knowledge base (SQLite) built by /agy:notebook — precise, grounded, cited. Ask in natural language ("sum the amounts by category", "which docs mention 'Acme Corp'", "build a project timeline") or pass raw SQL. Read-only. Use this when you need exact aggregates/lookups across a document corpus…