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.
git 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/install)<a href="https://agentmods.dev/commands/alifanov/darkflow/install"><img src="https://agentmods.dev/badge/commands/alifanov/darkflow/install/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/alifanov/darkflow/install"><img src="https://agentmods.dev/badge/commands/alifanov/darkflow/install.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00015 | $0.00334 |
| Opus 5.5 | $0.00006 | $0.00134 |
| Sonnet 5.5 | $0.00003 | $0.00067 |
| Haiku 4.5 | $0.00002 | $0.00033 |
Grade A, and why
install scanned grade A with 1 finding 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 14d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
bash <(curl -fsSL https://raw.githubusercontent.com/alifanov/darkflow/main/install.sh) What it actually says
Run the Dark Flow installer — works for fresh projects and existing ones alike:
bash <(curl -fsSL https://raw.githubusercontent.com/alifanov/darkflow/main/install.sh)
Options:
--all— enable all optional modules non-interactively-y / --yes— accept defaults with no prompts--dry-run— preview changes without applying--force— re-apply all templates, skip version check
After the installer finishes, read .darkflow.d/state/config.json if it exists and extract language (default: English) — use it for all user-facing messages below.
Check for stale slash commands that are no longer part of Dark Flow:
- Fetch the current canonical command list from the Dark Flow repo:
curl -fsSL https://api.github.com/repos/alifanov/darkflow/contents/templates/.claude/commands/darkflow \ | grep '"name"' | grep '\.md"' | sed 's/.*"name": "\(.*\)".*/\1/' - List all files currently in
~/.claude/commands/darkflow/. - If there are any local files not in the canonical list, show them to the user and ask whether to delete them (they are likely leftovers from an older Dark Flow version).
- Delete only the files the user confirms.
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.
- 14d ago Changed 7cdb8229e054
- 1mo ago First seen · 30 lines · 15 tokens per session scan A 24e554f81ca2
install is a command published in the GitHub repository alifanov/darkflow (4 stars, last pushed yesterday), licensed MIT. It adds 15 tokens to every session and 334 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
local
Command "local" from getsentry/toolkit, covering examples, start the server and tail events (default), run your app with the local server auto-enabled, use a custom port and only show errors and logs (filter out transactions).
debug-files
Command "debug-files" from getsentry/toolkit, covering examples, inspect a debug information file (auto-detects the format), bundle jvm sources with a debug id, exclude additional directories and output as json.
feedback
Modern User Feedback is stored as Feedback issues. The command always limits issue searches to issue.category:feedback; it does not use the legacy User Reports API.
auth
Command "auth" from getsentry/toolkit, covering examples, oauth login (recommended), token login, read-only oauth login and custom oauth scopes.
api
Endpoints are relative to /api/0/ — the prefix is added automatically. Absolute HTTP(S) Sentry URLs also work; their origin is validated against your authenticated host.
init
Authentication: Interactive runs start the OAuth login flow automatically when credentials are missing or the stored session has expired. Non-interactive and CI runs must authenticate before running sentry init.