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 supportersimulator/3-surgeons --skill setup-api-keysgit clone --depth 1 https://github.com/supportersimulator/3-surgeonsWrote 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/supportersimulator/3-surgeons/setup-api-keys)<a href="https://agentmods.dev/skills/supportersimulator/3-surgeons/setup-api-keys"><img src="https://agentmods.dev/badge/skills/supportersimulator/3-surgeons/setup-api-keys.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.1 | $0.00021 | $0.00854 |
| Opus 5 | $0.00010 | $0.00427 |
| Sonnet 5 | $0.00004 | $0.00171 |
| Haiku 4.5 | $0.00002 | $0.00085 |
Grade A, and why
setup-api-keys 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 7d 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Setup API Keys
When This Fires
probereturns a surgeon withstatus: "fail"and aremediationfield- Any tool returns an auth error mid-operation
- User asks about API key configuration
Flow
- Read the remediation plan from the probe/tool response
- Present options as a numbered list — only show sources where
available: true - Wait for user choice
- Execute the resolution based on choice
- Persist if requested — offer Keychain storage for future sessions
- Re-run probe to verify the fix worked
Presenting Options
Format the remediation.sources into a clear menu:
🔑 {surgeon} needs {key_name} ({provider}).
{N}. {source.description}
→ `{source.resolve_command}`
{N+1}. Switch to a local model (free, no API key needed)
→ Available: {local_alternatives list}
{N+2}. Paste a key manually
→ I'll store it securely (env var or Keychain)
{N+3}. Skip for now
→ {skip_option}
Only show options where the tool is actually available. Don't show AWS if aws CLI isn't installed.
Executing Each Choice
Shell Profile (method: "shell_profile")
If uses_command: true (e.g., aws secretsmanager call in .zshrc):
# Run the export line to load the key
eval '{resolve_command}'
Then verify with probe.
If uses_command: false (plain value):
The key was likely auto-resolved by diagnose_auth. Just re-probe.
AWS Secrets Manager (method: "aws_secretsmanager")
# Get the key value
KEY_VALUE=$(aws secretsmanager get-secret-value --secret-id {metadata.secret_id} --query SecretString --output text)
export {key_name}="$KEY_VALUE"
Then offer: "Want me to add this to your shell profile for future sessions?"
1Password (method: "1password")
KEY_VALUE=$(op item get "{provider}" --fields credential)
export {key_name}="$KEY_VALUE"
macOS Keychain (method: "keychain")
If metadata.exists: true:
KEY_VALUE=$(security find-generic-password -s {metadata.service} -w)
export {key_name}="$KEY_VALUE"
If metadata.exists: false: Ask user for the key value, then store:
security add-generic-password -s {metadata.service} -a 3surgeons -w "{key_value}"
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.
- 7d ago First seen · 111 lines · 21 tokens per session scan A a364502d81b9
setup-api-keys is a skill published in the GitHub repository supportersimulator/3-surgeons (2 stars, last pushed 3mo ago), licensed MIT. It adds 21 tokens to every session and 854 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 skills, from other repositories
skill-creator
Create, install, or update skills in the workspace. Use when (1) installing a skill from a URL or remote source, (2) creating a new skill from scratch, (3) updating or restructuring existing skills. Always use this skill for any skill installation or creation task.
image-generation
Generate or edit images from text prompts. Use when the user asks to create, draw, design, or edit an image, illustration, photo, icon, poster, or any visual content.
deepcode-self-refer
Answers questions about Deep Code CLI itself — including features, configuration options, slash commands, Skills, MCP integration, permissions, notifications, session persistence, and troubleshooting. Use this when users ask how to configure or use Deep Code, how to set up an MCP server, configure notifications (such…
image-generator
Generate or edit images from text and local files, image URLs, or data URLs through image API. Use when the user asks to create an image, generate from one or more reference images, combine styles or elements across references, or edit a marked region while blending the result into the original scene.
weibo-poster
A writing guide for Weibo, a Chinese microblogging platform similar to a short-post social network. It covers concise posts, longer posts, hashtags, @ mentions, image layouts, and posting-time suggestions.
xiaohongshu-writer
A writing guide for Xiaohongshu, a Chinese social platform for short lifestyle and advice posts. It helps shape titles, post structure, emoji use, cover text, and hashtags.