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/youngjaedev/my-claude-plugins/asknpx skills add YoungjaeDev/my-claude-plugins --skill askgit clone --depth 1 https://github.com/YoungjaeDev/my-claude-pluginsWrote 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/youngjaedev/my-claude-plugins/ask)<a href="https://agentmods.dev/skills/youngjaedev/my-claude-plugins/ask"><img src="https://agentmods.dev/badge/skills/youngjaedev/my-claude-plugins/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.00116 | $0.00429 |
| Opus 5 | $0.00058 | $0.00215 |
| Sonnet 5 | $0.00023 | $0.00086 |
| Haiku 4.5 | $0.00012 | $0.00043 |
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 4d 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
DeepWiki ask
Deep query a GitHub repository using DeepWiki's AI-powered documentation. Same workflow as the /deepwiki:ask slash command — this skill exposes it as a capability so the model can reach for it during conversational research.
- Restate the repository (
owner/repo) and the question back to the user so the parse is auditable. - Follow the four-phase procedure (structure → optional contents → ask → optional multi-query expansion).
- Return the answer in the documented output format.
See references/ask-procedure.md in this plugin's installed root for the full workflow, smart-query strategy, multi-repo patterns, and error handling table. Under Claude Code this resolves to ${CLAUDE_PLUGIN_ROOT}/references/ask-procedure.md; under Codex 0.135 (which does not export CLAUDE_PLUGIN_ROOT) the plugin cache directory exposes the same references/ subdirectory next to skills/ (~/.codex/plugins/cache/<marketplace>/deepwiki/<version>/references/). This reference is a plugin-root file (shared with the generate-llmstxt skill), so a skill-level install carries it only when the whole plugin is installed.
Requirements
- DeepWiki MCP must be configured in the host runtime (
mcp__deepwiki__*tools available). If absent, surface the setup link:https://mcp.deepwiki.com/. - Internet connection (queries the DeepWiki API).
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.
- 4d ago First seen · 20 lines · 116 tokens per session scan A 2b57b8ed283a
ask is a skill published in the GitHub repository YoungjaeDev/my-claude-plugins (2 stars, last pushed 9d ago), licensed MIT. It adds 116 tokens to every session and 429 once invoked, about $0.0006 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…