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/davidvujic/my-eca-config/commitnpx skills add DavidVujic/my-eca-config --skill commitgit clone --depth 1 https://github.com/DavidVujic/my-eca-configWhat 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.00017 | $0.00638 |
| Opus 5 | $0.00009 | $0.00319 |
| Sonnet 5 | $0.00003 | $0.00128 |
| Haiku 4.5 | $0.00002 | $0.00064 |
Grade A, and why
commit 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commit Skill
Purpose
Produce a single, well-formed conventional commit from the currently staged changes. The commit message follows the format:
<type>(<scope>): <subject>
<body>
This skill MUST be used whenever a task depends on creating a commit.
Procedure
Follow these steps strictly and in order.
Step 1 — Check for staged changes
Run:
git diff --cached --stat
If the output is empty, stop immediately and inform the user:
"No staged changes found. Stage files with
git addbefore committing."
Do not auto-stage files. Do not proceed.
Step 2 — Obtain the diff context
Load and execute the git-changes-context skill to obtain diff_context.
If the skill returns "error": "NO_DIFF_FOUND", fall back to using the staged diff:
git diff --cached
Capture whichever diff is available as diff.
Step 3 — Analyse the diff and build the commit message
Using diff, determine:
- type — one of:
feat,fix,refactor,docs,style,test,chore,perf,ci,build,revert. - scope (optional) — the primary module, file, or area affected. Omit parentheses entirely if no clear scope exists.
- subject — a short imperative summary (lowercase, no period, max ~72 chars).
- body — a concise description (1–3 sentences) of what changed and why, derived from the diff. Focus on intent, not low-level line changes.
If the user provided a hint (passed as $ARGUMENTS), use it as the subject line.
Still generate the body from the diff. If the hint already contains a type prefix
(e.g. fix: correct null check), honour it and do not override the type.
Step 4 — Execute the commit
Construct the full commit message and run:
git commit -m "<full message>"
Use a HEREDOC to preserve newlines:
git commit -m "$(cat <<'EOF'
<type>(<scope>): <subject>
<body>
EOF
)"
Step 5 — Confirm
Show the user:
- The commit hash (short form).
- The full commit message that was used.
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 · 103 lines · 17 tokens per session scan A 7a0e99f6da8d
commit is a skill published in the GitHub repository DavidVujic/my-eca-config (11 stars, last pushed 4d ago), licensed MIT. It adds 17 tokens to every session and 638 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
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.