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 askgit 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/ask)<a href="https://agentmods.dev/skills/thewolffish/wolffish-app/ask"><img src="https://agentmods.dev/badge/skills/thewolffish/wolffish-app/ask.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.00047 | $0.01606 |
| Opus 5 | $0.00023 | $0.00803 |
| Sonnet 5 | $0.00009 | $0.00321 |
| Haiku 4.5 | $0.00005 | $0.00161 |
Grade A, and why
ask 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 — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ask the user
ask_user is how you put decisions back to the user with concrete choices
instead of guessing or asking in plain prose. It pauses your turn, shows one
interactive card in the chat — each question with its numbered options (a
title and a short description each) and, unless you turn it off, a free-text
box for the user to write their own instructions — and resumes your loop the
moment every question is answered. Whatever they choose comes back to you as
the tool result, so you just continue from there.
One call takes a list of questions. With a single question the card looks like a simple ask; with several, the card shows numbered tabs (1 2 3 …) and moves to the next question as the user answers each one. On Telegram and WhatsApp the questions are posed one message at a time, in order.
When to use it
Reach for ask_user when the next step depends on choices only the user
can make, and you can frame each choice as a few discrete options:
- A real fork in the work: which approach, which file, which format, which of several candidates to act on.
- Disambiguating a vague request before you spend effort down one path.
- Confirming a consequential direction when there's more than a yes/no at stake.
- Quizzing or testing the user — always through this tool. Put every quiz
question in ONE call (usually
allow_other: falseso answers stay gradeable), wait for the answers, then grade and explain in your reply. Never print a quiz as chat text — answers tucked behind<details>blocks are still the wrong shape; the interactive card is the quiz surface.
When NOT to use it
- Don't use it for things you can decide yourself from context, the files, or sensible defaults. Asking when you should just act is friction.
- Don't use it for a plain open-ended question with no natural options — just ask in your normal reply.
- Don't chain separate
ask_usercalls for decisions you already know you need: bundle them as one call with several questions, so the user answers once. Only ask again if a genuinely new decision appears from their answers.
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 · 155 lines · 47 tokens per session scan A 5189ec969aa9
ask is a skill published in the GitHub repository thewolffish/wolffish-app (5 stars, last pushed yesterday), licensed MIT. It adds 47 tokens to every session and 1,606 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 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…