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 skills add bricerising/enterprise-software-playbook --skill architecturegit clone --depth 1 https://github.com/bricerising/enterprise-software-playbookWrote 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/bricerising/enterprise-software-playbook/architecture)<a href="https://agentmods.dev/skills/bricerising/enterprise-software-playbook/architecture"><img src="https://agentmods.dev/badge/skills/bricerising/enterprise-software-playbook/architecture/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/skills/bricerising/enterprise-software-playbook/architecture"><img src="https://agentmods.dev/badge/skills/bricerising/enterprise-software-playbook/architecture.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.00086 | $0.02977 |
| Opus 5.5 | $0.00034 | $0.01191 |
| Sonnet 5.5 | $0.00017 | $0.00595 |
| Haiku 4.5 | $0.00009 | $0.00298 |
Grade A, and why
architecture 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 — 191 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architecture (System Pattern Chooser)
Overview
Pick the smallest system/architecture pattern that addresses the pressure (reliability, consistency, domain boundaries, scalability).
Use code patterns for in-process structure; use system patterns when the problem is cross-process or cross-team.
Monolith edge case: If you're restructuring within a monolith without decomposing it into services (e.g., extracting modules, introducing internal boundaries, applying GoF patterns), use design instead. Use architecture when the monolith is being decomposed into separate deployable units, or when decisions span process/deployment/team boundaries.
Inputs / Outputs
Inputs: Archobs JSON — cluster coupling, leakage, risk scores (required); plan scope (if exists); forecast lifecycle data (if external deps involved).
Outputs: Pattern selection with rationale, decision table, boundary diagram, implementation tactics. Consumed by design (in-process patterns), spec (contracts), plan (task ordering).
Workflow
- Gather empirical data (required — wait for completion):
- Reuse
.archobs/file_metrics.parquetonly when it is newer than the most recent commit and.archobs/run_manifest.jsonexists withstatusequal tocomplete; otherwise runarchobs report --repo <path> --out .archobs --suggestions-provider rulesand wait for the report to complete before continuing. - Read results:
archobs show all --format json(or queryarchobs show risks,archobs show clustersindividually). - Use cluster leakage data to identify where boundaries are already porous.
- Use file-level risk scores to focus on the highest-impact areas.
- Skip this step only if the repo is too small (< 10 files) for meaningful analysis.
- Reuse
0b. Ecosystem Pressure Check (conditional — run when the architecture decision involves adopting or replacing a technology, defining boundaries around external dependencies, or planning work with a time horizon > 6 months):
What ships with it
59 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.
- references/3rd-party-registration.md 837 B
- references/access-token.md 769 B
- references/aggregate.md 783 B
- references/anti-corruption-layer.md 831 B
- references/api-composition.md 1.0 KB
- references/api-gateway-bff.md 1.2 KB
- references/application-metrics.md 682 B
- references/audit-logging.md 743 B
- references/circuit-breaker.md 882 B
- references/client-side-service-discovery.md 801 B
- references/client-side-ui-composition.md 852 B
- references/command-side-replica.md 824 B
- references/consumer-side-contract-test.md 697 B
- references/cqrs.md 839 B
- references/database-per-service.md 769 B
- references/decision-tree.md 5.3 KB
- references/decompose-by-business-capability.md 814 B
- references/decompose-by-subdomain.md 743 B
- references/distributed-tracing.md 692 B
- references/domain-event.md 795 B
- references/domain-specific-protocol.md 838 B
- references/event-driven-architecture.md 866 B
- references/event-sourcing.md 763 B
- references/exception-tracking.md 629 B
- references/externalized-configuration.md 836 B
- references/health-check-api.md 827 B
- references/idempotent-consumer.md 754 B
- references/log-aggregation.md 653 B
- references/log-deployments-and-changes.md 722 B
- references/messaging.md 925 B
- references/microservice-architecture.md 1.2 KB
- references/microservice-chassis.md 907 B
- references/monolithic-architecture.md 835 B
- references/multiple-service-instances-per-host.md 809 B
- references/patterns.md 3.3 KB
- references/polling-publisher.md 713 B
- references/publish-events-using-database-triggers.md 796 B
- references/remote-procedure-invocation-rpi.md 784 B
- references/saga.md 916 B
- references/self-contained-service.md 807 B
- references/self-registration.md 759 B
- references/server-side-page-fragment-composition.md 899 B
- references/server-side-service-discovery.md 844 B
- references/serverless-deployment.md 766 B
- references/service-component-test.md 813 B
- references/service-deployment-platform.md 744 B
- references/service-instance-per-container.md 735 B
- references/service-instance-per-vm.md 649 B
- references/service-integration-contract-test.md 835 B
- references/service-mesh.md 811 B
- references/service-per-team.md 797 B
- references/service-registry.md 910 B
- references/service-template.md 2.2 KB
- references/shared-database.md 711 B
- references/sidecar.md 800 B
- references/single-service-instance-per-host.md 628 B
- references/strangler-application.md 855 B
- references/transaction-log-tailing.md 872 B
- references/transactional-outbox.md 851 B
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 · 191 lines · 86 tokens per session scan A 717bc9979c31
architecture is a skill published in the GitHub repository bricerising/enterprise-software-playbook (8 stars, last pushed 8d ago), licensed Apache-2.0. It adds 86 tokens to every session and 2,977 once invoked, about $0.0003 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-08-31.
Other skills, from other repositories
frontmcp-guides
Tutorials, end-to-end walkthroughs, and complete reference projects for FrontMCP. Use when you want a getting-started guide, a full worked example, or to learn best practices by following a step-by-step build rather than a single API reference. Includes a beginner weather-API server (tool plus static resource, Zod…
dotnet-aspnetcore-service
Use when building or extending a C# service on ASP.NET Core - Minimal APIs or controllers, DI and options, EF Core with Npgsql, ProblemDetails, HttpClientFactory resilience, async and cancellation.
node-typescript-service
Use when building or extending a TypeScript service on Node.js - Fastify, NestJS, Express or Hono, runtime validation at the boundary, strict types, the repository's ORM and migrations, async error handling, graceful shutdown.
rust-axum-service
Use when building or extending a Rust service - axum on tokio (or the repository's actix-web / rocket), typed errors with IntoResponse, serde at the boundary, sqlx queries and migrations, never blocking the runtime, tracing, clippy.
go-hexagonal-architecture
Use when adding a use case, port, repository or adapter in a Go service — where each piece goes, how errors and transactions cross layers, and how to check the import direction.
quarkus-service-architecture
Use when building or extending a Java service with Quarkus - layered architecture, JAX-RS resources, CDI beans, Panache persistence, and native-friendly patterns.