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/uptime-checkgit 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/uptime-check)<a href="https://agentmods.dev/commands/alifanov/darkflow/uptime-check"><img src="https://agentmods.dev/badge/commands/alifanov/darkflow/uptime-check.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.1 | $0.00026 | $0.01916 |
| Opus 5 | $0.00013 | $0.00958 |
| Sonnet 5 | $0.00005 | $0.00383 |
| Haiku 4.5 | $0.00003 | $0.00192 |
Grade A, and why
uptime-check 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 6d 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.
> **Note — cheap pre-flight.** The dispatcher (`darkflow-run.sh`) runs a fast bash `curl` probe *before* launching this agent. On the common happy path (site returns 2xx with a real body) it writes the snapshot + metrics How it starts
The opening of the file, as written. The whole thing — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Check whether this project's website is actually up: resolve DNS, hit the URL, verify the HTTP status is healthy, and confirm the page really loads (not a blank/error/maintenance page). If the site is down or broken, create an auto-approved critical-priority task so fix-issues picks it up immediately and restores it.
This is an active health check: when the site is healthy it does nothing but write a snapshot. When the site is broken it files a critical, auto-approved task describing exactly what failed (DNS, HTTP status, or empty/error body) so the fix can start without waiting for human triage.
Note — cheap pre-flight. The dispatcher (
darkflow-run.sh) runs a fast bashcurlprobe before launching this agent. On the common happy path (site returns 2xx with a real body) it writes the snapshot + metrics itself and skips this agent entirely — so on healthy runs you are not invoked at all. This agent runs only when the probe finds the site down/broken or can't decide (nosite_url, DNS failure, etc.). When you are invoked, perform the full check below from scratch (the probe is only a coarse filter) and file the issue.
Step 1 — Read project config
Load the project config (contract in .darkflow.d/claude.md → Project config). Uses: domain, language.
Step 2 — Resolve the URL to check
If domain is set, use it. Otherwise, auto-discover the production URL from the project (first match wins):
- Coolify:
coolify app listthen the app's FQDN/domain (if thecoolifyCLI is configured) vercel.json/.vercel/project.jsonproduction domainnetlify.tomlsite URLCNAMEfile (GitHub Pages custom domain)package.json→homepage- A production URL stated in
README.mdordocs/
If a URL is found this way, persist it for next time:
grep -q "^site_url=" .darkflow || echo "site_url=<discovered-url>" >> .darkflow
If no URL can be determined at all, do not create an issue. Output uptime-check: no site_url configured and none discoverable — skipping and still write the snapshot (Step 5) noting that the target is unknown. Done.
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.
- 6d ago First seen · 150 lines · 26 tokens per session scan A c7716922cea4
uptime-check is a command published in the GitHub repository alifanov/darkflow (2 stars, last pushed 6d ago), licensed MIT. It adds 26 tokens to every session and 1,916 once invoked, about $0.0001 per session on Opus 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
project
Generate project documentation (product.md, structure.md, tech.md, codemaps/).
toh-help
Display all Toh Framework commands and quick usage guide.
deep-audit.skeleton
Aciklama: Bu bolum Bootstrap tarafindan manifest verileriyle doldurulur. Gerekli manifest alanlari: project.description, stack.primary, project.structure, project.subprojects, stack.orm, stack.authmethod Ornek cikti.
rev
Invoke Code Reviewer for code quality, security, requirements validation, and best practices review.
session-log
Create or append a session log entry.
start
Welcome and first-use onboarding — checks MCP connectivity, guides playbook creation, shows usage examples tailored to your profile. Replaces /setup.