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/builder)<a href="https://agentmods.dev/agents/toffyui/ccteams/builder"><img src="https://agentmods.dev/badge/agents/toffyui/ccteams/builder/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/builder"><img src="https://agentmods.dev/badge/agents/toffyui/ccteams/builder.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.00052 | $0.00839 |
| Opus 5.5 | $0.00021 | $0.00336 |
| Sonnet 5.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 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 — 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.
- 1mo ago First seen · 60 lines · 52 tokens per session scan A 9f0c28a91bfe
builder is an agent published in the GitHub repository toffyui/ccteams (48 stars, last pushed 1mo ago), licensed MIT. It adds 52 tokens to every session and 839 once invoked, about $0.0002 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
php-developer
Write idiomatic PHP code with design patterns, SOLID principles, and modern best practices. Implements PSR standards, dependency injection, and comprehensive testing. Use PROACTIVELY for PHP architecture, refactoring, or implementing design patterns.
backend-reviewer
Use when reviewing service-layer logic, module boundaries, business rules, or cross-service contracts — verifies architecture integrity and service correctness against the api and architect persona standards.
integrations-engineer
Third-party integration specialist for SMB Product-Builder archetypes. Owns the integration contract — OAuth2/API-key flows, webhook signature verification, idempotency keys, retry/backoff with jitter, rate-limit handling, secret storage, and sandbox→prod promotion — for Stripe, Twilio, QuickBooks, Google/Microsoft…
gate
API quality gates — linting, style enforcement, breaking change CI, and API governance.
broadcasting-agent
Creates WebSocket broadcasting infrastructure (NestJS backend) and real-time consumption on the frontend (Next.js or React). Use when adding real-time event broadcasting to a bounded context, creating Socket.IO gateways, or implementing frontend event listeners. Dispatched after infrastructure layer is complete.
dotnet-architecture-reviewer
Reviews a .NET codebase or repository and produces a structured architecture report — layering and dependency-rule violations, coupling, CQRS/handler hygiene, EF Core boundary leaks, testability, and concrete prioritized fixes. Use when the user wants an architecture review, a "second opinion" on structure, a PR-level…