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/local-confignpx skills add Zate/cc-plugins --skill local-configgit 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.00030 | $0.01592 |
| Opus 5 | $0.00015 | $0.00796 |
| Sonnet 5 | $0.00006 | $0.00318 |
| Haiku 4.5 | $0.00003 | $0.00159 |
Grade A, and why
local-config 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 — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Local Configuration
Project-specific devloop settings via .devloop/local.md (NOT git-tracked).
Format
YAML frontmatter followed by optional markdown notes:
---
git:
auto-branch: false # Create branch when plan starts
branch-pattern: "feat/{slug}" # {slug}, {date}, {user}
main-branch: main
pr-on-complete: ask # ask | always | never
worktree_isolation: false # Isolate swarm workers in git worktrees (opt-in)
commits:
style: conventional # conventional | simple
scope-from-plan: true
sign: false
review:
before-commit: ask # ask | always | never
use-plugin: null # null | code-review | pr-review-toolkit
github:
link-issues: false # Enable GH issue linking
auto-close: ask # ask | always | never
comment-on-complete: true
tokens:
token_budget: 4000 # Max tokens for gather-task-context.sh output (default: 4000)
cache_friendly_context: true # Order agent prompts for prompt cache hits (default: true)
---
Settings Reference
| Setting | Values | Default |
|---|---|---|
git.auto-branch |
true/false | false |
git.branch-pattern |
Pattern with {slug}, {date}, {user} | feat/{slug} |
git.pr-on-complete |
ask/always/never | ask |
git.worktree_isolation |
true/false | false |
commits.style |
conventional/simple | conventional |
commits.sign |
true/false | false |
review.before-commit |
ask/always/never | ask |
review.use-plugin |
null/code-review/pr-review-toolkit | null |
github.link-issues |
true/false | false |
github.auto-close |
ask/always/never | ask |
github.comment-on-complete |
true/false | true |
fresh_threshold |
5-50 | 10 |
context_threshold |
50-95 | 70 |
tokens.token_budget |
1000-20000 | 4000 |
tokens.cache_friendly_context |
true/false | true |
Example Configurations
Minimal (Git-aware)
---
git:
auto-branch: true
---
Full CI/CD Workflow
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 · 194 lines · 30 tokens per session scan A 4c2d62837c6f
local-config is a skill published in the GitHub repository Zate/cc-plugins (10 stars, last pushed 1mo ago), licensed MIT. It adds 30 tokens to every session and 1,592 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.
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.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
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.