claude-code

claude-code is a skill for Claude Code, Codex from djscheuf/agentic-dev-ecosystem-template. It costs 61 tokens per session (802 once invoked), scanned A, original, MIT.

A reference guide for Claude Code, a command-line tool that can read, change, and run code through an agent loop. It covers its commands, settings, permissions, hooks, skills, and connections to external tools.

In plain words
What is it for?
Use it when working with the claude command, project configuration, automated runs, permissions, lifecycle hooks, or scripts and agents that wrap Claude Code.
Why use it?
It helps developers understand how to configure, automate, and troubleshoot Claude Code instead of guessing at command flags or configuration files.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: reads .claude/ paths; mentions CLAUDE.md; mentions subagents.

Good fit Use it when working with the claude command, project configuration, automated runs, permissions, lifecycle hooks, or scripts and agents that wrap Claude Code.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/djscheuf/agentic-dev-ecosystem-template/claude-code
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 djscheuf/agentic-dev-ecosystem-template --skill claude-code
Clone the repo
git clone --depth 1 https://github.com/djscheuf/agentic-dev-ecosystem-template

Made for: Claude Code, Codex.

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

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/djscheuf/agentic-dev-ecosystem-template/claude-code"><img src="https://agentmods.dev/badge/skills/djscheuf/agentic-dev-ecosystem-template/claude-code.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 61 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 802 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 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.1 $0.00061 $0.00802
Opus 5.5 $0.00024 $0.00321
Sonnet 5.5 $0.00012 $0.00160
Haiku 4.5 $0.00006 $0.00080

Measured 22d ago against content hash 2f906caf05e5, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

claude-code 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 22d 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.

.agents/skills/claude-code/SKILL.md · 36 lines

How it starts

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

Claude Code

Anthropic's agentic CLI (claude): an interactive terminal agent that reads, writes, and runs code in a loop — model proposes, tools execute, results feed back — until the task is done. Same binary powers interactive sessions, headless claude -p runs, the Agent SDK, Desktop, and cloud sessions, so configuration and debugging techniques transfer across surfaces.

Quick mental model:

  • Prompt goes in (terminal, flag, stdin, or SDK call); agent loop iterates tool calls; result comes out
  • Config layers: managed → local → project → user settings.json, env vars, CLI flags (see configuration.md for precedence)
  • Context fills from CLAUDE.md, .claude/ skills/agents/rules, .mcp.json servers, system prompt — --bare skips all of it, --safe-mode skips customizations but keeps auth/permissions
  • Permissions gate every tool call via rules + mode + prompt fallback; hooks can observe/block/rewrite at each lifecycle point

Common one-liners:

claude                                    # interactive session
claude -p "task" --output-format json     # one-shot scripted run
claude -c / claude -r <id>                # continue / resume a session
claude doctor                             # diagnose install & settings

Reference files

  • ref/cli-usage.md — commands & flags, interactive session controls (slash commands, vim/editor modes, Plan mode, background tasks), session lifecycle, keybindings. Consult for how to drive claude day-to-day.
  • ref/configuration.md — settings.json files & precedence, all key settings, env vars, ~/.claude directory layout, CLAUDE.md/memory mechanics, model selection, --settings/--setting-sources for passing config on the CLI. Consult for anything about where config lives or why a value applies.
  • ref/hooks.md — every hook event, matcher syntax, JSON stdin contract, exit codes & control fields, prompt/agent/HTTP hook types, hook security model. Consult when writing or debugging hooks.
  • ref/permissions.md — permission rule syntax, modes (Manual/auto/dontAsk/acceptEdits/plan), what each built-in tool can do, sandboxed Bash, workspace trust. Consult when a call prompts/gets denied or when writing allow/deny rules.
  • ref/extending.md — skills, subagents, MCP servers, plugins: frontmatter schemas, scopes, transports, approval flows, mechanism-selection guide. Consult when adding capabilities or packaging for a team.
  • ref/headless-and-sdk.md — claude -p print mode, output formats & stream-json event model, --bare, unattended permission strategies, process lifecycle signals, Agent SDK overview. Consult when scripting or wrapping Claude Code.
  • ref/debugging.md — /context, /doctor, /debug, safe-mode & clean-config isolation, common failure patterns (hooks not firing, MCP down, settings ignored), error-message map, performance fixes. Consult first when something's wrong.

Read the full file on GitHub · 36 lines

Files

What ships with it

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

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. 22d ago First seen · 36 lines · 61 tokens per session scan A 2f906caf05e5

Subscribe to this mod's changes

claude-code is a skill published in the GitHub repository djscheuf/agentic-dev-ecosystem-template (12 stars, last pushed 20d ago), licensed MIT. It adds 61 tokens to every session and 802 once invoked, about $0.0002 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-10-01.

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