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 IceWhaleTech/ZimaOS-Blue --skill askgit clone --depth 1 https://github.com/IceWhaleTech/ZimaOS-BlueWrote 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/icewhaletech/zimaos-blue/ask)<a href="https://agentmods.dev/skills/icewhaletech/zimaos-blue/ask"><img src="https://agentmods.dev/badge/skills/icewhaletech/zimaos-blue/ask/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/icewhaletech/zimaos-blue/ask"><img src="https://agentmods.dev/badge/skills/icewhaletech/zimaos-blue/ask.svg" alt="Reviewed on agentmods" width="80" 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.00063 | $0.00965 |
| Opus 5.5 | $0.00025 | $0.00386 |
| Sonnet 5.5 | $0.00013 | $0.00193 |
| Haiku 4.5 | $0.00006 | $0.00097 |
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 1mo 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ask Skill
Setup
No external dependencies required. This skill uses the built-in ask capability.
Task Routing
Based on user intent, choose the corresponding ask action:
| User Intent | Action |
|---|---|
| User explicitly asks for question flow (e.g. "ask me questions", "用 ask 技能问我问题") | Run one blue ask call immediately (prefer questions='[...]' for multi-question flows) |
| Requirement is ambiguous and you must clarify before choosing a strategy | Run blue ask to collect missing constraints/preferences |
| MCP internal Plan mode requires a confirmation/clarification gate | Run blue ask before continuing plan execution |
| Multi-step questionnaire/interview (Q1/Q2/Q3) | Use a single blue ask questions='[...]' call whenever possible |
| Multiple valid implementation approaches | Run blue ask to get explicit user choice before execution |
Command Usage
Preferred Single-Question Format
blue ask q="Choose a deploy strategy" a='["Canary","Blue-Green"]'
Multi-Question Format (Recommended)
blue ask questions='[
{"question":"How should I address you?","type":"radio","options":["Alex","A."]},
{"question":"Preferred language?","type":"radio","options":["zh","en"]},
{"question":"请假时长？","type":"text"},
{"question":"邮件收件人是？","type":"radio","options":["直属上级","HR","两者都抄送"]}
]'
Do not continue staged questionnaires via plain assistant text (e.g. "continnue second question...").
Each follow-up must be another blue ask call.
Input Format
| Field | Requirement | Notes |
|---|---|---|
questions |
Preferred | Array of question objects |
type |
Required per item | radio, checkbox, or text |
options |
Conditional | Required for radio/checkbox; omit for text |
q + a |
Shorthand | Single-question shorthand |
mq + a |
Shorthand | Multi-choice shorthand |
Example payload:
[
{
"question": "Which environment should we use?",
"type": "radio",
"options": ["Staging", "Production"]
},
{
"question": "How long is the leave?",
"type": "text"
}
]
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.
- 1mo ago First seen · 118 lines · 63 tokens per session scan A 46aa4473b7bc
ask is a skill published in the GitHub repository IceWhaleTech/ZimaOS-Blue (28 stars, last pushed 2d ago), licensed MIT. It adds 63 tokens to every session and 965 once invoked, about $0.0003 per session on Opus 5.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-30.
Other skills, from other repositories
obsidian-cli
Interact with Obsidian vaults using the Obsidian CLI to read, create, search, and manage notes, tasks, properties, and more. Also supports plugin and theme development with commands to reload plugins, run JavaScript, capture errors, take screenshots, and inspect the DOM. Use when the user asks to interact with their…
intent-recognition
Load before you build any new kept workflow or Agent. It decides which one to build, or what to ask first. Classifies automation requests using two decisions: anchor (which primitive owns the top-level control flow — workflow-anchored, agent-anchored, needs-clarification, or out-of-scope) and embedsother (whether the…
debugging-executions
Debug failed or wrong-output workflow executions using executions tools. Load when the user reports execution failures, unexpected node output, empty parameter values after a successful run, or a node showing a red or failed expression error. Also load when a live run you started for the user fails with an error from…
planned-task-runtime
Handles system follow-up turns: planned-task-follow-up (synthesize, replan, build-workflow, checkpoint), background-task-completed, running-tasks context, and workflowbuildercreatetasks silence rules. Load whenever any of these tags appear or after calling workflowbuildercreatetasks.
suggest-automations
Offer the three most common automations for a user as a single-choice card, from your own knowledge of their team and their apps, then build the one they choose once they confirm, or offer more. The system preloads it on onboarding threads, where the opening card already asked the user about themselves. Use it on…
task_automation
Design effective automated workflows using scheduled tasks, prompt chaining, and delivery channels.