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 skills add veryfront/veryfront-code --skill flywheelgit clone --depth 1 https://github.com/veryfront/veryfront-codeWrote 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/skills/veryfront/veryfront-code/flywheel)<a href="https://agentmods.dev/skills/veryfront/veryfront-code/flywheel"><img src="https://agentmods.dev/badge/skills/veryfront/veryfront-code/flywheel/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/skills/veryfront/veryfront-code/flywheel"><img src="https://agentmods.dev/badge/skills/veryfront/veryfront-code/flywheel.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.01475 |
| Opus 5.5 | $0.00010 | $0.00590 |
| Sonnet 5.5 | $0.00005 | $0.00295 |
| Haiku 4.5 | $0.00003 | $0.00147 |
Grade A, and why
flywheel 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 — 233 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Development Flywheel
Self-reinforcing development loop: Run → Observe → Fix → Verify → Repeat
┌─────────┐ ┌─────────┐ ┌─────────┐
│ RUN │────────▶│ OBSERVE │────────▶│ FIX │
└─────────┘ └─────────┘ └─────────┘
▲ │
│ ┌─────────┐ │
└──────────────│ VERIFY │◀─────────────┘
└─────────┘
Quick Start
# 1. Start server in background
Bash: deno task start &
# 2. Wait for ready
vf_wait_for_ready({ port: 8080 })
# 3. Open browser (Chrome MCP)
tabs_context_mcp() → tabs_create_mcp() → navigate({ url: "http://localhost:8080" })
# 4. Take baseline screenshot
computer({ action: "screenshot" })
# 5. Begin flywheel loop
Tools
Flywheel Core
| Tool | Purpose |
|---|---|
vf_wait_for_ready |
Poll until server accepts requests |
vf_get_flywheel_status |
Aggregated view: server + errors + logs + HMR |
vf_trigger_hmr |
Force browser refresh after code changes |
Server Errors & Logs
| Tool | Purpose |
|---|---|
vf_get_errors |
Compile, runtime, bundle errors |
vf_get_logs |
Server logs with filtering |
vf_clear_errors |
Clear error collector after fixing |
Browser (Chrome MCP)
| Tool | Purpose |
|---|---|
computer({ action: "screenshot" }) |
Visual verification |
read_console_messages |
Browser console errors |
read_network_requests |
Failed API calls |
Observe Loop
// Check all error sources in one call
const status = await vf_get_flywheel_status({ port: 8080 });
if (!status.server.running) {
// Server crashed - restart
}
if (status.errors.total > 0) {
// Compilation or runtime errors
// Get details: vf_get_errors()
}
if (status.logs.errors > 0) {
// Server logged errors
// Get details: vf_get_logs({ level: "error" })
}
// Browser side (Chrome MCP)
read_console_messages({ tabId, pattern: "error|Error" });
read_network_requests({ tabId, urlPattern: "/api/" });
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 · 233 lines · 26 tokens per session scan A da9b586f7236
flywheel is a skill published in the GitHub repository veryfront/veryfront-code (19 stars, last pushed today), licensed Apache-2.0. It adds 26 tokens to every session and 1,475 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-30.
Other skills, from other repositories
node-inspect-debugger
Debug Node.js via --inspect + Chrome DevTools Protocol.
investigate
A structured root-cause investigation method for software bugs. It moves from history and reproduction through tested hypotheses, a focused fix, verification, and a report.
bugfix-triage
A method for locating the cause of a bug before changing code, using a minimal reproduction and step-by-step narrowing of the failing input and code path.
javascript-sandbox
Best practices for using the clodex built-in JavaScript sandbox for browser debugging, fetched-data processing, attachments, and mini-app orchestration within its bundled capability boundary.
debug-failed-action
When your last vsact returned an unexpected result (NOTFOUND, no visible state change, suspected silent failure), run this skill with the action's pre-token. Pulls console errors, network failures, and current performance into one report.
CodeShuX__mockhunter
Audit a live web page to find mock data, hardcoded values, LLM-fabricated metrics, and broken endpoints. Opens the URL in Playwright, clicks every interactive element, traces every visible value to its actual source (DB/API/mock/LLM/hardcoded), and produces a markdown report. Use when the user wants a reality check on…