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 thewolffish/wolffish-app --skill secretsgit clone --depth 1 https://github.com/thewolffish/wolffish-appWrote 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/thewolffish/wolffish-app/secrets)<a href="https://agentmods.dev/skills/thewolffish/wolffish-app/secrets"><img src="https://agentmods.dev/badge/skills/thewolffish/wolffish-app/secrets.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.00029 | $0.00939 |
| Opus 5 | $0.00015 | $0.00469 |
| Sonnet 5 | $0.00006 | $0.00188 |
| Haiku 4.5 | $0.00003 | $0.00094 |
Grade A, and why
secrets 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 8d 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Secrets & variables
Save and look up the user's named values — API keys, tokens, passwords, base
URLs — in the same store the Settings > Variables panel uses
(config.json → variables). A value saved here shows up in the Settings UI
and is made available to you in your <variables> context block, so you can use
it directly in later tool calls.
When to use
- The user pastes an API key/token/password and asks you to save or remember it
→
add_secret(sensitive by default). - The user gives you a reusable non-secret value (a base URL, an account id) and
wants it kept →
add_secretwithsensitive: false. - You're about to ask the user for a key/value — first
list_secretsto check whether it already exists. - The user asks "what keys/secrets do I have saved?" →
list_secrets.
Tools
add_secret— save (or update) a secret/variable. Same effect as adding it in the Variables UI. Replaces the value if the name already exists.list_secrets— list saved secrets/variables with their real values so you can use them directly. Each is tagged sensitive or not.
Rules
- These tools exist so you have the values — don't ask the user for something
you already have.
list_secretsreturns the real values to you; thesensitivetag is just a hint about which ones not to paste into your chat reply to the user. There is no masking that hides a value from you. - Only save when the user asks. Don't squirrel away values speculatively.
- Don't paste a sensitive value into your user-facing reply — refer to it by
name ("using your
OPENAI_API_KEY"). Using it in a tool call is fine. - Default to sensitive. A key, token, or password is sensitive. Use
sensitive: falseonly for plainly non-secret config (a base URL, a region). - Check before asking. If a task needs a value,
list_secrets(or your<variables>block) may already have it — don't ask the user to re-enter it. - Updating replaces the old value. If the name already exists,
add_secretoverwrites it — confirm you have the right name so you don't clobber a real key. - This is the right tool for secrets — do not hand-edit
config.jsonwith the filesystem tools to add a variable.
What ships with it
1 file 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.
- 8d ago First seen · 91 lines · 29 tokens per session scan A 91d5e5e9dc16
secrets is a skill published in the GitHub repository thewolffish/wolffish-app (5 stars, last pushed yesterday), licensed MIT. It adds 29 tokens to every session and 939 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
agent-computer-use
REQUIRED for any task that involves operating a desktop application — opening apps, clicking buttons, typing into fields, pressing keys, scrolling, dragging, reading what's on screen, moving or resizing windows, or verifying state after an action. Always use the agent-cu CLI commands (open, snapshot, click, type, key…
claude-api
Build, debug, and optimize Claude API / Anthropic SDK apps. Apps built with this skill should include prompt caching. Also handles migrating existing Claude API code between Claude model versions (4.5 → 4.6, 4.6 → 4.7, retired-model replacements). TRIGGER when: code imports anthropic/@anthropic-ai/sdk; user asks for…
create-skill
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
figma-create-design-system-rules
Generates custom design system rules for the user's codebase. Use when user says "create design system rules", "generate rules for my project", "set up design rules", "customize design system guidelines", or wants to establish project-specific conventions for Figma-to-code workflows. Requires Figma MCP server…
figma-generate-design
Use this skill alongside figma-use when the task involves translating an application page, view, or multi-section layout into Figma. Triggers: 'write to Figma', 'create in Figma from code', 'push page to Figma', 'take this app/page and build it in Figma', 'create a screen', 'build a landing page in Figma', 'update the…
figma-generate-library
Build or update a professional-grade design system in Figma from a codebase. Use when the user wants to create variables/tokens, build component libraries, set up theming (light/dark modes), document foundations, or reconcile gaps between code and Figma. This skill teaches WHAT to build and in WHAT ORDER — it…