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/robinslange/learning-loop/uninstallnpx skills add robinslange/learning-loop --skill uninstallgit clone --depth 1 https://github.com/robinslange/learning-loopWhat 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.00054 | $0.00376 |
| Opus 5 | $0.00027 | $0.00188 |
| Sonnet 5 | $0.00011 | $0.00075 |
| Haiku 4.5 | $0.00005 | $0.00038 |
Grade C, and why
uninstall scanned grade C 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
`rm -rf ~/.claude/plugins/data/learning-loop-learning-loop-marketplace/` What it actually says
Uninstall learning-loop
Removing the plugin via /plugin alone leaves two artefacts behind: the
episodic-memory MCP entry in ~/.claude.json and the captured-index data
dir. This skill walks the full removal with operator confirmation.
Steps
-
Confirm intent. Ask the operator to confirm they want to fully remove learning-loop, including all captured indexes (backlinks, justification index, session labels). If they only want hooks off, point them at the
disableAllHooks: trueguidance in the README's "Disabling parts without uninstalling" section instead and stop. -
Remove the plugin. Tell the operator to run
/pluginand remove learning-loop via the marketplace UI. (Claude cannot drive the marketplace UI; the operator does this step.) -
Remove the dependent MCP (confirm first):
claude mcp remove episodic-memoryNote: only if no OTHER installed plugin depends on episodic-memory. Check withclaude mcp listand ask before removing. -
Purge captured indexes (confirm first — irreversible):
rm -rf ~/.claude/plugins/data/learning-loop-learning-loop-marketplace/Show the operator the dir'sdu -shsize before deleting so they see what is being purged.
Report what was removed and what (if anything) the operator chose to keep.
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 · 36 lines · 0 tokens per session scan C a655e8690da1
uninstall is a skill published in the GitHub repository robinslange/learning-loop (11 stars, last pushed 11d ago), licensed Apache-2.0. It adds 54 tokens to every session and 376 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). 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.
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…