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 djscheuf/agentic-dev-ecosystem-template --skill claude-codegit clone --depth 1 https://github.com/djscheuf/agentic-dev-ecosystem-templateWrote 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/djscheuf/agentic-dev-ecosystem-template/claude-code)<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.
<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>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.00061 | $0.00802 |
| Opus 5.5 | $0.00024 | $0.00321 |
| Sonnet 5.5 | $0.00012 | $0.00160 |
| Haiku 4.5 | $0.00006 | $0.00080 |
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.
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.jsonservers, system prompt —--bareskips all of it,--safe-modeskips 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 driveclaudeday-to-day.ref/configuration.md— settings.json files & precedence, all key settings, env vars,~/.claudedirectory layout, CLAUDE.md/memory mechanics, model selection,--settings/--setting-sourcesfor 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 -pprint 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.
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.
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.
- 22d ago First seen · 36 lines · 61 tokens per session scan A 2f906caf05e5
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.
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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…