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/scope-watchnpx skills add t1djani/servo --skill scope-watchgit 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/scope-watch)<a href="https://agentmods.dev/skills/t1djani/servo/scope-watch"><img src="https://agentmods.dev/badge/skills/t1djani/servo/scope-watch.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.00045 | $0.00429 |
| Opus 5 | $0.00023 | $0.00215 |
| Sonnet 5 | $0.00009 | $0.00086 |
| Haiku 4.5 | $0.00005 | $0.00043 |
Grade A, and why
scope-watch 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.
What it actually says
scope-watch
Hold the work to its intent while it is being built, not after. A human implementer keeps the goal in their head for hours; an agent loses it as the context fills with implementation detail and starts solving adjacent problems it was never asked to. This skill catches that drift in flight.
What drift looks like
- Building something the issue did not ask for ("while I'm here, I'll also…").
- Quietly widening the change beyond the plan's scope.
- Solving a harder, more interesting problem than the one assigned.
- Touching files or systems the scope did not name.
Procedure
-
Anchor on the scope oracle. From the manifest, read the
scopesource for this work (the issue / the spec's scope section). That is the intent: what this work is, and what it is not. -
Diff at each meaningful step. As you implement, periodically compare the work in progress against that intent. Cheap question: does this change still serve the stated scope, or did it grow a second purpose?
-
On suspected drift, stop the line. This is the andon cord: stopping is cheap and expected; pushing through a scope smell is the failure. Surface the drift — "this step is adding X, which is outside the issue's scope" — and decide explicitly: is X in scope (update the scope oracle deliberately) or out (drop it)?
-
Never widen scope silently. If the work genuinely needs more than the issue covers, that is a decision for the human (CEO/client), not a default the agent takes mid-implementation.
Rule
An agent that pushes through a scope smell to "be helpful" is the exact failure this skill exists to stop. Stopping to check is the cheap, correct move.
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 · 30 lines · 45 tokens per session scan A 589e8ccc8f92
scope-watch is a skill published in the GitHub repository t1djani/servo (1 stars, last pushed 2mo ago), licensed MIT. It adds 45 tokens to every session and 429 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.