Borrowing it
Nothing to install: this file belongs to Insight-Services-APAC/ingenious. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Insight-Services-APAC/ingenious/main/.claude/commands/viz/c4-map.mdgit clone --depth 1 https://github.com/Insight-Services-APAC/ingeniousWrote 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/commands/insight-services-apac/ingenious/c4-map)<a href="https://agentmods.dev/commands/insight-services-apac/ingenious/c4-map"><img src="https://agentmods.dev/badge/commands/insight-services-apac/ingenious/c4-map/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/commands/insight-services-apac/ingenious/c4-map"><img src="https://agentmods.dev/badge/commands/insight-services-apac/ingenious/c4-map.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.01720 |
| Opus 5.5 | $0.00000 | $0.00688 |
| Sonnet 5.5 | $0.00000 | $0.00344 |
| Haiku 4.5 | $0.00000 | $0.00172 |
Grade A, and why
c4-map 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 1mo 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 — 255 lines — stays where its author put it; the contents beside it link to each section on GitHub.
C4 Architecture Mapping
Map the codebase architecture using a hierarchical C4 model (Context -> Containers -> Components -> Code).
Orchestration
Phase 1: Context ──> Phase 2: Containers ──> Phase 3: Components ──> Phase 4: Code ──> Phase 5: Synthesis ──> Phase 6: Files
Each level depends on outputs from the previous level. Execute sequentially, passing outputs forward.
Output structure: See c4-templates.md
Phase 1: System Context
Tool: Task
Parameters:
subagent_type: "Explore"
description: "Map C4 system context"
prompt: |
Map SYSTEM CONTEXT level (C4 Level 1).
GOALS:
1. Identify system name, create kebab-case SYSTEM_ID
2. Define system boundary and purpose
3. Find actors (auth patterns, API consumers, user roles)
4. Map external systems (SDK imports, env vars, HTTP clients)
5. Identify preliminary containers (deployable units)
SEARCH:
- Glob: **/*.env*, **/pyproject.toml, **/package.json
- Grep: "requests\.", "httpx\.", "import.*azure", "import.*aws"
- Check docker-compose.yml for external services
OUTPUT: JSON per c4-templates.md#context-phase-output
Include C4-PlantUML context diagram
WAIT for Phase 1 to complete.
Store: SYSTEM_ID, EXTERNAL_SYSTEMS, PRELIMINARY_CONTAINERS
Phase 2: Containers
Tool: Task
Parameters:
subagent_type: "Explore"
description: "Map C4 containers"
prompt: |
Map CONTAINER level (C4 Level 2).
CONTEXT FROM PHASE 1:
- SYSTEM_ID: <insert>
- EXTERNAL_SYSTEMS: <insert>
- PRELIMINARY_CONTAINERS: <insert>
GOALS:
For each preliminary container:
1. Validate it's a distinct deployable unit
2. Identify technology stack (framework, runtime)
3. Map inter-container communication (protocols)
4. Identify preliminary components within each
5. Validate external system boundaries
SEARCH:
- Glob: **/Dockerfile, **/docker-compose.yml, **/main.py
- Grep: "FastAPI", "Express", "Flask"
- Analyze directory structure per container
OUTPUT: JSON per c4-templates.md#container-phase-output
Include C4-PlantUML container diagram
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.
- 1mo ago First seen · 255 lines · 0 tokens per session scan A 17a2f6024be9
c4-map is a command published in the GitHub repository Insight-Services-APAC/ingenious (25 stars, last pushed 9mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,720 tokens. 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-09-04.
Other commands, from other repositories
remote-autopilot-install.v1
Remotely install Stakpak Autopilot on any reachable Linux host over SSH, with optional AWS/GCP/Azure VM discovery or provisioning: /remote-autopilot-install.
create-agents.md
Generates an AGENTS.md file for a project repository.
create-readme
You're a senior expert software engineer with extensive experience in open source projects. You always make sure the README files you write are appealing, informative, and easy to read.
enable-beer
Once you have done the above steps, just prompt the user to run the azd up command to deploy the infrastructure and services to complete the setup.
fix-lint-issues
You're a senior expert software engineer with extensive experience in maintaining projects over long time and ensuring clean code and best practices.
review-and-refactor
You're a senior expert software engineer with extensive experience in maintaining projects over long time and ensuring clean code and best practices.