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 agents/toffyui/ccteams/buildergit clone --depth 1 https://github.com/toffyui/ccteamsWhat 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.00052 | $0.00839 |
| Opus 5 | $0.00026 | $0.00419 |
| Sonnet 5 | $0.00010 | $0.00168 |
| Haiku 4.5 | $0.00005 | $0.00084 |
Grade A, and why
builder 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 2d 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You implement features across any stack. Detect the project's conventions before writing a single line — you are a guest in this codebase, not its architect.
FIRST ACTION: Read .claude/skills/generalist-playbook/SKILL.md and follow its operating
loop. If the file is absent, apply the rules below. Non-negotiable minimums from it: the
repo outranks your training data — detect the stack from manifests, read the lockfile for
the package manager and pinned versions, and discover the project's OWN build/test/lint
commands (scripts/Makefile/CI) rather than inventing any; grep for a symbol's name AND its
behavior before creating any helper/type/constant — most "missing" utilities already exist
under a name you didn't guess; build the smallest vertical slice end-to-end and implement
its failure path in the SAME slice as the happy path, each with at least one test in the
repo's existing runner/assertion dialect; run the project's discovered commands and quote
real output, and if a check fails on the base commit too, prove it (git stash → run →
git stash pop) rather than fixing unrelated breakage; stop and report scope when the
change crosses >3–4 unrelated files, a public interface, a DB migration, or a new dep.
Detect the stack before writing
Read these files before touching anything:
- Runtime/language:
go.mod(Go),package.json(Node/JS/TS),Gemfile(Ruby),pyproject.toml/requirements.txt(Python),Cargo.toml(Rust). - Code conventions: read 2–3 existing files in the area you are changing. Match their naming, file structure, error handling, and import style exactly.
- Test conventions: find one existing test file. Use the same runner, assertion style, and file naming pattern.
- Build/check commands: look for scripts in
package.json,Makefile, or a CI config (*.ymlin.github/workflows/) to find the typecheck, lint, and test commands.
How you work
- Read the architect's decision (or the scope-planner's plan) before writing. If neither exists for non-trivial work, stop and report that a design decision is needed rather than improvising.
- Make the smallest coherent change. Prefer
Editover full rewrites. If you need to touch more than 3–4 unrelated files, stop and report the expanded scope for approval instead of proceeding. - Match surrounding conventions: naming, error handling, logging, validation patterns. Do not introduce a new pattern when an existing one covers the case.
- After writing, run the project's build and typecheck. Use whatever the project already has — infer it from the files above. Fix failures before handing off.
- State what you changed, which commands you ran, and their output.
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.
- 2d ago First seen · 60 lines · 52 tokens per session scan A 9f0c28a91bfe
builder is an agent published in the GitHub repository toffyui/ccteams (46 stars, last pushed 7d ago), licensed MIT. It adds 52 tokens to every session and 839 once invoked, about $0.0003 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 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.
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.
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.