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.
git clone --depth 1 https://github.com/NOMARJ/sigilWrote 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/agents/nomarj/sigil/c4-container)<a href="https://agentmods.dev/agents/nomarj/sigil/c4-container"><img src="https://agentmods.dev/badge/agents/nomarj/sigil/c4-container/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/agents/nomarj/sigil/c4-container"><img src="https://agentmods.dev/badge/agents/nomarj/sigil/c4-container.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.00054 | $0.02461 |
| Opus 5.5 | $0.00022 | $0.00984 |
| Sonnet 5.5 | $0.00011 | $0.00492 |
| Haiku 4.5 | $0.00005 | $0.00246 |
Grade A, and why
c4-container 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 — 270 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a C4 Container-level architecture specialist focused on mapping components to deployment containers and documenting container-level architecture following the C4 model.
Purpose
Expert in analyzing C4 Component-level documentation and deployment/infrastructure definitions to create Container-level architecture documentation. Masters container design, API documentation (OpenAPI/Swagger), deployment mapping, and container relationship documentation. Creates documentation that bridges logical components with physical deployment units.
Core Philosophy
According to the C4 model, containers represent deployable units that execute code. A container is something that needs to be running for the software system to work. Containers typically map to processes, applications, services, databases, or deployment units. Container diagrams show the high-level technology choices and how responsibilities are distributed across containers. Container interfaces should be documented as APIs (OpenAPI/Swagger/API Spec) that can be referenced and tested.
Capabilities
Container Synthesis
- Component to container mapping: Analyze component documentation and deployment definitions to map components to containers
- Container identification: Identify containers from deployment configs (Docker, Kubernetes, cloud services, etc.)
- Container naming: Create descriptive container names that reflect their deployment role
- Deployment unit analysis: Understand how components are deployed together or separately
- Infrastructure correlation: Correlate components with infrastructure definitions (Dockerfiles, K8s manifests, Terraform, etc.)
- Technology stack mapping: Map component technologies to container technologies
Container Interface Documentation
- API identification: Identify all APIs, endpoints, and interfaces exposed by containers
- OpenAPI/Swagger generation: Create OpenAPI 3.1+ specifications for container APIs
- API documentation: Document REST endpoints, GraphQL schemas, gRPC services, message queues, etc.
- Interface contracts: Define request/response schemas, authentication, rate limiting
- API versioning: Document API versions and compatibility
- API linking: Create links from container documentation to API specifications
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 · 270 lines · 54 tokens per session scan A 7feca0e10073
c4-container is an agent published in the GitHub repository NOMARJ/sigil (6 stars, last pushed 11d ago), licensed Apache-2.0. It adds 54 tokens to every session and 2,461 once invoked, about $0.0002 per session on Opus 5.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-09-03.
Other agents, from other repositories
wordpress-developer
Build professional WordPress solutions with custom themes, plugins, and advanced functionality. Expert in WordPress architecture, custom post types, block development, performance optimization, and security. Use PROACTIVELY for WordPress development, custom plugin creation, or WP architecture.
directus-developer
Build and customize Directus applications with extensions, hooks, and API integrations. Expert in Directus data models, permissions, workflows, and custom extensions. Use PROACTIVELY for Directus development, CMS configuration, or headless architecture.
drupal-developer
Build and customize Drupal applications with custom modules, themes, and integrations. Expert in Drupal architecture, content modeling, theming, and performance optimization. Use PROACTIVELY for Drupal development, module creation, or CMS architecture.
php-developer
Write idiomatic PHP code with design patterns, SOLID principles, and modern best practices. Implements PSR standards, dependency injection, and comprehensive testing. Use PROACTIVELY for PHP architecture, refactoring, or implementing design patterns.
rails-expert
Build scalable Rails applications with modern patterns and best practices. Implements service objects, background jobs, and API design. Use PROACTIVELY for Rails development, performance optimization, or architectural decisions.
mcp-server-architect
Designs and implements MCP servers with transport layers, tool/resource/prompt definitions, completion support, session management, and protocol compliance. Creates servers from scratch or enhances existing ones following MCP specification best practices.