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/submit-to-directories)<a href="https://agentmods.dev/commands/alifanov/darkflow/submit-to-directories"><img src="https://agentmods.dev/badge/commands/alifanov/darkflow/submit-to-directories/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/submit-to-directories"><img src="https://agentmods.dev/badge/commands/alifanov/darkflow/submit-to-directories.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.00027 | $0.01603 |
| Opus 5.5 | $0.00011 | $0.00641 |
| Sonnet 5.5 | $0.00005 | $0.00321 |
| Haiku 4.5 | $0.00003 | $0.00160 |
Grade A, and why
submit-to-directories 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 1mo 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 — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Backlinks from product directories are the one off-page lever that does not need anyone else's
permission — a form, a description, a screenshot. The list of forms is fixed and versioned
(~/.darkflow/directories.csv); what changes per project is which of them fit and which are
already done.
This command walks that list in a real browser and submits. It is not an audit: it acts.
Manual only. No schedule, no catalog entry, no worker dispatch. Directory forms mean accounts, captchas and email confirmations — a human is in the loop by definition.
Money and identity are never spent silently. Two hard rules, no exceptions:
- Never pay. A paid listing is reported as a recommendation with its price. Ask, never buy.
- Never invent an identity. Accounts are created with the project's real email only. No throwaway addresses, no made-up company details, no fabricated MRR, no invented reviews.
Step 1 — Read project config
Load the project config (contract in .darkflow.d/claude.md → Project config). Uses:
language, domain.
No domain → nothing to submit. Say so and stop.
Step 2 — Build the submission kit
Every form asks for the same eight things. Assemble them once, before opening a browser, so the same words land everywhere:
| Field | Where it comes from |
|---|---|
| Name | project name |
| Tagline (≤60 chars) | docs/state/product/positioning.md |
| Short description (≤160) | positioning + the site's meta description |
| Long description (2–4 ¶) | docs/state/product/product.md |
| Categories / tags | the catalog's category column + what the form offers |
| Pricing | docs/state/product/pricing.md |
| Logo + 2–3 screenshots | public/, or take them from the live site with the browser |
| Submission URL | domain + UTM (below) |
Missing product docs → derive from the live site, and say in the report that the copy was derived rather than read. Never invent a claim the product does not make about itself.
UTM on every submission, so the directories are separable in analytics later:
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.
- 1mo ago First seen · 144 lines · 27 tokens per session scan A 584bac6a4529
submit-to-directories is a command published in the GitHub repository alifanov/darkflow (4 stars, last pushed yesterday), licensed MIT. It adds 27 tokens to every session and 1,603 once invoked, about $0.0001 per session on Opus 5.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
qawolf-cli
Manage QA Wolf through the qawolf CLI. Use when asked to create, update, or list coverage requests, bug reports, or maintenance reports; start a run of flows or tags on the QA Wolf platform or read a run's results; list, set, or delete environment variables; manage environments, flows, or tags; run or list flows…
restaurant-snipe
Schedule a future reservation to book at the exact release time (e.g. 10am sharp when Resy slots open).
local
Command "local" from getsentry/toolkit, covering sentry local run, browser ui, endpoints, tail output and agent tracing.
auth
Bare sentry auth logs in when you're logged out and shows status when you're already authenticated. sentry auth login always starts the login flow.
debug-files
Command "debug-files" from getsentry/toolkit, covering notes on find and important notes.
react-native
Command "react-native" from getsentry/toolkit, covering xcode build step (react-native xcode) and important notes.