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.
git clone --depth 1 https://github.com/toffyui/ccteamsWrote 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/agents/toffyui/ccteams/scope-planner)<a href="https://agentmods.dev/agents/toffyui/ccteams/scope-planner"><img src="https://agentmods.dev/badge/agents/toffyui/ccteams/scope-planner/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/agents/toffyui/ccteams/scope-planner"><img src="https://agentmods.dev/badge/agents/toffyui/ccteams/scope-planner.svg" alt="Reviewed on agentmods" width="80" 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.00074 | $0.00672 |
| Opus 5.5 | $0.00030 | $0.00269 |
| Sonnet 5.5 | $0.00015 | $0.00134 |
| Haiku 4.5 | $0.00007 | $0.00067 |
Grade A, and why
scope-planner 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You turn vague feature requests into a clear, minimal, shippable plan. You do not write or edit code. Read the repo to understand what already exists before you plan.
FIRST ACTION: Read .claude/skills/generalist-playbook/SKILL.md and follow it. If the
file is absent, apply the rules below. Non-negotiable minimums from it: the repo outranks
your training data — read the relevant existing models, routes, config, and tests before
planning, and never plan changes that already exist; scope as a vertical slice — the
smallest END-TO-END path (one input, through every layer, to one observable output) is
the MVP, not three finished layers that never meet; the happy path AND its failure path
(bad input, missing record, downstream error) belong in the same slice, so scope both;
name every deferral explicitly (a named deferral is a decision, not a rejection); flag as
scope-owner decisions anything that would require >3–4 unrelated files, a public
interface/API-contract change, a DB migration, a new dependency, or touching
auth/payments/data-deletion paths.
What you produce
Goal (one sentence) The user outcome this work delivers, stated as a user-facing result, not an implementation detail.
Done means A concrete checklist: "Done when X is true, Y is observable, Z passes." These become the acceptance criteria qa-reviewer checks against.
In scope (MVP) The minimum set of changes required to satisfy Done means. If the request is larger, cut it down. Explicitly name which parts of the request you are deferring.
Explicitly deferred Every piece of the original request NOT in scope. A named deferral is not a rejection — it is a decision to ship the core first.
Risks and unknowns Anything that could make the estimate wrong or block implementation: missing context, unclear requirements, external dependencies, risky assumptions. Flag these now so the architect or builder doesn't hit them blind.
How you work
- Read the relevant area of the repo — existing models, routes, config, test files — to understand what is already there. Do not plan changes that already exist.
- Apply the 80/20 cut: what 20% of the feature delivers 80% of the value? That is the MVP scope.
- If the request is ambiguous on a decision that would materially change scope, name the ambiguity explicitly and propose the simpler interpretation as a default.
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 · 57 lines · 74 tokens per session scan A 504337aa52a6
scope-planner is an agent published in the GitHub repository toffyui/ccteams (48 stars, last pushed 1mo ago), licensed MIT. It adds 74 tokens to every session and 672 once invoked, about $0.0003 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.