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 skills/romiluz13/cc-teams/cross-layer-buildnpx skills add romiluz13/cc-teams --skill cross-layer-buildgit clone --depth 1 https://github.com/romiluz13/cc-teamsWrote 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/skills/romiluz13/cc-teams/cross-layer-build)<a href="https://agentmods.dev/skills/romiluz13/cc-teams/cross-layer-build"><img src="https://agentmods.dev/badge/skills/romiluz13/cc-teams/cross-layer-build.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 | $0.00033 | $0.02360 |
| Opus 5 | $0.00016 | $0.01180 |
| Sonnet 5 | $0.00007 | $0.00472 |
| Haiku 4.5 | $0.00003 | $0.00236 |
Grade A, and why
cross-layer-build 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 5d 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 — 262 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cross-Layer Build Protocol
Overview
Cross-Layer Build runs two TDD builders in parallel — backend-builder (API/services/models) and frontend-builder (components/pages/hooks) — with a mandatory API contract relay phase ensuring the frontend implements against a verified, stable API contract.
Core principle: Distinct file ownership + verified contract relay = true parallel implementation without coordination overhead.
When to use: Features that require both UI changes AND API/service changes. Not for UI-only or API-only features (use standard BUILD FULL for those).
Detection Signals
Lead applies cross-layer routing when ANY of these are present:
- User requirements explicitly mention BOTH frontend (UI/components/pages) AND backend (API/services/DB)
- Plan covers files in BOTH
src/components/(or pages/) ANDsrc/api/(or services/) - User explicitly requests "full-stack", "cross-layer", or "frontend and backend" implementation
- AskUserQuestion confirms: "Will this feature require changes to both UI and API/services?"
Team Composition
| Teammate | Phase | File Scope | Mode | When Active |
|---|---|---|---|---|
| backend-builder | Phase 1a | src/api/, src/services/, src/models/, src/db/ |
READ+WRITE | First — publishes API contract |
| frontend-builder | Phase 1b | src/components/, src/pages/, src/hooks/, src/styles/ |
READ+WRITE | After contract relay |
| live-reviewer | Phase 1c (async) | All modified files | READ-ONLY | After BOTH builders complete |
| hunter | Phase 2 | All modified files | READ-ONLY | After live-reviewer |
| security-reviewer | Phase 3 | All modified files | READ-ONLY | Parallel (after hunter) |
| performance-reviewer | Phase 3 | All modified files | READ-ONLY | Parallel (after hunter) |
| quality-reviewer | Phase 3 | All modified files | READ-ONLY | Parallel (after hunter) |
| accessibility-reviewer | Phase 3 (conditional) | Frontend files | READ-ONLY | If UI files detected |
| api-contract-reviewer | Phase 3 (conditional) | Backend files | READ-ONLY | If API files detected |
| verifier | Phase 4 | Integration E2E | READ-ONLY | After challenge round |
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.
- 5d ago First seen · 262 lines · 33 tokens per session scan A 67322a17c674
cross-layer-build is a skill published in the GitHub repository romiluz13/cc-teams (5 stars, last pushed 4mo ago), licensed MIT. It adds 33 tokens to every session and 2,360 once invoked, about $0.0002 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…