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/kazdenc/builder-skills/scopenpx skills add kazdenc/builder-skills --skill scopegit clone --depth 1 https://github.com/kazdenc/builder-skillsWrote 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/kazdenc/builder-skills/scope)<a href="https://agentmods.dev/skills/kazdenc/builder-skills/scope"><img src="https://agentmods.dev/badge/skills/kazdenc/builder-skills/scope.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.00074 | $0.01278 |
| Opus 5 | $0.00037 | $0.00639 |
| Sonnet 5 | $0.00015 | $0.00256 |
| Haiku 4.5 | $0.00007 | $0.00128 |
Grade A, and why
scope 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 4d 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cut scope to ship something meaningful within constraints. Favor a complete small thing over an incomplete big thing.
Step 1: List All Requirements
Collect every feature, requirement, and "wouldn't it be nice if" into a flat list. If the user provided a PRD or feature set, extract items from it. If not, ask.
Each item should be a concrete, shippable unit — not a theme. Break down anything vague ("improve onboarding") into specific deliverables ("add welcome wizard", "send day-1 email", "add progress indicator").
Step 2: Apply the Core Job Test
For each item, ask: "If we shipped without this, would the core job still get done?"
- Yes → Nice-to-have. Move it down.
- No → Must-have candidate. Keep it.
Be honest. "Get done" means the user can complete the primary task, even if it's manual, ugly, or slow. A to-do app without drag-and-drop reordering still lets people track tasks. A to-do app without the ability to add tasks does not.
Step 3: Categorize into Tiers
Sort every item into one of four tiers:
| Tier | Label | Criteria | Ships in |
|---|---|---|---|
| T0 | Must Ship (MVP) | Without this, the product doesn't work or the core job can't be completed | Current timeline |
| T1 | Should Ship | Makes the experience significantly better but isn't blocking the core job | v1.1 / next cycle |
| T2 | Could Ship | Genuine value, but the product is viable and useful without it | Future |
| T3 | Won't Ship | Out of scope, wrong timing, low value, or conflicts with focus | Never (for now) |
Present the result as a table:
| Tier | Item | Rationale |
|------|------|-----------|
| T0 | ... | Core job requires it: [why] |
| T1 | ... | Improves [what], but core flow works without it |
| T2 | ... | Nice for [who], revisit after launch |
| T3 | ... | Out of scope because [reason] |
Step 4: Validate the MVP
Check that the T0 set is coherent:
- Does it complete one whole job? Users should be able to go from start to done, even if the path is rough. Partial flows are worse than missing features.
- Is it scoped to one persona? Serving one user well beats serving three users poorly. If T0 tries to cover multiple personas, pick the most important one and move the rest to T1.
- Can it ship within the timeline? If T0 alone exceeds the timeline, cut further. Ask: "Which of these must-haves is the most must-have?"
- Is there a simpler version of any T0 item? "Full search with filters" might become "basic text search." "Role-based permissions" might become "admin/member only." Reduce the scope within must-haves, not just between them.
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.
- 4d ago First seen · 96 lines · 74 tokens per session scan A 84db710c5410
scope is a skill published in the GitHub repository kazdenc/builder-skills (44 stars, last pushed 5mo ago), licensed MIT. It adds 74 tokens to every session and 1,278 once invoked, about $0.0004 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-30.
Other skills, from other repositories
migrate-radix-to-base
Migrates React projects and components from Radix UI to Base UI. Use when asked to migrate from radix, move to base-ui, convert radix primitives, or switch a shadcn project's base library. Handles single components ("migrate accordion") and whole projects.
copilotkit-upgrade
Use when migrating a CopilotKit v1 application to v2 -- updating package imports, replacing deprecated hooks and components, switching from GraphQL runtime to AG-UI protocol runtime, and resolving breaking API changes.
non-json-content-types
Handle FormData, file uploads, Blob, Uint8Array, and ReadableStream inputs in tRPC mutations. Use octetInputParser from @trpc/server/http for binary data. Route non-JSON requests with splitLink and isNonJsonSerializable() from @trpc/client. FormData and binary inputs only work with mutations (POST).
saas-builder
Clone, verify, map, and build on top of ixartz/SaaS-Boilerplate for a user's SaaS idea. Use when a user wants to reuse SaaS Boilerplate, evaluate how their product fits it, or build product-specific pages, database schema, roles, permissions, MVP features, and launch scope on top of the boilerplate.
trigger-authoring-tasks
Covers writing backend Trigger.dev tasks with @trigger.dev/sdk: defining task() and schemaTask(), the run function and its ctx, retries, waits, queues and concurrency, idempotency keys, run metadata, logging, triggering other tasks (and the Result shape), scheduled/cron tasks, and the essentials of trigger.config.ts.…
rebase-themes
Rebase all theme- branches onto main, resolving conflicts while preserving each theme's visual identity. Force-pushes directly to theme branches with backup tags. Run as a scheduled task or one-off.