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/yusufalikync/ccs/dev-installnpx skills add yusufalikync/ccs --skill dev-installgit clone --depth 1 https://github.com/yusufalikync/ccsWhat 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.00013 | $0.00269 |
| Opus 5 | $0.00006 | $0.00134 |
| Sonnet 5 | $0.00003 | $0.00054 |
| Haiku 4.5 | $0.00001 | $0.00027 |
Grade B, and why
dev-install scanned grade B with 1 finding 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
2. Check `~/.claude/settings.json` contains `statusLine` key: read the file and confirm the `statusLine` configuration is present What it actually says
Dev Install
Quick shortcut to run the CLI during local development.
Instructions
Run the CLI command based on $ARGUMENTS:
node bin/cli.js $ARGUMENTS
If $ARGUMENTS is empty, default to status.
Post-run Verification
After the command completes, verify the result:
After install
- Check
~/.claude/statusline.shexists:ls -la ~/.claude/statusline.sh - Check
~/.claude/settings.jsoncontainsstatusLinekey: read the file and confirm thestatusLineconfiguration is present
After uninstall
- Confirm
~/.claude/statusline.shis gone:ls ~/.claude/statusline.sh 2>&1 - Confirm
statusLinekey removed from~/.claude/settings.json: read the file and check
After status
Just display the output — no additional checks needed.
Report what happened and whether verification passed.
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 · 40 lines · 13 tokens per session scan B 7c40aaca493e
dev-install is a skill published in the GitHub repository yusufalikync/ccs (2 stars, last pushed 5mo ago), licensed MIT. It adds 13 tokens to every session and 269 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). 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.
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.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…