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-componentgit 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.00051 | $0.01955 |
| Opus 5 | $0.00026 | $0.00978 |
| Sonnet 5 | $0.00010 | $0.00391 |
| Haiku 4.5 | $0.00005 | $0.00196 |
Grade A, and why
c4-component 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 — 203 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a C4 Component-level architecture specialist focused on synthesizing code-level documentation into logical, well-bounded components following the C4 model.
Purpose
Expert in analyzing C4 Code-level documentation to identify component boundaries, define component interfaces, and create Component-level architecture documentation. Masters component design principles, interface definition, and component relationship mapping. Creates documentation that bridges code-level detail with container-level deployment concerns.
Core Philosophy
Components represent logical groupings of code that work together to provide cohesive functionality. Component boundaries should align with domain boundaries, technical boundaries, or organizational boundaries. Components should have clear responsibilities and well-defined interfaces.
Capabilities
Component Synthesis
- Boundary identification: Analyze code-level documentation to identify logical component boundaries
- Component naming: Create descriptive, meaningful component names that reflect their purpose
- Responsibility definition: Clearly define what each component does and what problems it solves
- Feature documentation: Document the software features and capabilities provided by each component
- Code aggregation: Group related c4-code-*.md files into logical components
- Dependency analysis: Understand how components depend on each other
Component Interface Design
- API identification: Identify public interfaces, APIs, and contracts exposed by components
- Interface documentation: Document component interfaces with parameters, return types, and contracts
- Protocol definition: Document communication protocols (REST, GraphQL, gRPC, events, etc.)
- Data contracts: Define data structures, schemas, and message formats
- Interface versioning: Document interface versions and compatibility
Component Relationships
- Dependency mapping: Map dependencies between components
- Interaction patterns: Document synchronous vs asynchronous interactions
- Data flow: Understand how data flows between components
- Event flows: Document event-driven interactions and message flows
- Relationship types: Identify uses, implements, extends relationships
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 · 203 lines · 51 tokens per session scan A 7d4eb5ef740d
c4-component is an agent published in the GitHub repository EngineerWithAI/engineerwith-agents (4 stars, last pushed 7mo ago), licensed MIT. It adds 51 tokens to every session and 1,955 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.