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/okhp3/skillz/c4-codebase-architecturenpx skills add OKHP3/skillz --skill c4-codebase-architecturegit clone --depth 1 https://github.com/OKHP3/skillzWrote 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/okhp3/skillz/c4-codebase-architecture)<a href="https://agentmods.dev/skills/okhp3/skillz/c4-codebase-architecture"><img src="https://agentmods.dev/badge/skills/okhp3/skillz/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.1 | $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 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.
This is a copy
100% identical to c4-codebase-architecture — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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.
- yesterday First seen · 539 lines · 47 tokens per session scan A 69c37c26f2e5
c4-codebase-architecture is a skill published in the GitHub repository OKHP3/skillz (3 stars, last pushed today), 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. It is 100% identical to c4-codebase-architecture, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
vastai-sdk
Vast.ai Python SDK — high-level API for GPU instances, volumes, serverless endpoints, and billing.
pm-aarrr
Use when: 产品上线后需要分析用户增长、制定增长策略、诊断产品健康度、优化AARRR各环节 Do NOT use when: 产品未上线、仅需单一指标分析无需全链路.
pm-docs
Use when: 需要输出PRD/BRD/MRD产品文档、方案文档、商业计划文档、需要文档模板 Do NOT auto-select when: 用户用自然语言说"写需求文档""写PRD""帮我设计需求"等新产品请求 → 这些必须先路由到 start-super-pm Direct slash-command use is allowed: 用户显式输入 /pm-docs 时可直接进入，但必须通过本 skill 的前置门禁 Do NOT use when: 文档已完备无需生成、仅需口头讨论无需书面输出.
pm-position
Use when: 需要明确产品定位、设计商业模式、规划盈利方式、制定定价策略、进行盈利预测 Do NOT use when: 产品定位已明确、仅需执行无需重新定位.
pm-retro
Use when: 迭代结束后需要复盘总结经验教训、改进团队流程、记录改进行动项 Do NOT use when: 迭代尚未结束、团队不需要正式复盘.
product-marketing-copywriter
当市场调研分析师与营销专员、内容创作者需要推广产品时，使用本技能可精准分析受众痛点与产品卖点，一键生成高转化标题与正文，快速产出激发购买欲的优质营销文案，大幅提升销售转化率。.