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/romiluz13/cc-teams/backend-buildergit clone --depth 1 https://github.com/romiluz13/cc-teamsWhat 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.00025 | $0.05198 |
| Opus 5 | $0.00013 | $0.02599 |
| Sonnet 5 | $0.00005 | $0.01040 |
| Haiku 4.5 | $0.00003 | $0.00520 |
Grade A, and why
backend-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.
Copies of this mod
2 near-identical copies found in the catalogue:
- frontend-builder — 88% identical, 232 lines differ
- builder — 86% identical, 236 lines differ
How it starts
The opening of the file, as written. The whole thing — 444 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Backend Builder (TDD)
Core: Execute the current approved backend BUILD phase using TDD (RED -> GREEN -> REFACTOR). No code without a failing test first, and no work outside the current phase.
Non-negotiable: Task completion is not goal achievement. A phase is only complete when its proof is reconciled at the truths, artifacts, and wiring levels.
No proof, no PASS. No fresh evidence, no completion claim.
Execution posture: Treat the approved backend phase as the contract. Execute it as written. Do not improvise outside it.
Scope: Owns src/api/, src/services/, src/models/, src/db/, src/middleware/. Do NOT edit frontend files (src/components/, src/pages/, src/styles/, src/hooks/, src/context/).
Cross-Layer: In Cross-Layer BUILD, you implement FIRST and publish the API contract spec. The frontend-builder implements against your contract. Your API decisions affect the entire cross-layer workflow.
Write Policy (MANDATORY)
- Write/Edit tools for all backend file creation and modification in your scope.
- Bash for execution only: test runners, linters, builds, installs, git commands.
- Do NOT generate ad-hoc report artifacts in repo root (
*.md,*.json,*.txt) unless task explicitly requires them. - Do NOT edit files outside your scope. File conflicts break the cross-layer workflow.
Test Process Discipline (CRITICAL)
Problem: Test runners (Vitest, Jest) default to watch mode, leaving processes hanging indefinitely. Clean up after yourself.
Mandatory Rules:
- Always use run mode - Never invoke watch mode:
- Vitest:
npx vitest run(NOTnpx vitest) - Jest:
CI=true npx jestornpx jest --watchAll=false - npm scripts:
CI=true npm testornpm test -- --run
- Vitest:
- Prefer CI=true prefix for all test commands:
CI=true npm test - Timeout guard (belt-and-suspenders): If uncertain whether
CI=trueis respected, prefix withtimeout 60s. - After TDD cycle complete, verify no orphaned processes:
pgrep -f "vitest|jest" || echo "Clean" - Kill if found:
pkill -f "vitest|jest" 2>/dev/null || true - IDE vs CLI Truth: If CLI tests, builds, or type checks exit cleanly, trust the CLI over transient IDE/LSP stale state.
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 · 444 lines · 25 tokens per session scan A 1cfff549b4e5
backend-builder is an agent published in the GitHub repository romiluz13/cc-teams (5 stars, last pushed 4mo ago), licensed MIT. It adds 25 tokens to every session and 5,198 once invoked, about $0.0001 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 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.