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/archive228/loopkit/using-loopkitnpx skills add Archive228/loopkit --skill using-loopkitgit clone --depth 1 https://github.com/Archive228/loopkitWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/archive228/loopkit/using-loopkit)<a href="https://agentmods.dev/skills/archive228/loopkit/using-loopkit"><img src="https://agentmods.dev/badge/skills/archive228/loopkit/using-loopkit.svg" alt="Measured on agentmods" height="20"></a>What 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.00040 | $0.01368 |
| Opus 5 | $0.00020 | $0.00684 |
| Sonnet 5 | $0.00008 | $0.00274 |
| Haiku 4.5 | $0.00004 | $0.00137 |
Grade B, and why
using-loopkit 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 today.
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.
Enumerates other installed skillsmediumAgent snooping
Other skills' SKILL.md files reveal prompts, capabilities and secrets that should be invisible to peers.
Full list: `ls .claude/skills/`. How it starts
The opening of the file, as written. The whole thing — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Using Loopkit
IF A SKILL APPLIES, YOU DO NOT HAVE A CHOICE. YOU MUST USE IT.
This overrides "just answer quickly" instincts. Not negotiable.
The Rule
Invoke relevant skills BEFORE any response or action — including clarifying questions, exploring the codebase, or reading files. If it turns out wrong for the situation, drop it.
Then announce "Using [skill] to [purpose]" and follow the skill exactly. If it has a checklist, create a todo per item.
Where the skills live
Skills are files at .claude/skills/<name>/SKILL.md. Each has YAML frontmatter with name and description (the description is a trigger phrase, not a summary). Load a skill by reading its SKILL.md when its trigger matches your task.
Skill routing (49 skills, 10 tracks)
| Task shape | First skill |
|---|---|
| "Fix this bug" / test failing / crash | systematic-debugging, then read-the-trace |
| "It broke between two commits" | bisect-regression |
| "Flaky test" | flaky-hunter |
| "Add a feature" / write anything new | spec-first, then write-failing-test-first |
| "Refactor" / dead code / deep nesting | kill-dead-code, simplify, reduce-nesting |
| About to claim done / commit / open PR | adversarial-verify + verification-before-completion + self-eval-bias |
| Review a diff | adversarial-verify, pr-from-diff |
| Frontend / UI work | design-system, a11y-pass, loading-empty-error-states |
| Security touch | owasp-review, authz-check, input-validation, secret-scan, dependency-audit |
| Data / SQL / migrations | sql-review, migration-writer, schema-diff |
| Docs / changelog / README | changelog-from-diff, decision-record, readme-audit |
| Git ops | clean-commits, pr-from-diff, rebase-safely, revert-surgical |
| Test suite gaps | coverage-gaps, contract-test |
| Running out of context | context-budget, tool-restraint |
| Parallel work | subagent-fanout |
| Starting a fresh project / major feature | planner-spec-expand, then feature-list-json, then init-script-contract |
| Bootstrapping into an existing multi-session project | progress-reading-protocol |
| Entering an implementation sprint | sprint-contract |
| Calibrating a reviewer / evaluator | evaluator-calibration |
| New Claude/Sonnet/Opus model landed | harness-stripping |
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.
- today First seen · 102 lines · 40 tokens per session scan B 8125467db686
using-loopkit is a skill published in the GitHub repository Archive228/loopkit (755 stars, last pushed 1mo ago), licensed MIT. It adds 40 tokens to every session and 1,368 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (enumerates other installed skills). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
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…