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/kesteva/soloflow/configgit clone --depth 1 https://github.com/kesteva/soloflowWhat 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.00010 | $0.04278 |
| Opus 5 | $0.00005 | $0.02139 |
| Sonnet 5 | $0.00002 | $0.00856 |
| Haiku 4.5 | $0.00001 | $0.00428 |
Grade A, and why
config 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.
How it starts
The opening of the file, as written. The whole thing — 405 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/soloflow:config
Interactive walkthrough for every SoloFlow setting. Reads config/defaults.yaml,
shows current overrides from .soloflow/config.json, lets the user adjust
categories interactively, and writes the result back — preserving unknown keys.
See docs/CUSTOMIZATION.md#config-resolution for the
three-tier resolution recipe (.soloflow/config.json → defaults.yaml →
inline fallback) that every agent uses to read these values.
Step 1: Check initialization
Run test -d .soloflow via Bash. If it does not exist, report:
SoloFlow not initialized. Run `/soloflow:init` first to scaffold .soloflow/.
and stop.
Step 2: Load current config
- Run
test -e .soloflow/config.jsonvia Bash to check existence. - If present: use the Read tool (not
cat) to load.soloflow/config.jsonand parse into memory asconfig. - If absent: start with
config = {}.
Keep track of the original config state (e.g. original = deep-copy of config)
so the diff in Step 7 compares against disk, not against defaults.
Preserve every top-level key the command doesn't touch. Only the keys listed in "Managed keys" below are edited or removed by this command.
Step 3: Load defaults
Resolve $CLAUDE_PLUGIN_ROOT via a single Bash call (echo "$CLAUDE_PLUGIN_ROOT"),
then use the Read tool (not cat) on <plugin_root>/config/defaults.yaml
and parse into defaults. Used throughout to show the default value next to the
current value, and to compute the diff on exit.
If $CLAUDE_PLUGIN_ROOT is empty, fall back to the directory containing this
command file (two levels up from commands/config.md).
Step 4: Category picker (top level)
Loop the two-round picker until the user selects Done — exit.
Round 1 — Area
Use AskUserQuestion:
- Question: "Which area would you like to configure?"
- Header: "Area"
- Options:
"Behavior"— description: "Models, phases, tester mode""Operations"— description: "Limits, git, code review, verification, roadmap""Reset to defaults"— description: "Remove all overrides managed by this command""Done — exit"— description: "Review diff and write or discard"
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 · 405 lines · 10 tokens per session scan A 2b5ab8a02eb9
config is a command published in the GitHub repository kesteva/soloflow (40 stars, last pushed 3mo ago), licensed MIT. It adds 10 tokens to every session and 4,278 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-30.
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.
constitution
Create or update the project constitution from interactive or provided principle inputs.