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 commands/kernalix7/aips/aips-uninstallgit clone --depth 1 https://github.com/kernalix7/AIPSWhat 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.00018 | $0.00541 |
| Opus 5 | $0.00009 | $0.00270 |
| Sonnet 5 | $0.00004 | $0.00108 |
| Haiku 4.5 | $0.00002 | $0.00054 |
Grade A, and why
aips-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 3d 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
/aips:uninstall
Tear down per-project AIPS state in the current PROJECT_ROOT. Global plugin install in ~/.claude/plugins/AIPS/ is not touched.
What it does
- Locate
PROJECT_ROOT— walk up from$PWDto nearest.gitdirectory. - Confirm — prompt:
Require explicitThis will remove .priv-storage/ and AIPS root symlinks from <PROJECT_ROOT>. A backup will be created at tmp-igbkp/uninstall-backup-<ts>/. Global plugin install will NOT be removed. Proceed? [y/N]y; any other input aborts. - Backup — create
tmp-igbkp/uninstall-backup-<YYYYMMDD-HHMMSS>/and move into it:.priv-storage/(entire dir)- root symlinks:
CLAUDE.md,AGENTS.md,.cursorrules,.vscode/settings.json(only if they resolve into.priv-storage/; never touch unrelated files of the same name)
- Remove — delete the originals after the backup
mvsucceeds. Usemv, notcp + rm, so it is atomic per-file. - Leave alone — do NOT touch:
- Global
~/.claude/plugins/AIPS/install - Project source code, git history,
.git/ tmp-igbkp/(other than creating the new backup subdir).gitignore(leave the AIPS block in place so re-init stays clean)
- Global
Output
[uninstall] backup created tmp-igbkp/uninstall-backup-20260519-143012/
[uninstall] removed .priv-storage/, CLAUDE.md, AGENTS.md, .cursorrules, .vscode/settings.json
[uninstall] global plugin untouched
note: global plugins still installed; run
claude --print '/plugin uninstall AIPS@AIPS'
to fully remove AIPS from this machine.
Rules
- Never delete without a successful backup first.
- Never touch the global plugin or any path outside
PROJECT_ROOT. - Abort cleanly on any non-
yresponse.
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.
- 3d ago First seen · 47 lines · 18 tokens per session scan A 91fab3472470
aips-uninstall is a command published in the GitHub repository kernalix7/AIPS (5 stars, last pushed 3mo ago), licensed MIT. It adds 18 tokens to every session and 541 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-31.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.