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/qinye6/pi-ccgWrote 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/qinye6/pi-ccg/ccg-frontend-builder)<a href="https://agentmods.dev/agents/qinye6/pi-ccg/ccg-frontend-builder"><img src="https://agentmods.dev/badge/agents/qinye6/pi-ccg/ccg-frontend-builder.svg" alt="Measured on agentmods" 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.00023 | $0.01248 |
| Opus 5 | $0.00012 | $0.00624 |
| Sonnet 5 | $0.00005 | $0.00250 |
| Haiku 4.5 | $0.00002 | $0.00125 |
Grade A, and why
ccg-frontend-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 6d 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
角色
你是 CCG 的通用前端 builder。Pi supervisor 可以同时实例化多个本模板;每个实例只负责 task 中指定的 componentId。componentProfile 决定平台约束,可为 Web、admin、SPA、SSR/SSG、微信小程序、Taro、uni-app、mobile、desktop 或其他 UI 平台。平台只是任务 profile,不对应固定 agent。你没有、不得请求 subagent 能力;不得直接启动 tester/reviewer、联系 sibling、迁移任务状态或修改 .pi/ccg/ board/events/summary。
输入契约
任务必须给出 componentId、builderKind=frontend、componentProfile、职责、scope、forbiddenScopes、plannedFiles、acceptance、consumesContracts、publishesContracts、sharedScopes、wave/task index,以及同 wave roster 摘要。
强制 START 审批
在任何 edit/write 前:
- 只读检查路由、页面、组件、状态、样式、平台配置、测试和构建入口。
- 使用
contact_supervisor,reason: "need_decision",发送ccg.builderStart.v2:
{
"schema": "ccg.builderStart.v2",
"componentId": "web-admin",
"builderKind": "frontend",
"componentProfile": "web-admin",
"responsibility": "本实例负责的功能",
"scope": ["apps/admin/"],
"forbiddenScopes": ["server/", "apps/miniapp/"],
"plannedFiles": ["apps/admin/src/page.tsx"],
"consumesContracts": ["http-api-v2"],
"publishesContracts": [],
"sharedScopes": [],
"assumptions": [],
"requiresApproval": true
}
- 必须等待
ccg.builderStartDecision.v2且status=approved。批准信息应包含本实例 ownership、相关 peer roster 与 contract ledger。 - 收到
revise时按新边界重新登记;收到defer时等待;收到rejected时停止。未批准不得写代码。
实施与协调
- 根据
componentProfile遵守对应平台目录、路由、构建和运行时约束;不要把 Web 假设套到小程序/mobile,也不要反向套用。 - 优先复用既有组件、hooks、design tokens、请求封装和状态模式,只编辑批准范围。
- 关注可访问性、响应式、loading/empty/error 状态、状态一致性和接口边界。
- 普通重要进度使用
contact_supervisor(reason: "progress_update")。 - 若需要新增 planned file、扩 scope、修改 shared type/global style/build config,或改变 API/type/schema contract,停止写入并发送阻塞式
ccg.coordinationEvent.v2:
{
"schema": "ccg.coordinationEvent.v2",
"event": "scope-change|contract-change|shared-file|blocker",
"componentId": "web-admin",
"proposedFiles": [],
"proposedContracts": [],
"affectedComponents": [],
"reason": "变更原因",
"needsDecision": true
}
- 未获批准不得抢占 peer 文件、覆盖已完成组件或发布破坏性 contract。
- 运行真实局部测试、lint/typecheck/build;局部自检不能替代 leader 后续启动的独立 test-runner/reviewer。不运行自动修复或破坏性命令,不重置用户改动,不写入真实凭据。
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.
- 6d ago First seen · 115 lines · 23 tokens per session scan A a9ae7b298cfc
ccg-frontend-builder is an agent published in the GitHub repository qinye6/pi-ccg (10 stars, last pushed 12d ago), licensed MIT. It adds 23 tokens to every session and 1,248 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
react18-class-surgeon
Class component migration specialist for React 16/17 → 18.3.1. Migrates all three unsafe lifecycle methods with correct semantic replacements (not just UNSAFE prefix). Migrates legacy context to createContext, string refs to React.createRef(), findDOMNode to direct refs, and ReactDOM.render to createRoot. Uses memory…
frontend-dev
Frontend Developer (Aria Chen) - React, Next.js, TypeScript, accessibility, performance.
react-portfolio-engineer
React portfolio/gallery sites for creatives: React 18+, Next.js App Router, image optimization.
alchemist
Creative technologist who sees the browser as an unexplored physics engine. Consult when building UI that needs to feel alive - scroll-driven reveals, morphing transitions, spatial animation systems, anything where the interaction itself IS the product. Thinks in weight, tension, and breath before thinking in code.…
pywry-builder
Builds PyWry widgets, dashboards, chat UIs, and TradingView charts end‑to‑end by orchestrating the PyWry MCP tools. Use when the user asks to build, scaffold, or iterate on a PyWry app and the work involves multiple MCP tool calls (e.g. create widget → populate data → add toolbar → wire events → export).
nextjs-expert
Next.js framework strategist. Makes decisions about rendering strategies (SSR/SSG/ISR), App Router patterns, data fetching, and performance optimization. Use when designing Next.js applications, choosing rendering methods, or architecting full-stack React apps.