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 skills add romiluz13/cc10x --skill architecturegit clone --depth 1 https://github.com/romiluz13/cc10xWrote 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/cc10x/architecture)<a href="https://agentmods.dev/skills/romiluz13/cc10x/architecture"><img src="https://agentmods.dev/badge/skills/romiluz13/cc10x/architecture/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/skills/romiluz13/cc10x/architecture"><img src="https://agentmods.dev/badge/skills/romiluz13/cc10x/architecture.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00056 | $0.01473 |
| Opus 5.5 | $0.00022 | $0.00589 |
| Sonnet 5.5 | $0.00011 | $0.00295 |
| Haiku 4.5 | $0.00006 | $0.00147 |
Grade A, and why
architecture 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 14d 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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architecture
Design systems from scratch: map flows, then draw components. For retrofitting existing code, use codebase-hygiene instead.
Intake Routing
| Request type | Use |
|---|---|
| New system/major feature (greenfield) | This skill |
| Existing code with shallow modules | codebase-hygiene |
| Multi-component integration | This skill |
| Single-component refactor | planning + building |
Functionality-First Design Process
Phase 1: Map Functionality Flows
Map every user flow end-to-end before designing any component:
Flow: [name]
1. [step] → [what the system does] → [what the user sees]
2. [step] → [what the system does] → [what the user sees]
Error paths:
- [error] → [system response] → [user sees]
Every flow must have its error paths mapped. Unmapped error paths become unmapped components.
Phase 2: Map to Architecture
Translate flows into components:
- Each flow step maps to one or more components
- Each error path maps to a component's error handling
- Data crossings between components become interfaces
Phase 3: Design Components
For each component:
- Interface: what it receives and returns (the contract)
- Responsibility: what it does (one sentence)
- Dependencies: what it needs (other components, external services)
- State: what it remembers (if anything)
- Error handling: what can go wrong and what it does about it
Before finalizing any component boundary, apply the Deletion Test and Two-Adapter Rule as defined in cc10x:codebase-design. A component that fails the deletion test (complexity vanishes if deleted) or fails the two-adapter rule (it is a port with only one adapter — an ordinary caller or test exercising the interface is not an adapter) is not a real boundary yet — fold it into its caller or defer the split until a second concrete need appears.
Architecture Views
System Context (C4 Level 1)
Box diagram: your system + external systems it talks to. One paragraph per external system: what it provides, what you depend on.
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.
- 14d ago Changed · -2 lines 7ff27295eecf
- 1mo ago First seen · 169 lines · 56 tokens per session scan A 4a896acbd613
architecture is a skill published in the GitHub repository romiluz13/cc10x (165 stars, last pushed today), licensed MIT. It adds 56 tokens to every session and 1,473 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 skills, from other repositories
push-ci
Push to remote and monitor CI. Validates branch safety, executes git push WITH explicit user approval, then monitors CI run status via gh CLI. Use when: user says 'push', 'push and watch CI', 'ship it', 'push-ci'. Not for: committing (use /smart-commit), creating PRs (use /create-pr), merging (use /merge-prep).
create-request
Create, update, or scan per-task request tickets for progress tracking. These are date-prefixed non-lifecycle docs under requests/, NOT feature-level requirements (use /req-analyze for those). Use when: tracking task progress, updating completion status, scanning incomplete requests, checking request status dashboard.…
gh-stack
Native stacked pull requests through the github/gh-stack extension. Detects the extension, installs it only after the user approves, resolves the branch chain, and executes gh stack link / gh stack push / gh stack submit --auto under a per-use AskUserQuestion gate. Use when: opening or refreshing a native stack of…
smart-rebase
Smart partial rebase for squash-merge repositories. Auto-detect which commits to keep/drop when base branch was squash-merged into target. Use when: user says 'rebase', 'partial rebase', 'base already merged', 'smart rebase', or /smart-rebase. Not for: simple git rebase (the developer runs it — no skill executes…
remind
A correction helper that checks which project rules or required steps were missed and loads the relevant guidance.
adr
Write an Architecture Decision Record (ADR) for a feature — Context / Decision / Status / Consequences / Alternatives, filed as docs/features/ /adr- - .md with a 3-digit zero-padded number. Handles the Superseded case: bidirectional linking when a new ADR replaces an old one. Use when: recording why an architectural…