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-session-solidifygit 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-session-solidify)<a href="https://agentmods.dev/skills/derjochenmeyer/claude-code-craft/craft-session-solidify"><img src="https://agentmods.dev/badge/skills/derjochenmeyer/claude-code-craft/craft-session-solidify/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-session-solidify"><img src="https://agentmods.dev/badge/skills/derjochenmeyer/claude-code-craft/craft-session-solidify.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.00064 | $0.01615 |
| Opus 5.5 | $0.00026 | $0.00646 |
| Sonnet 5.5 | $0.00013 | $0.00323 |
| Haiku 4.5 | $0.00006 | $0.00161 |
Grade A, and why
craft-session-solidify 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.
How it starts
The opening of the file, as written. The whole thing — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
craft-session-solidify
Save the current state — then keep working.
When to run
- Automatic: when the context monitor reports ~75% utilization
- Manual: when the user types
/craft-session-solidify - Proactive: when you notice a lot has happened that is not yet documented and the context window is filling up
Scope — what does NOT belong here
This skill maintains project documentation in .craft/. It does not maintain Claude's own memory. The boundary:
| Tool | Purpose | Target |
|---|---|---|
/craft-session-solidify |
Project state, backlog, decisions, handover | .craft/*.md |
/remember |
Save a single fact, decision, or warning | .claude/memory/YYYYMMDD_*.md |
/learn |
Abstract a pattern from context into a transferable insight | .claude/memory/YYYYMMDD_*.md |
Concretely: do not write new .claude/memory/ entries from this skill. If you notice during the solidify that a fact or pattern is worth keeping — mention it in the closing report as a recommendation (worth a /remember or worth a /learn), but do not write it yourself.
.craft/DECISIONS.md (project-level ADR log) and .claude/memory/ entries with type=decision (Claude's personal memory) are deliberately different layers. Some duplication is fine, but it is not the goal of this skill.
Steps
1. Get an overview
git diff --stat HEAD 2>/dev/null
git status --short 2>/dev/null
git log --oneline -5 2>/dev/null
ls .craft/ 2>/dev/null || echo "no .craft/"
If there is no .craft/: run anyway, but skip the doc-writing steps. Commit and short report still happen. At the end, suggest running /craft-project-setup.
2. Update .craft/PROJECT_STATE.md
Prepend a section at the top (newest state first):
## State: [YYYY-MM-DD HH:MM]
### Working
- ...
### In progress
- ...
### Known issues
- ...
### Technical debt
- ...
Be honest. If something is not working, say so explicitly — do not omit.
3. Update .craft/BACKLOG.md
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 · 192 lines · 64 tokens per session scan A f3bddde3128c
craft-session-solidify is a skill published in the GitHub repository derjochenmeyer/claude-code-craft (2 stars, last pushed 6mo ago), licensed MIT. It adds 64 tokens to every session and 1,615 once invoked, about $0.0003 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…