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/lmammino/c4-codebase-architecture-skill/c4-codebase-architecturenpx skills add lmammino/c4-codebase-architecture-skill --skill c4-codebase-architecturegit clone --depth 1 https://github.com/lmammino/c4-codebase-architecture-skillWrote 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/lmammino/c4-codebase-architecture-skill/c4-codebase-architecture)<a href="https://agentmods.dev/skills/lmammino/c4-codebase-architecture-skill/c4-codebase-architecture"><img src="https://agentmods.dev/badge/skills/lmammino/c4-codebase-architecture-skill/c4-codebase-architecture.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.00047 | $0.03046 |
| Opus 5 | $0.00023 | $0.01523 |
| Sonnet 5 | $0.00009 | $0.00609 |
| Haiku 4.5 | $0.00005 | $0.00305 |
Grade A, and why
c4-codebase-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 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- c4-codebase-architecture — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 539 lines — stays where its author put it; the contents beside it link to each section on GitHub.
C4 Model Codebase Documentation Skill
Purpose
This skill helps an agent inspect a codebase and produce useful C4-style architecture documentation. It should combine evidence from the repository with targeted follow-up questions whenever code inspection alone is not enough to determine system boundaries, responsibilities, runtime topology, or business intent.
The skill should be pragmatic rather than dogmatic. The goal is not to force every repository into a perfect set of four diagrams, but to produce the clearest possible architecture view at the right level of detail.
When to use this skill
Use this skill when the user wants to:
- understand the architecture of an existing codebase
- produce C4 documentation for a repository
- generate a system context, container, or component view
- onboard new engineers with architecture docs
- reverse engineer system structure from code and infrastructure definitions
- compare intended architecture with implemented architecture
This skill works best when the repository includes at least some of the following:
- source code
- infrastructure as code
- deployment descriptors
- README or docs
- API specifications
- CI/CD configuration
- test suites
What this skill should produce
The skill should aim to produce some or all of the following, depending on what the codebase supports:
-
System Context
- the system under study
- human users or personas
- external systems, APIs, providers, or dependencies
- key relationships
-
Container view
- main deployable or runnable units
- databases, queues, frontends, APIs, workers, serverless functions, data stores
- protocols and interactions between them
-
Component view
- major internal components within a selected container
- their responsibilities and relationships
-
Supporting narrative
- assumptions made from code inspection
- unresolved ambiguities
- questions for the user
- notable architectural risks or mismatches
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 · 539 lines · 47 tokens per session scan A 69c37c26f2e5
c4-codebase-architecture is a skill published in the GitHub repository lmammino/c4-codebase-architecture-skill (17 stars, last pushed 4mo ago), licensed MIT. It adds 47 tokens to every session and 3,046 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-30.
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…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…