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 skills/jeffy-w/agentskills/asknpx skills add jeffy-w/AgentSkills --skill askgit clone --depth 1 https://github.com/jeffy-w/AgentSkillsWrote 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/jeffy-w/agentskills/ask)<a href="https://agentmods.dev/skills/jeffy-w/agentskills/ask"><img src="https://agentmods.dev/badge/skills/jeffy-w/agentskills/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 | $0.00041 | $0.00570 |
| Opus 5 | $0.00020 | $0.00285 |
| Sonnet 5 | $0.00008 | $0.00114 |
| Haiku 4.5 | $0.00004 | $0.00057 |
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 3d 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.
What it actually says
Ask
使用本 skill 时，直接调用本机安装的 claude、gemini 或 codex CLI，并把结果保存为可复用 artifact。
When to use
- 用户明确说要使用本地顾问 CLI 能力。
- 需要本地 Claude / Gemini 做一轮 review、二次确认、brainstorming。
- 需要保留原始任务、最终 prompt、原始输出和 action items。
Script
主脚本：
ask/scripts/ask.js
Direct usage
node ask/scripts/ask.js claude "请 review 当前改动"
node ask/scripts/ask.js gemini --prompt "分析这个 bug 根因"
node ask/scripts/ask.js codex --prompt "给我第二视角分析当前实现"
node ask/scripts/ask.js claude --agent-prompt code-reviewer "请检查这次重构风险"
Behavior
- 校验 provider 只允许
claude、gemini或codex。 - 可选读取
prompts/<role>.md，将角色 prompt 与用户 prompt 拼接。 - 直接调用本地 CLI：
claude -p -- "<prompt>"gemini -p "<prompt>"codex exec --skip-git-repo-check --sandbox read-only "<prompt>"
- 将输出写入：
.artifacts/ask/<provider>-<slug>-<timestamp>.md
artifact 至少包含：
- Original user task
- Final prompt
- Raw CLI output
- Concise summary
- Action items
Role prompts
角色 prompt 目录：
ask/prompts/
如果需要新增角色，直接新增同名 .md 文件，例如：
code-reviewer.mdarchitect.mddebugger.md
Guardrails
- 本 skill 只走本地 CLI，不要静默切换到 MCP 或远端 provider。
- 如果本地 binary 缺失，应直接报错并提示用户安装。
codexprovider 默认走非交互codex exec，并使用只读沙箱，适合作为问答 / review / 分析顾问，不适合直接让它改代码。- 回答时优先总结 artifact 里的结论，再决定是否继续落实现或 review。
What ships with it
4 files 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.
- 3d ago First seen · 75 lines · 41 tokens per session scan A cca84b8c08f9
ask is a skill published in the GitHub repository jeffy-w/AgentSkills (2 stars, last pushed 2mo ago), licensed MIT. It adds 41 tokens to every session and 570 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…