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 derjochenmeyer/claude-code-craft --skill craft-project-exploregit clone --depth 1 https://github.com/derjochenmeyer/claude-code-craftWrote 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/derjochenmeyer/claude-code-craft/craft-project-explore)<a href="https://agentmods.dev/skills/derjochenmeyer/claude-code-craft/craft-project-explore"><img src="https://agentmods.dev/badge/skills/derjochenmeyer/claude-code-craft/craft-project-explore/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/derjochenmeyer/claude-code-craft/craft-project-explore"><img src="https://agentmods.dev/badge/skills/derjochenmeyer/claude-code-craft/craft-project-explore.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.00024 | $0.00483 |
| Opus 5.5 | $0.00010 | $0.00193 |
| Sonnet 5.5 | $0.00005 | $0.00097 |
| Haiku 4.5 | $0.00002 | $0.00048 |
Grade A, and why
craft-project-explore 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.
What it actually says
craft-project-explore
Discover MCPs and Claude Code integrations that are actually relevant to this project -- not a generic list, a filtered one based on detected stack and workflow patterns.
Behavior
Step 1: Detect project context
Read, in order (skip files that do not exist):
package.jsonrequirements.txtcomposer.jsonCLAUDE.md.craft/PROJECT_STATE.md.craft/BACKLOG.md
Run git log --oneline -10 to detect recent workflow patterns.
From these sources, extract:
- Languages and runtimes
- Frameworks and major dependencies
- External services mentioned (databases, APIs, deployment targets)
- Recurring workflow patterns from backlog and git history
Step 2: Fetch current integrations
Fetch:
https://modelcontextprotocol.io/docs/tools/sampling(or the MCP registry index if available)https://docs.anthropic.com/en/docs/claude-code/mcpfor official Claude Code MCP docs
Step 3: Cross-reference and output
Only include tools that match the detected stack. Do not list generic tools unless they address a pattern seen in the backlog or git history. Cite the source URL for each recommendation.
## Opportunities for [project name]
Based on detected stack: [comma-separated list]
| Tool / Integration | What it enables for this project | Install | Effort |
|-------------------|----------------------------------|---------|--------|
| [name] | [specific to detected needs] | [exact command or URL] | low / medium / high |
Sort by relevance to the detected stack -- most relevant first.
Below the table:
Sources: [URLs fetched]
Want me to install any of these? Reply with numbers.
Rules
- Only recommend real tools with real, verifiable install commands.
- If a tool appears in the registry but has no stable install path, note that instead of guessing.
- Do not pad the table with generic tools to make it look longer.
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.
- 1mo ago First seen · 68 lines · 24 tokens per session scan A b0524258dcf5
craft-project-explore is a skill published in the GitHub repository derjochenmeyer/claude-code-craft (2 stars, last pushed 6mo ago), licensed MIT. It adds 24 tokens to every session and 483 once invoked, about $0.0001 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-08-31.
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…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…