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/zate/cc-plugins/devloop-auditnpx skills add Zate/cc-plugins --skill devloop-auditgit clone --depth 1 https://github.com/Zate/cc-pluginsWhat 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.00032 | $0.00827 |
| Opus 5 | $0.00016 | $0.00413 |
| Sonnet 5 | $0.00006 | $0.00165 |
| Haiku 4.5 | $0.00003 | $0.00083 |
Grade A, and why
devloop-audit 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 yesterday.
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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Devloop Audit
Audit devloop against Claude Code's evolving capabilities.
When to Run
- After major Claude Code releases
- Monthly maintenance check
- When noticing new Claude Code features
Audit Process
Step 1: Gather Claude Code Information
- Fetch Release Notes: https://code.claude.com/docs/en/changelog.md
- Review Key Docs: Skills, Plugins, Hooks, Sub-agents at code.claude.com/docs/en/
Step 2: Analyze Current devloop
ls plugins/devloop/agents/
ls plugins/devloop/skills/
Step 3: Compare and Identify Gaps
| Category | Questions |
|---|---|
| Overlap | Does native Claude Code now provide this? |
| Enhancement | Can new features improve this? |
| Deprecation | Are we using outdated patterns? |
| Missing | New capabilities to adopt? |
Step 4: Generate Findings Report
Priority Ranking:
- High: Native feature replaces devloop, security issue, blocks users
- Medium: Partial overlap, improves UX, aligns with best practices
- Low: Minor improvement, nice-to-have
Effort Estimation:
- Low: <1 day, localized change
- Medium: 1-3 days, multiple files
- High: 3+ days, architectural change
Save to .devloop/spikes/claude-code-audit-YYYY-MM-DD.md:
# Claude Code Audit Findings
**Date**: YYYY-MM-DD
**Claude Code Version**: X.Y.Z
**devloop Version**: X.Y.Z
## Summary
Brief overview.
## Integration Opportunities
### High Priority
| Finding | Current State | Action | Effort |
|---------|--------------|--------|--------|
### Medium Priority
...
## Deprecated Patterns
| Pattern | Native Alternative | Migration |
|---------|-------------------|-----------|
## New Features to Adopt
| Feature | Use Case | Notes |
|---------|----------|-------|
Step 5: Offer Next Steps
AskUserQuestion:
questions:
- question: "Audit complete. What next?"
header: "Action"
options:
- label: "Create spike from findings"
- label: "Create plan from findings"
- label: "Review findings"
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.
- yesterday First seen · 129 lines · 32 tokens per session scan A 6b97f2a51f32
devloop-audit is a skill published in the GitHub repository Zate/cc-plugins (10 stars, last pushed 1mo ago), licensed MIT. It adds 32 tokens to every session and 827 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…