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/derjochenmeyer/claude-code-craft/craft-update-selfnpx skills add derjochenmeyer/claude-code-craft --skill craft-update-selfgit 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-update-self)<a href="https://agentmods.dev/skills/derjochenmeyer/claude-code-craft/craft-update-self"><img src="https://agentmods.dev/badge/skills/derjochenmeyer/claude-code-craft/craft-update-self.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.00025 | $0.00922 |
| Opus 5 | $0.00013 | $0.00461 |
| Sonnet 5 | $0.00005 | $0.00184 |
| Haiku 4.5 | $0.00003 | $0.00092 |
Grade D, and why
craft-update-self scanned grade D with 3 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 4d 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
curl -fsSL https://raw.githubusercontent.com/derjochenmeyer/claude-code-craft-statusline/main/install.sh | bash Enumerates other installed skillsmediumAgent snooping
Other skills' SKILL.md files reveal prompts, capabilities and secrets that should be invisible to peers.
## Step 1: Read installed skills Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
remote_ver=$(curl -sf "$GITHUB_RAW/skills/$skill/SKILL.md" | grep "^version:" | head -1 | awk '{print $2}') How it starts
The opening of the file, as written. The whole thing — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
craft-update-self
Check for updates to your installed craft skills. Completes in a single response.
Usage
/craft-update-self check for updates, show what is available
/craft-update-self apply check and apply all updates in one go
Step 1: Read installed skills
SKILLS_DIR="$HOME/.claude/skills"
GITHUB_RAW="https://raw.githubusercontent.com/derjochenmeyer/claude-code-craft/main"
SKILLS=(
craft-project-setup
craft-project-status
craft-project-audit
craft-project-audit-full
craft-project-dream
craft-project-remember
craft-project-explore
craft-global-audit
craft-session-solidify
craft-update-self
)
for skill in "${SKILLS[@]}"; do
target="$SKILLS_DIR/$skill/SKILL.md"
if [[ -f "$target" ]]; then
local_ver=$(grep "^version:" "$target" | head -1 | awk '{print $2}')
else
local_ver="not installed"
fi
remote_ver=$(curl -sf "$GITHUB_RAW/skills/$skill/SKILL.md" | grep "^version:" | head -1 | awk '{print $2}')
echo "$skill|$local_ver|${remote_ver:-unavailable}"
done
The statusline lives in its own repo and tracks its own version — this skill only manages craft skills. To update the statusline, re-run its installer:
curl -fsSL https://raw.githubusercontent.com/derjochenmeyer/claude-code-craft-statusline/main/install.sh | bash
Step 2: Compare versions and classify
For each skill, classify as:
- up to date: local version == remote version
- update available: local version != remote version (and both are valid semver)
- new skill: skill is not installed locally but exists on GitHub
- unavailable: could not fetch remote version (network issue or skill removed)
Do NOT classify "unavailable" as an update. Skip it silently.
Step 3: Output
No apply arg — check only
Show a compact table:
craft skills installed latest
craft-project-setup 1.0.0 1.0.0 ✅
craft-project-status 1.0.0 1.0.0 ✅
craft-project-audit 1.0.0 1.0.0 ✅
craft-global-audit 1.0.0 1.0.1 ⬆️ update available
craft-update-self — 1.0.0 ✨ new skill
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.
- 4d ago First seen · 132 lines · 25 tokens per session scan D 1fbd5db8b73d
craft-update-self is a skill published in the GitHub repository derjochenmeyer/claude-code-craft (2 stars, last pushed 4mo ago), licensed MIT. It adds 25 tokens to every session and 922 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it D with 3 findings (downloads and executes remote code, enumerates other installed skills, makes network calls). 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…