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/nomarj/sigil/c4-componentgit 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-component)<a href="https://agentmods.dev/agents/nomarj/sigil/c4-component"><img src="https://agentmods.dev/badge/agents/nomarj/sigil/c4-component.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 | $0.00051 | $0.02187 |
| Opus 5 | $0.00026 | $0.01094 |
| Sonnet 5 | $0.00010 | $0.00437 |
| Haiku 4.5 | $0.00005 | $0.00219 |
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 today.
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 — 249 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.
- today First seen · 249 lines · 51 tokens per session scan A be187f72198c
c4-component is an agent published in the GitHub repository NOMARJ/sigil (5 stars, last pushed today), licensed Apache-2.0. It adds 51 tokens to every session and 2,187 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-09-03.
Other agents, from other repositories
hyperledger-fabric-developer
Develop enterprise blockchain solutions with Hyperledger Fabric v2.5 LTS and v3.x. Expertise in chaincode development, network architecture, BFT consensus, and permissioned blockchain design. Use PROACTIVELY for enterprise blockchain, supply chain solutions, or private network implementations.
blockchain-developer
Develop smart contracts, DeFi protocols, and Web3 applications. Expertise in Solidity, security auditing, and gas optimization. Use PROACTIVELY for blockchain development, smart contract security, or Web3 integration.
arbitrage-bot
Identify and execute cryptocurrency arbitrage opportunities across exchanges and DeFi protocols. Use PROACTIVELY for arbitrage bot development, cross-exchange trading, and DEX/CEX arbitrage.
crypto-risk-manager
Implement risk management systems for cryptocurrency trading and DeFi positions. Use PROACTIVELY for portfolio risk assessment, position sizing, and risk monitoring systems.
defi-strategist
Design and implement DeFi yield strategies, liquidity provision, and protocol interactions. Use PROACTIVELY for yield farming, liquidity mining, and DeFi protocol integration.
prometeo-pm
Product Manager agent for product strategy, feature specifications, user stories, business logic, prioritization, and roadmap management. Use for any product definition, business requirement, or feature planning task.