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 billbuchanan-code/claude-code-power-setup --skill ask-megit clone --depth 1 https://github.com/billbuchanan-code/claude-code-power-setupWrote 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/billbuchanan-code/claude-code-power-setup/ask-me)<a href="https://agentmods.dev/skills/billbuchanan-code/claude-code-power-setup/ask-me"><img src="https://agentmods.dev/badge/skills/billbuchanan-code/claude-code-power-setup/ask-me/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/billbuchanan-code/claude-code-power-setup/ask-me"><img src="https://agentmods.dev/badge/skills/billbuchanan-code/claude-code-power-setup/ask-me.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.00101 | $0.01521 |
| Opus 5.5 | $0.00040 | $0.00608 |
| Sonnet 5.5 | $0.00020 | $0.00304 |
| Haiku 4.5 | $0.00010 | $0.00152 |
Grade A, and why
ask-me 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/ask-me — research-driven interview
Interview the user about: $ARGUMENTS
If no topic was given, ask one open question (plain text, not the tool) about what to cover, then proceed.
Parse the request
Free text in the arguments may override defaults: a round count ("8 rounds", "at least 10"), an output ("output goal.md", "then write the spec"), "quick" (lightweight mode), "no html". Everything else is the topic. Defaults: 5–10 rounds (adaptive, see Stopping), HTML briefings on, deliverable = decision log unless a spec/goal/plan was requested.
Phase 0 — Research first. Never open with questions.
- Read anything the request names (handoff docs, specs, the codebase, screenshots).
- For product/greenfield topics, launch parallel background research agents (existing tools, open-source prior art, data sources, best practices) and let them run during early rounds.
- Check persistent memory and any existing
ask-me-notes.mdfor preferences already on record — never re-ask a settled preference; surface it in the briefing's "decided so far" strip instead. - Sketch an interview map: 5–10 themes, one per round, ordered so high-stakes decisions come first (architecture, scope, data) and easy/confirmatory ones last (naming, polish).
- Create the notes file (see Compaction safety) before round 1.
The round loop
Each round = briefing → questions → log → adapt.
1. Briefing (skip in quick mode)
Rewrite ONE file — <scratchpad>/ask-me-briefing.html — every round; never create per-round files.
<title> = "Round N: Theme". Start from references/briefing-template.html. Content: what this
round decides, research findings, each option with honest trade-offs, mockups/diagrams when the
question is visual, and a running "decided so far" strip.
Open it with the first viewer that applies — decide once in round 1, then reuse that choice:
- cmux — if
$CMUX_WORKSPACE_IDis set and the CLI exists:/Applications/cmux.app/Contents/Resources/bin/cmux browser open "file://<abs-path>/ask-me-briefing.html"Repeated calls reuse the same pane and reload in place. Never use macOSopenfor HTML when in cmux — it goes to the default browser instead of the cmux pane. - Artifact tool — if available: publish the briefing as an artifact (loading the artifact-design skill first, as its instructions require). Republishing the same file path updates the same URL every round.
- OS default browser —
open(macOS),xdg-open(Linux), orstart(Windows). Tell the user the tab does not auto-refresh, and open the file again each round.
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.
- 1mo ago First seen · 112 lines · 101 tokens per session scan A 1200493d09fa
ask-me is a skill published in the GitHub repository billbuchanan-code/claude-code-power-setup (2 stars, last pushed 2mo ago), licensed MIT. It adds 101 tokens to every session and 1,521 once invoked, about $0.0004 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-31.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.