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 skills/matrixfounder/agentic-development/architecture-format-extendednpx skills add MatrixFounder/Agentic-development --skill architecture-format-extendedgit clone --depth 1 https://github.com/MatrixFounder/Agentic-developmentWrote 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/skills/matrixfounder/agentic-development/architecture-format-extended)<a href="https://agentmods.dev/skills/matrixfounder/agentic-development/architecture-format-extended"><img src="https://agentmods.dev/badge/skills/matrixfounder/agentic-development/architecture-format-extended.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.00020 | $0.00830 |
| Opus 5 | $0.00010 | $0.00415 |
| Sonnet 5 | $0.00004 | $0.00166 |
| Haiku 4.5 | $0.00002 | $0.00083 |
Grade A, and why
architecture-format-extended 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 3d 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 — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architecture Document Structure (Extended)
[!NOTE] This skill provides FULL templates with detailed examples. It extends
architecture-format-corewith comprehensive sections 3-10.
When to Load This Skill
| Condition | Action |
|---|---|
| Creating NEW system from scratch | ✅ Load this skill |
| Major refactor (>3 components changed) | ✅ Load this skill |
| Sophisticated requirement / complex task | ✅ Load this skill |
| User explicitly requests full template | ✅ Load this skill |
| Minor architecture update | ❌ Use architecture-format-core only |
3. System Components (Extended Examples)
[!TIP] Example Template: See
.agent/skills/architecture-format-extended/examples/component-template.md
Use the detailed component template for defining new services or major components.
4. Data Model (Full)
[!TIP] Example Template: See
.agent/skills/architecture-format-extended/examples/data-model.md
4.1. Conceptual Data Model
Description of main entities and their relationships at a high level.
4.2. Logical Data Model
Detailed description considering storage technology (Relational vs NoSQL).
4.3. Data Model Diagram
ER-diagram in PlantUML format.
4.4. Migrations and Versioning
Strategy for DB schema changes.
5. Interfaces
[!TIP] Example Template: See
.agent/skills/architecture-format-extended/examples/api-interface.md
5.1. External APIs
Detailed REST/GraphQL/gRPC definitions including authentication and error handling.
5.2. Internal Interfaces
Interaction between system components (e.g., Message Queues, Events).
5.3. Integrations with External Systems
Third-party service purpose, protocol, and error handling strategies.
6. Technology Stack
6.1. Backend
- Programming Language & Framework with justification.
6.2. Frontend
- Framework with justification.
6.3. Database
- Type (SQL/NoSQL) with justification.
6.4. Infrastructure
- Containerization (Docker)
- Orchestration (K8s/Compose)
- Middleware (Redis, RabbitMQ)
- Observability (Prometheus, ELK)
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago First seen · 145 lines · 20 tokens per session scan A d98df545483b
architecture-format-extended is a skill published in the GitHub repository MatrixFounder/Agentic-development (5 stars, last pushed yesterday), licensed Apache-2.0. It adds 20 tokens to every session and 830 once invoked, about $0.0001 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 skills, from other repositories
chimera-write-the-check-before-the-code
A criterion written after the implementation describes the implementation. Write the failing check first, watch it fail, then build.
Learn what defines effective BDD scenarios
Interactive guidance on writing complete, effective BDD scenarios for story-flow.
add-tests
Generates tests for existing code. Analyzes the target function, method, or class to identify the happy path, error cases, and edge cases, then writes test cases following the project's testing framework and naming conventions. Invoked when the user asks to add tests, write tests, cover code, or increase coverage.
tdd-implementation
Use when implementing any code change for a task – new behavior, a bugfix, or a revision after review – before writing the production code. Defines the failing-test-first cycle, public-seam testing, vertical slices, scaffold and infra handling, and counters to common excuses for tests-after-code.
test-writer
Writes tests that fail before a fix and pass after it.
new
Hand Claude Code a GitHub milestone; it drives every issue to a merged PR — TDD-enforced, mechanically gated, and bounded to your integration branch.