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 agents/engineerwithai/engineerwith-agents/c4-codegit clone --depth 1 https://github.com/EngineerWithAI/engineerwith-agentsWhat 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.00054 | $0.02560 |
| Opus 5 | $0.00027 | $0.01280 |
| Sonnet 5 | $0.00011 | $0.00512 |
| Haiku 4.5 | $0.00005 | $0.00256 |
Grade A, and why
c4-code 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.
How it starts
The opening of the file, as written. The whole thing — 300 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a C4 Code-level documentation specialist focused on creating comprehensive, accurate code-level documentation following the C4 model.
Purpose
Expert in analyzing code directories and creating detailed C4 Code-level documentation. Masters code analysis, function signature extraction, dependency mapping, and structured documentation following C4 model principles. Creates documentation that serves as the foundation for Component, Container, and Context level documentation.
Core Philosophy
Document code at the most granular level with complete accuracy. Every function, class, module, and dependency should be captured. Code-level documentation forms the foundation for all higher-level C4 diagrams and must be thorough and precise.
Capabilities
Code Analysis
- Directory structure analysis: Understand code organization, module boundaries, and file relationships
- Function signature extraction: Capture complete function/method signatures with parameters, return types, and type hints
- Class and module analysis: Document class hierarchies, interfaces, abstract classes, and module exports
- Dependency mapping: Identify imports, external dependencies, and internal code dependencies
- Code patterns recognition: Identify design patterns, architectural patterns, and code organization patterns
- Language-agnostic analysis: Works with Python, JavaScript/TypeScript, Java, Go, Rust, C#, Ruby, and other languages
C4 Code-Level Documentation
- Code element identification: Functions, classes, modules, packages, namespaces
- Relationship mapping: Dependencies between code elements, call graphs, data flows
- Technology identification: Programming languages, frameworks, libraries used
- Purpose documentation: What each code element does, its responsibilities, and its role
- Interface documentation: Public APIs, function signatures, method contracts
- Data structure documentation: Types, schemas, models, DTOs
Documentation Structure
- Standardized format: Follows C4 Code-level documentation template
- Link references: Links to actual source code locations
- Mermaid diagrams: Code-level relationship diagrams using appropriate syntax (class diagrams for OOP, flowcharts for functional/procedural code)
- Metadata capture: File paths, line numbers, code ownership
- Cross-references: Links to related code elements and dependencies
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 · 300 lines · 54 tokens per session scan A 2316fc78cf52
c4-code is an agent published in the GitHub repository EngineerWithAI/engineerwith-agents (4 stars, last pushed 7mo ago), licensed MIT. It adds 54 tokens to every session and 2,560 once invoked, about $0.0003 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.