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/ciroaurelio22/agentloop/uninstallnpx skills add ciroaurelio22/AgentLoop --skill uninstallgit clone --depth 1 https://github.com/ciroaurelio22/AgentLoopWhat 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.00032 | $0.00454 |
| Opus 5 | $0.00016 | $0.00227 |
| Sonnet 5 | $0.00006 | $0.00091 |
| Haiku 4.5 | $0.00003 | $0.00045 |
Grade A, and why
agent-loop-uninstall 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.
What it actually says
Agent Loop — Uninstall
Remove the Agent Loop kit from this repository (not the global AgentLoop clone).
Before you start
- Confirm the user wants to remove Agent Loop from the current workspace.
- Ask whether to keep task data (
.agent-loop/,specs/agent-tasks/) or remove everything.- Keep data → use
--keep-data - Full removal → default (no flag)
- Keep data → use
Run the uninstaller
From the target repo root, run the kit uninstall script. If the kit is not local, clone it to a temp dir first (same as install):
node "<KIT_DIR>/bin/uninstall.mjs" --target .
With preserved queue and programs:
node "<KIT_DIR>/bin/uninstall.mjs" --target . --keep-data
Replace <KIT_DIR> with the AgentLoop kit path (clone from https://github.com/ciroaurelio22/AgentLoop.git if needed).
What gets removed
| Path | Removed |
|---|---|
scripts/agent/ |
Yes |
tools/agent-gui/ |
Yes |
.cursor/hooks/ (agent-loop hooks) |
Yes |
.cursor/hooks.json |
Yes |
.cursor/skills/uninstall, update |
Yes |
agent-loop.config.json |
Yes |
agent:* scripts in package.json |
Yes |
Agent loop section in CLAUDE.md / AGENTS.md |
Yes |
.agent-loop/, specs/agent-tasks/ |
Only without --keep-data |
After uninstall
- Confirm
pnpm agent:statusfails or script is gone. - Remind the user that Cursor hooks and skills for agent-loop are no longer active.
- Do not delete the user's git history or unrelated project files.
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 · 53 lines · 32 tokens per session scan A e84f44517886
agent-loop-uninstall is a skill published in the GitHub repository ciroaurelio22/AgentLoop (10 stars, last pushed 2mo ago), licensed MIT. It adds 32 tokens to every session and 454 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.