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/alifanov/darkflow/update-configgit clone --depth 1 https://github.com/alifanov/darkflowWrote 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/alifanov/darkflow/update-config)<a href="https://agentmods.dev/commands/alifanov/darkflow/update-config"><img src="https://agentmods.dev/badge/commands/alifanov/darkflow/update-config.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.00012 | $0.00847 |
| Opus 5 | $0.00006 | $0.00424 |
| Sonnet 5 | $0.00002 | $0.00169 |
| Haiku 4.5 | $0.00001 | $0.00085 |
Grade A, and why
update-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 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.
How it starts
The opening of the file, as written. The whole thing — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Usage
/darkflow:update-config ← interactive (ask for new values)
/darkflow:update-config lang=Russian
/darkflow:update-config branch=develop
/darkflow:update-config lang=Russian branch=develop
Step 1 — Read current settings
Run bash ~/.darkflow/get-config.sh to pull the latest project settings from the Web UI and refresh the project config at .darkflow.d/state/config.json (silently falls back to cache if the server is unreachable).
Read .darkflow.d/state/config.json from the project root. Extract language and branch values. If the file is missing, abort with an error.
Step 2 — Determine new values
Parse any lang and branch arguments passed to the command.
For any value not provided as an argument, ask the user interactively:
- Language: current value shown as default; accept free text (e.g. English, Russian, Spanish)
- Main branch: current value shown as default; accept free text (e.g. main, master, develop)
If the user presses Enter without input, keep the current value unchanged.
Step 3 — Update .darkflow.d/state/config.json
For each changed value, update the corresponding key in .darkflow.d/state/config.json in-place:
# macOS
sed -i '' "s/^language=.*/language=<NEW_LANG>/" .darkflow
sed -i '' "s/^branch=.*/branch=<NEW_BRANCH>/" .darkflow
# Linux
sed -i "s/^language=.*/language=<NEW_LANG>/" .darkflow
sed -i "s/^branch=.*/branch=<NEW_BRANCH>/" .darkflow
Step 4 — Update .darkflow.d/claude.md
Read .darkflow.d/claude.md. Update the two lines in-place:
# macOS
sed -i '' "s/^\*\*Language:\*\* .*/\*\*Language:\*\* <NEW_LANG> — use this language for tasks, comments, commit messages, and all agent-facing text./" .darkflow.d/claude.md
sed -i '' "s/^\*\*Main branch:\*\* .*/\*\*Main branch:\*\* \`<NEW_BRANCH>\`/" .darkflow.d/claude.md
# Linux
sed -i "s/^\*\*Language:\*\* .*/\*\*Language:\*\* <NEW_LANG> — use this language for tasks, comments, commit messages, and all agent-facing text./" .darkflow.d/claude.md
sed -i "s/^\*\*Main branch:\*\* .*/\*\*Main branch:\*\* \`<NEW_BRANCH>\`/" .darkflow.d/claude.md
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 · 83 lines · 0 tokens per session scan A 9623352c9de3
update-config is a command published in the GitHub repository alifanov/darkflow (2 stars, last pushed 4d ago), licensed MIT. It adds 12 tokens to every session and 847 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
checkpoint
Export, refresh, verify, or import a comprehensive cross-topic Project Knowledge Checkpoint for a repository, with privacy checks.
idea
Capture, research, shape, catalog, and explicitly promote Ideas into Projects through natural language.
portfolio
Show a read-only hub-wide portfolio of canonical Ideas and active Projects without duplicating topic-owned records.
story-implement
Implement a story through the Implement Phase. Stories must be fully designed with chunks before implementation.
planning
Feature roadmap and planning. Manage initiatives, concepts, open questions, and story creation from planning.
story-new
Create a new story. It lands in the backlog until assigned to a cycle.