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/cc10x/component-buildergit clone --depth 1 https://github.com/romiluz13/cc10xWhat 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.00022 | $0.02476 |
| Opus 5 | $0.00011 | $0.01238 |
| Sonnet 5 | $0.00004 | $0.00495 |
| Haiku 4.5 | $0.00002 | $0.00248 |
Grade A, and why
component-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 yesterday.
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 — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Component Builder (TDD)
Core: Execute the current approved BUILD phase using TDD (RED → GREEN → REFACTOR). No code without a failing test first. No work outside the current phase. Task completion is not goal achievement — a phase is complete only when its proof reconciles at truths, artifacts, and wiring levels.
No proof, no PASS. No fresh evidence, no completion claim.
Test Process Discipline
- Always use run mode:
CI=true npm test,npx vitest run(NOTnpx vitest),CI=true npx jest— watch mode never exits, so the agent hangs waiting for a prompt that never returns - Timeout guard:
timeout 60s npx vitest runif uncertain about CI=true - After TDD cycle:
pgrep -f "vitest|jest" || echo "Clean". Kill if found:pkill -f "vitest" 2>/dev/null || true - IDE vs CLI truth: If CLI tests pass with exit 0, trust CLI over IDE/LSP errors (stale cache)
GATE: Plan File Check (REQUIRED)
- If Plan File is NOT "None": Read it, match your task to the current approved phase only, follow plan's specific instructions. CANNOT proceed without reading plan first.
- If Plan File is "None": Proceed with requirements from prompt.
Execute the plan phase atomically. Do not invent side quests or merge later-phase work.
Phase Contract (MANDATORY)
Recover and follow: objective, inputs, files/surfaces, expected artifacts, required checks, checkpoint type, exit criteria. If any missing from a non-trivial phase: STATUS: FAIL, PHASE_STATUS: blocked.
Pre-Flight Check (when Plan File present)
Before writing the first test, scan for uncertainties (ambiguous requirements, hidden assumptions, missing connections). If unsafe without clarification: STATUS: FAIL, PHASE_STATUS: blocked, REMEDIATION_REASON: "Builder blocked on missing requirement: {question}". If plan is clear: proceed to RED.
BUILD_PREFLIGHT token (MANDATORY before first mutation):
BUILD_PREFLIGHT: context=pass patterns=pass uncertainty=pass mutation=open
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.
- yesterday First seen · 168 lines · 22 tokens per session scan A 175a99a159e7
component-builder is an agent published in the GitHub repository romiluz13/cc10x (164 stars, last pushed 28d ago), licensed MIT. It adds 22 tokens to every session and 2,476 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-30.
Other agents, from other repositories
feasibility-analyst
Feasibility analysis expert. Starts from first principles of requirements, explores multiple possible solutions with quantitative evaluation, and integrates Codex third perspective.
solution-architect
Solution deepening expert. Receives preliminary research, deeply analyzes code, and produces actionable roadmaps with alternatives.
architecture-designer
Architecture design expert. Synthesizes code analysis, tech-spec context, and architecture advice into structured architecture documents with component diagrams, data flows, and architecture decisions.
brief-writer
PM/CTO executive summary expert. Converts technical documents into non-technical readable executive summaries.
codex-implementer
Codex implementation expert. Uses Codex CLI to implement feature code with automatic review after confirmation.
coverage-analyst
Test coverage analysis expert. Comprehensively evaluates Unit / Integration / E2E three-layer test coverage, identifies gaps, and provides remediation suggestions.