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/web-vitalsgit 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/web-vitals)<a href="https://agentmods.dev/commands/alifanov/darkflow/web-vitals"><img src="https://agentmods.dev/badge/commands/alifanov/darkflow/web-vitals.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.00025 | $0.02091 |
| Opus 5 | $0.00013 | $0.01045 |
| Sonnet 5 | $0.00005 | $0.00418 |
| Haiku 4.5 | $0.00003 | $0.00209 |
Grade A, and why
web-vitals 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 5d 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 — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Measure this project's Core Web Vitals by running Lighthouse locally against its URL (mobile emulation), compare the lab metrics against Google's thresholds, and file a task when any metric lands in the 'poor' band. This tracks user-facing performance (LCP, CLS, TBT, FCP, TTFB) over time and turns regressions into actionable work for fix-issues. No API key and no external service — Lighthouse drives a local headless Chrome.
This is an analysis routine: healthy runs only write a snapshot; runs with a "poor" metric file a normal (human-triaged) task — a slow page is not an emergency, so unlike uptime-check these tasks are not auto-approved.
Lab, not field. Local Lighthouse produces lab data (a single synthetic run on this machine), not real-user field data. There is no lab INP — TBT (Total Blocking Time) is used as its proxy. Because it's local Chrome, it can measure
localhost/staging/private URLs too, not just public ones.
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 measure
If domain is set, use it. Otherwise auto-discover the production URL the same way uptime-check does (first match wins): Coolify FQDN, vercel.json / .vercel/project.json, netlify.toml, CNAME, package.json → homepage, or a production URL stated in README.md / docs/. If found, persist it:
grep -q "^site_url=" .darkflow || echo "site_url=<discovered-url>" >> .darkflow
The URL just has to be reachable from this machine (public, staging, or localhost all work). If no URL can be determined at all, do not create a task — output web-vitals: no site_url — skipping and write a snapshot (Step 5) noting the target is unknown. Done.
Step 3 — Run Lighthouse locally
Lighthouse needs a Chrome/Chromium binary on this machine (chrome-launcher auto-detects it). Run the mobile preset (Lighthouse's default form factor — mobile is what Google ranks on):
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.
- 5d ago First seen · 152 lines · 25 tokens per session scan A ceae76f2ffab
web-vitals is a command published in the GitHub repository alifanov/darkflow (2 stars, last pushed 5d ago), licensed MIT. It adds 25 tokens to every session and 2,091 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
project
Generate project documentation (product.md, structure.md, tech.md, codemaps/).
toh-help
Display all Toh Framework commands and quick usage guide.
new
Plan mode. Generates a plan for a feature based on a description.
feature
Create a feature specification using spec-driven development.
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.
fix-issue
!gh issue view $ARGUMENTS 2>/dev/null || echo "Could not fetch issue $ARGUMENTS".