ask

ask is a skill for Claude Code from pleaseai/claude-code-plugins. It costs 54 tokens per session (1,482 once invoked), scanned A, a copy of ask, MIT.

A code-exploration assistant that answers questions using the original AI conversations behind AI-written code.

In plain words
What is it for?
Use it to investigate selected lines, files, symbols, or codebase behavior and ask about the decisions behind them.
Why use it?
It helps explain how code works and why it was built that way when the implementation alone is hard to understand.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: mentions subagents; installed under .agents/ (shared by several agents).

Part of the git-ai plugin — 3 skills shipped together

Good fit Use it to investigate selected lines, files, symbols, or codebase behavior and ask about the decisions behind them.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/pleaseai/claude-code-plugins/ask
Install

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.

Any agent
npx skills add pleaseai/claude-code-plugins --skill ask
Clone the repo
git clone --depth 1 https://github.com/pleaseai/claude-code-plugins

Made for: Claude Code.

Or install git-ai, the plugin that ships this one along with the rest of its 3 skills.

Wrote 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.

agentmods badge for ask

README.md
[![agentmods](https://agentmods.dev/badge/skills/pleaseai/claude-code-plugins/ask/github.svg)](https://agentmods.dev/skills/pleaseai/claude-code-plugins/ask)
Your own site
<a href="https://agentmods.dev/skills/pleaseai/claude-code-plugins/ask"><img src="https://agentmods.dev/badge/skills/pleaseai/claude-code-plugins/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.

agentmods 80×15 button for ask

Your own site · 80×15
<a href="https://agentmods.dev/skills/pleaseai/claude-code-plugins/ask"><img src="https://agentmods.dev/badge/skills/pleaseai/claude-code-plugins/ask.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 54 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,482 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00054 $0.01482
Opus 5.5 $0.00022 $0.00593
Sonnet 5.5 $0.00011 $0.00296
Haiku 4.5 $0.00005 $0.00148

Measured 1mo ago against content hash b9bb8bd00413, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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.

Origin

This is a copy

100% identical to ask — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

plugins/git-ai/.agents/skills/ask/SKILL.md · 141 lines

How it starts

The opening of the file, as written. The whole thing — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Ask Skill

Answer questions about AI-written code by finding the original prompts and conversations that produced it, then embodying the author agent's perspective to answer.

Main Agent's Job (you)

You do the prep work, then hand off to a fast, tightly scoped subagent:

  1. Resolve the file path and line range — check these sources in order:

    a) Editor selection context (most common). When the user has lines selected in their editor, a <system-reminder> is injected into the conversation like:

    The user selected the lines 2 to 4 from /path/to/file.rs:
    _flush_logs(args: &[String]) {
        flush::handle_flush_logs(args);
    }
    

    Extract the file path and line range directly from this. This is the primary way users will invoke /ask — they select code, then type something like "/ask why is this like that" without naming the file or lines.

    b) Explicit file/line references — "on line 42", "lines 10-50 of src/main.rs" → use directly.

    c) Named symbol — mentions a variable/function/class → Read the file, find where it's defined, extract line numbers.

    d) File without line specifics → whole file (omit --lines).

    e) No file, no lines, no selection context, no identifiable code reference → Do NOT attempt to guess or search. Just reply:

    Select some code or mention a specific file/symbol, then /ask your question.

    Stop here. Do not spawn a subagent.

  2. Spawn one subagent with the template below. Use max_turns: 4.

  3. Relay the answer to the user. That's it.

Subagent Configuration

Task tool settings:
  subagent_type: "general-purpose"
  max_turns: 4

The subagent gets only Bash and Read. It does NOT get Glob, Grep, or Task. It runs at most 4 turns — this is a fast lookup, not a research project.

If you want to read an entire file or range of lines AND the corresponding prompts behind them, use git-ai blame --show-prompt. This is better than search for this use case — it gives you every line's authorship plus the full prompt JSON in one call.

Read the full file on GitHub · 141 lines

Changes

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.

  1. 1mo ago First seen · 141 lines · 54 tokens per session scan A b9bb8bd00413

Subscribe to this mod's changes

ask is a skill published in the GitHub repository pleaseai/claude-code-plugins (16 stars, last pushed 5d ago), licensed MIT. It adds 54 tokens to every session and 1,482 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to ask, differing in 0 lines, and is treated as a copy.

Related

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…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

vercel/next.js · 95 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens