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/dixus/claudeframework/deploynpx skills add dixus/claudeframework --skill deploygit clone --depth 1 https://github.com/dixus/claudeframeworkWhat 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.00040 | $0.01295 |
| Opus 5 | $0.00020 | $0.00647 |
| Sonnet 5 | $0.00008 | $0.00259 |
| Haiku 4.5 | $0.00004 | $0.00129 |
Grade A, and why
deploy 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 2d 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Replace shared framework directories in a target project with junctions pointing back to this framework repo, so updates propagate automatically.
Prerequisites
- The target project must already have a
.claude/directory (either copied from Framework or created fresh) - This skill must be run from the Framework repo (the source of truth)
Shared vs local directories
Shared (symlinked) — maintained in Framework, identical across all projects:
| Dir | Contents |
|---|---|
skills/ |
All 21 skill definitions |
agents/ |
Subagent personas |
rules/ |
Auto-loaded instructions (instincts) |
Local (never symlinked) — project-specific, stay as regular directories:
| Dir | Why local |
|---|---|
context/ |
Project-specific knowledge base |
specs/ |
Feature specs for this project |
reviews/ |
Review reports for this project |
input/ |
Requirements for this project |
references/ |
Research material for this project |
hooks/ |
Project-specific lifecycle hooks |
handoffs/ |
Session state (gitignored) |
docs/ |
Generated docs (project-specific) |
worktrees/ |
Git worktree state |
settings.json |
Project-specific settings |
settings.local.json |
Local overrides |
metrics-pipeline.csv |
Ship pipeline run log |
metrics-scout.csv |
Scout/harvest run log |
Steps
- Validate target path. $ARGUMENTS must be an absolute path or relative path to a project directory. Resolve it to absolute. Confirm
<target>/.claude/exists. If not, ask: "No.claude/directory found at<target>. Copy the full framework first? (Y/N)" — if Y, copy the entire.claude/directory to the target, then continue.
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.
- 2d ago First seen · 100 lines · 40 tokens per session scan A 396aaba1be1d
deploy is a skill published in the GitHub repository dixus/claudeframework (10 stars, last pushed 4mo ago), licensed MIT. It adds 40 tokens to every session and 1,295 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.
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…