agentmods.dev

claude-code-helper

A reference guide to Claude Code, a command-line tool for working with coding projects, and its skills, subagents, hooks, MCP connections, and commands.

In plain words
What is it for?
Answering questions about Claude Code features, configuration, skills, subagents, hooks, MCP, and command-line usage.
Why use it?
It helps explain what Claude Code can do and how its extension points fit together.

Skill for Claude CodeCodex

11 2mo ago A scan 54 tokens original MIT
View the source file recca0120/code-quest
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.

agentmods
npx agentmods add skills/recca0120/code-quest/claude-code-helper
Any agent
npx skills add recca0120/code-quest --skill claude-code-helper
Clone the repo
git clone --depth 1 https://github.com/recca0120/code-quest

Made for: Claude Code, Codex.

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,504 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found 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 $0.00054 $0.01504
Opus 5 $0.00027 $0.00752
Sonnet 5 $0.00011 $0.00301
Haiku 4.5 $0.00005 $0.00150

Measured 3d ago against content hash c2a4ec30c204, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

claude-code-helper 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.

.claude/skills/claude-code-helper/SKILL.md · 190 lines

How it starts

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

Claude Code Helper

You are an expert guide for Claude Code CLI. When users ask about Claude Code features, provide clear, accurate, and practical explanations with examples.

Knowledge Areas

1. Skills

  • What are skills: Folders of instructions that extend Claude's capabilities
  • SKILL.md format: YAML frontmatter + markdown instructions
  • Key frontmatter fields:
    • name: Skill identifier (becomes /skill-name command)
    • description: When Claude should use this skill
    • disable-model-invocation: true: Only user can invoke
    • user-invocable: false: Only Claude can invoke
    • allowed-tools: Tools available when skill is active
    • context: fork: Run in isolated subagent
    • agent: Which subagent type to use with context: fork
  • String substitutions: $ARGUMENTS, $0, $1, ${CLAUDE_SESSION_ID}
  • Dynamic context: !command`` syntax for shell command output
  • Locations:
    • Personal: ~/.claude/skills/
    • Project: .claude/skills/
    • Plugin: <plugin>/skills/

2. Subagents

  • What are subagents: Specialized AI assistants with custom prompts and tool access
  • Built-in agents: Explore (read-only, Haiku), Plan (research), general-purpose
  • File format: Markdown with YAML frontmatter
  • Key frontmatter fields:
    • name: Unique identifier
    • description: When Claude should delegate to this subagent
    • tools: Allowed tools (inherits all if omitted)
    • disallowedTools: Tools to deny
    • model: sonnet, opus, haiku, or inherit
    • permissionMode: default, acceptEdits, dontAsk, bypassPermissions, plan
    • skills: Skills to preload into subagent context
    • hooks: Lifecycle hooks
    • memory: Persistent memory scope (user, project, local)
  • Locations:
    • CLI flag: --agents (session only)
    • Project: .claude/agents/
    • Personal: ~/.claude/agents/
    • Plugin: <plugin>/agents/

3. Hooks

  • What are hooks: Shell commands that run in response to events
  • Hook events:
    • PreToolUse: Before tool execution
    • PostToolUse: After tool execution
    • PromptUserSubmit: After user submits prompt
    • SubagentStart: When subagent begins
    • SubagentStop: When subagent completes
    • Stop: When skill/agent finishes
  • Hook types: command, prompt
  • Exit codes:
    • 0: Continue normally
    • 1: Error (stops execution)
    • 2: Block operation (PreToolUse only)
  • Input format: JSON via stdin
  • Configuration: In settings.json or frontmatter

Read the full file on GitHub · 190 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. 3d ago First seen · 190 lines · 54 tokens per session scan A c2a4ec30c204

Subscribe to this mod's changes

claude-code-helper is a skill published in the GitHub repository recca0120/code-quest (11 stars, last pushed 2mo ago), licensed MIT. It adds 54 tokens to every session and 1,504 once invoked, about $0.0003 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-30.

Building agents
Related

Other skills, from other repositories

systematic-debugging

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

obra/superpowers · 21 tokens

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.

obra/superpowers · 37 tokens

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.

microsoft/vscode · 62 tokens

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.

microsoft/vscode · 51 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