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/vladm3105/aidoc-flow-framework/uninstallgit clone --depth 1 https://github.com/vladm3105/aidoc-flow-frameworkWrote 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/commands/vladm3105/aidoc-flow-framework/uninstall)<a href="https://agentmods.dev/commands/vladm3105/aidoc-flow-framework/uninstall"><img src="https://agentmods.dev/badge/commands/vladm3105/aidoc-flow-framework/uninstall.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.00026 | $0.00817 |
| Opus 5 | $0.00013 | $0.00409 |
| Sonnet 5 | $0.00005 | $0.00163 |
| Haiku 4.5 | $0.00003 | $0.00082 |
Grade A, and why
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 4d 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Uninstall
A slash command cannot remove the plugin that's running it — Claude Code's
native /plugin uninstall does. This command is a guided exit: it
confirms intent, prints the exact native command to run, lists what the
native uninstall removes vs preserves, and offers to clean only the
plugin-written scratch in the current project.
Instructions
-
Confirm intent — ask once. If the user answers anything other than a clear yes, stop and acknowledge.
Removing aidoc-flow has two parts: 1. Uninstalling the plugin itself (Claude Code native command — your job) 2. Optionally cleaning plugin-written scratch in this project (this command) Want to proceed? -
Print the native uninstall command — exactly:
To uninstall the plugin, run this in Claude Code: /plugin uninstall aidoc-flow@aidoc-flow-framework This command (the one you're running now) cannot do that for you — a plugin slash command cannot remove the plugin it lives in. -
Print what native uninstall removes vs preserves:
The native uninstall WILL remove: - The plugin's installed files (skills, agents, commands, hooks) - The PostToolUse review-nudge hook registration The native uninstall WILL NOT touch: - Your project's docs/ artifacts (BRD, PRD, EARS, …) - Your project's .aidoc/ audit and review artifacts - Your project's .claude/aidoc-flow.config.yaml (if present) - Anything else under your project root -
Offer optional cleanup of plugin-written scratch in the current project only (not the install itself). The default is to leave files alone — user must opt in per item.
Optional: clean plugin-written state in this project. [ ] .aidoc/ scratch directory (audit and review artifacts) — usually keep [ ] .claude/aidoc-flow.config.yaml (your overrides) — usually keep [ ] .claude/CLAUDE.md "Work Plans Directory" line — usually keep Defaults are to keep everything. Anything you check is your work — make sure it's backed up.
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.
- 4d ago First seen · 105 lines · 26 tokens per session scan A ac2c10444dba
uninstall is a command published in the GitHub repository vladm3105/aidoc-flow-framework (17 stars, last pushed yesterday), licensed MIT. It adds 26 tokens to every session and 817 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
kb-archive
Archive, detach, purge, or rename KB objects while keeping registry, index, and links consistent.
vbw:discuss
Start or continue phase discussion to build context before planning.
vbw:init
Set up environment, scaffold .vbw-planning, detect project context, and bootstrap project-defining files.
reapdev.versionBump
Version bump — 변경 분석 후 bump 유형을 제안, 유저가 최종 결정.
reapdev.docsUpdate
REAP Dev — Update docs, README based on code changes.
reapdev.resolveIssue
Resolve Issue — GitHub Issue를 분석하고 해결.