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 skills/t1djani/servo/servo-flownpx skills add t1djani/servo --skill servo-flowgit clone --depth 1 https://github.com/t1djani/servoWrote 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/t1djani/servo/servo-flow)<a href="https://agentmods.dev/skills/t1djani/servo/servo-flow"><img src="https://agentmods.dev/badge/skills/t1djani/servo/servo-flow.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.00040 | $0.00893 |
| Opus 5 | $0.00020 | $0.00447 |
| Sonnet 5 | $0.00008 | $0.00179 |
| Haiku 4.5 | $0.00004 | $0.00089 |
Grade A, and why
servo-flow 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 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.
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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
servo-flow
servo runs a piece of work as a feedback loop, not a straight line. Each phase boundary re-grounds against the project's oracles and gates the artifact against ground truth before moving on. The premise: the agent is a high-gain actuator with no damping — left alone it converges fast and confidently, even on the wrong answer. The phases supply the damping.
The phases
scan-project → gather-context → expert-panel → shape-spec ⟂gate→ seal-plan ⟂gate→ execute ⟂scope-watch ⟂gate→ close-the-books
| Phase | Skill | When |
|---|---|---|
| Map the project | scan-project |
once per project: discover the manifest (oracles + experts) |
| Ground | gather-context |
at the start, and again at every phase boundary |
| Diverge | expert-panel |
only for decisions with no ground truth yet (the real forks) |
| Spec | shape-spec → servo-gate |
shape the spec, then gate it against invariants/scope |
| Plan | seal-plan → servo-gate |
write a closed plan, then gate it against the spec |
| Execute | (TDD) + scope-watch → servo-gate |
build, watching for drift, gating the diff |
| Done | close-the-books |
reconcile every criterion and invariant |
Two things that hold across all phases
-
The human is a seat at the table, not ceremony. Always the client (nothing ships without their OK). Often the CEO (they carry the intent). Sometimes also an expert (they contribute, and get challenged like any expert). Capture their input richly, in batches — then pressure-test it.
-
Verification only counts if it injects ground truth the producer did not have. Every gate names an oracle. A check that re-reads the artifact with the same context that wrote it is theater. Skip it.
Show the work — keep a live checklist
The phases are only damping if the human can see them happen. At the start of a servo run, open a TodoWrite checklist with one item per phase you intend to run (skip the ones that don't apply), and walk it: mark a phase in_progress when you enter it, completed when its gate passes. When a phase fans out, expand it into sub-items — one todo per expert in expert-panel, one todo per task when executing a sealed plan, one per verifier in a multi-gate. The checklist is the visible spine of the run; never do a multi-phase servo run as a silent block of work.
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 · 48 lines · 40 tokens per session scan A c739f627c022
servo-flow is a skill published in the GitHub repository t1djani/servo (1 stars, last pushed 2mo ago), licensed MIT. It adds 40 tokens to every session and 893 once invoked, about $0.0002 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 skills, from other repositories
quiz-me
Quiz the user on root cause and intended fix BEFORE writing any non-trivial code, then verify comprehension of every change after. Use when the user asks for a bug fix, refactor, or feature and wants to stay technically sharp instead of vibe-coding. Also use when the user says "quiz me", "don't let me vibe code", or…
website-deploy-builder
Plan what to build on Website Deploy (simple-host.app). Helps a user decide whether their idea fits the static + light-backend model, maps it to concrete patterns (shared JSON state with atomic ops, append-only collections, private/password-locked pages on a custom domain, drop-in comments/feedback widgets…
craft
Engineering standards for any code work on any stack — writing production code, slicing and reviewing PRs, authoring tests, running gates, merging, and running agent fleets. Load before touching code, not after review flags it.
connect-domain
Connect a user's own custom domain (subdomain e.g. recipes.brand.com via CNAME, or apex e.g. brand.com via A record) to a site already deployed on simple-host. Use when a user wants their site served from their own domain with automatic HTTPS, or wants a private/password-protected site (privacy is offered only on a…
personal-voice-capture
Use when a user wants an agent to learn, encode, or improve their personal writing voice as a reusable skill through source-text ingestion and iterative calibration edits.
demo-video-factory
Generate a custom 26s product-demo video from any SaaS URL — brand-matched scenes, a recreated product-UI "wow" scene, real screenshots, and a soundtrack. Use whenever the user wants a demo, promo, launch, or marketing video for a website or product.