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/configuregit 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/configure)<a href="https://agentmods.dev/commands/vladm3105/aidoc-flow-framework/configure"><img src="https://agentmods.dev/badge/commands/vladm3105/aidoc-flow-framework/configure.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.00036 | $0.01135 |
| Opus 5 | $0.00018 | $0.00567 |
| Sonnet 5 | $0.00007 | $0.00227 |
| Haiku 4.5 | $0.00004 | $0.00113 |
Grade A, and why
configure 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Configure
Bulk editor for the optional project-local config file at
.claude/aidoc-flow.config.yaml. For focused single-concern editing, prefer
/aidoc-flow:budget (effort knob) or /aidoc-flow:model (recommended model
per layer). All three commands edit the same file.
The schema, defaults, and enums are documented in
${CLAUDE_PLUGIN_ROOT}/docs/CONFIG.md — that doc is the contract. This
command reads and writes the file according to it.
Invocations
| Form | Action |
|---|---|
/aidoc-flow:configure |
Guided bulk editor — prompt per setting |
/aidoc-flow:configure show |
Print the current effective config (file ∪ defaults), no prompts |
/aidoc-flow:configure reset |
After confirmation, delete .claude/aidoc-flow.config.yaml (back to defaults) |
Instructions
-
Detect intent — look at the user's command for the optional subcommand (
show/reset); default to the guided editor. -
showpath:- If
.claude/aidoc-flow.config.yamlexists and parses, print it verbatim with a headerCurrent config (from file):. - If it does not exist, print the documented defaults under the header
No config file — these are the defaults that apply:. Source the defaults from${CLAUDE_PLUGIN_ROOT}/docs/CONFIG.md(the YAML fenced block). - Stop.
- If
-
resetpath:- Confirm intent: "Delete
.claude/aidoc-flow.config.yaml? This reverts every key to the default documented in${CLAUDE_PLUGIN_ROOT}/docs/CONFIG.md." - On yes: delete the file; print "Config reset. Defaults now apply."
- On no: print "Leaving config in place." and stop.
- Confirm intent: "Delete
-
Guided editor path (default):
a. Read current state — if the file exists, load it. Otherwise start from the defaults documented in
${CLAUDE_PLUGIN_ROOT}/docs/CONFIG.md.b. Prompt per setting using
AskUserQuestion. One question per top-level concern, in this order:docs_root(free text; defaultdocs/)work_plans_dir(free text; defaultwork_plans/)skip_layers(multi-select fromBRD | PRD | EARS | BDD | ADR | SPEC | TDD | IPLAN; default none)output_language(free text; ISO 639-1; defaulten)review_hook(single-select:on | off | verbose; defaulton)budget.profile(single-select:max | standard | min; defaultstandard)model.default(free text; defaultclaude-sonnet-4-6)model.precheck(single-select:warn | silent | block; defaultwarn)
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 · 103 lines · 36 tokens per session scan A 4d21fb75227e
configure is a command published in the GitHub repository vladm3105/aidoc-flow-framework (17 stars, last pushed yesterday), licensed MIT. It adds 36 tokens to every session and 1,135 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 commands, from other repositories
setup
Interactive setup for YAML LSP development environment.
publish
Release a new package version — semver bump from commits, tag, registry publish, GitHub Release.
mpm-config
Manage Claude MPM configuration.
bump
Full dependency and toolchain bump — deps to latest major, Node pins, GitHub Actions, audit, validate, commit.
rebase
Rebase the current branch on main, a local branch, or a remote branch (with fetch).
model-config
Configure AI provider models for Claude Octopus workflows.