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/backspace-shmackspace/claude-devkit/fixnpx skills add backspace-shmackspace/claude-devkit --skill fixgit clone --depth 1 https://github.com/backspace-shmackspace/claude-devkitWhat 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.00022 | $0.04304 |
| Opus 5 | $0.00011 | $0.02152 |
| Sonnet 5 | $0.00004 | $0.00861 |
| Haiku 4.5 | $0.00002 | $0.00430 |
Grade A, and why
fix 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 — 481 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/fix Workflow
Output Rules
- Always print full absolute paths for all artifact references (plan files, review files, audit logs). This makes paths clickable in terminals like Warp. Use the resolved
$PLANS_DIRvalue, never relative paths.
Role
This skill is a pipeline coordinator. It orchestrates a targeted fix workflow: parse a finding from a review artifact, scope the fix, dispatch a coder agent, run focused verification, and commit with traceability back to the source finding. It does NOT write code directly — it delegates implementation to a coder agent and verification to focused subagent tasks.
Finding-driven, not plan-driven: The finding IS the specification. No plan file required or generated.
Supported artifacts: Works with findings from both /ship artifacts (.code-review.md, .secure-review.md, .qa-report.md) and /audit artifacts (audit-[timestamp].security.md, audit-[timestamp].performance.md).
Dry-run mode: Supports --dry-run flag. Runs Steps 0-3 but skips Step 4 (commit). Changes remain in the working directory for manual review.
Inputs
/fix <artifact-path> [finding-id] [--dry-run]
Examples:
/fix $PLANS_DIR/archive/maven-build-support/maven-build-support.secure-review.md H-01
/fix $PLANS_DIR/archive/maven-build-support/maven-build-support.code-review.md M-1
/fix $PLANS_DIR/audit-20260523T143000.security.md C-01
/fix $PLANS_DIR/archive/audit/audit-20260523/audit-20260523.security.md H-02
/fix "command injection in find -exec in pipeline build step" # free-text fallback
/fix $PLANS_DIR/archive/maven-build-support/maven-build-support.secure-review.md H-01 --dry-run
artifact-path: Path to a review artifact (.code-review.md,.secure-review.md,.qa-report.md,.security.md,.performance.md) OR a free-text description of the fixfinding-id: Optional finding ID within the artifact (e.g., H-01, M-1, CR-3, C-01)--dry-run: Optional flag. If present, run Steps 0-3 but skip Step 4 (commit). Changes remain in working directory.
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 · 481 lines · 22 tokens per session scan A 12a60fe68a11
fix is a skill published in the GitHub repository backspace-shmackspace/claude-devkit (15 stars, last pushed 9d ago), licensed MIT. It adds 22 tokens to every session and 4,304 once invoked, about $0.0001 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-30.
Other skills, from other repositories
create-modal
Create declarative modals using the modal library API. Covers modal types (confirm, input, select, form), sections (Text, Buttons, Input, Textarea, Checkbox, List, Combo, When, Custom), rendering with OverlayModal, and keyboard/mouse handling. Use when adding modals or dialogs to the application.
worktree-switching
Git worktree support in sidecar: worktree detection, switching between worktrees, worktree state management, and plugin reinitialization. Covers the full lifecycle of worktree context switching including registry reinit, per-worktree state persistence, deleted worktree detection and fallback. Use when working on git…
autoprompt
Explicit-only useful-first orchestration. Invoke /autoprompt to turn a mission into one executable roadmap, build dependency-safe lanes, and verify the result with independent reviewers. Never infer invocation from ordinary requests. Never resume from leftover artifacts without an explicit resume instruction.
ap-fresh-verifier
L4 blind fresh verifier - independently checks a candidate roadmap or plan against the exact mission and repository; APPROVE/REJECT, default-FAIL.
cron
Schedule reminders and recurring tasks.
agenticx-query-data-source
Use when the user asks about verifiable quantitative facts (stock prices, financial indicators, macro data, company registry, academic metrics, legal statutes) that must come from a live data source rather than training memory.