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 agentmods add skills/benshapyro/cadre-devkit-claude/devkit-knowledgenpx skills add benshapyro/cadre-devkit-claude --skill devkit-knowledgegit clone --depth 1 https://github.com/benshapyro/cadre-devkit-claudeWrote 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/benshapyro/cadre-devkit-claude/devkit-knowledge)<a href="https://agentmods.dev/skills/benshapyro/cadre-devkit-claude/devkit-knowledge"><img src="https://agentmods.dev/badge/skills/benshapyro/cadre-devkit-claude/devkit-knowledge.svg" alt="Measured on agentmods" 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 | $0.00035 | $0.00661 |
| Opus 5 | $0.00017 | $0.00331 |
| Sonnet 5 | $0.00007 | $0.00132 |
| Haiku 4.5 | $0.00003 | $0.00066 |
Grade A, and why
devkit-knowledge 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.
How it starts
The opening of the file, as written. The whole thing — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cadre DevKit Knowledge Base
This skill helps you find information in the devkit. Read the actual files - they are the source of truth.
Where to Find Things
| Topic | Location |
|---|---|
| Global config | ~/.claude/CLAUDE.md |
| Commands | ~/.claude/commands/*.md |
| Skills | ~/.claude/skills/*/SKILL.md |
| Hooks | ~/.claude/hooks/ + settings.json |
| References | ~/.claude/references/*.md |
| Agents | Defined in system, use Task tool |
Quick Answers
How do I add a command?
Create ~/.claude/commands/my-command.md:
---
description: What this command does
argument-hint: [optional args]
---
# My Command
Instructions for Claude...
How do I add a skill?
Create ~/.claude/skills/my-skill/SKILL.md:
---
name: my-skill-name
description: What it does and when to use it.
---
# My Skill
Instructions and examples...
Skills vs Agents?
- Skills = Knowledge (methodology, templates, best practices)
- Agents = Workers (spawned via Task tool to do tasks independently)
Skills inform how to do something. Agents actually do things.
Debug hooks not running?
- Enable debug mode:
CLAUDE_HOOK_DEBUG=1 - Check
settings.jsonhas hook registered - Verify file is executable (
chmod +x)
Skill not activating?
- Check YAML frontmatter is valid (name + description)
- Ensure description has trigger keywords
- Try explicit reference: "Use the X skill"
Command workflow?
New Project:
/greenfield → SPEC.md + DESIGN.md + PLAN.md → /plan [feature] → implement → /review → /validate → /ship
Existing Project:
/plan [feature] → implement → /slop (optional) → /review → /validate → /ship
Research:
/research [topic] → findings → /progress (save as docs)
Project vs Global
| Location | Scope |
|---|---|
~/.claude/ |
All projects (personal) |
./.claude/ |
This project only (team) |
Project-level config takes precedence over global.
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.
- 3d ago First seen · 105 lines · 35 tokens per session scan A afff634da998
devkit-knowledge is a skill published in the GitHub repository benshapyro/cadre-devkit-claude (9 stars, last pushed 9mo ago), licensed MIT. It adds 35 tokens to every session and 661 once invoked, about $0.0002 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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.
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.
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.
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…