Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/exchanet/method_enterprise_builder_planningnpx agentmods add skills/exchanet/method_enterprise_builder_planning/phase-5-adrWrote 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/exchanet/method_enterprise_builder_planning/phase-5-adr)<a href="https://agentmods.dev/skills/exchanet/method_enterprise_builder_planning/phase-5-adr"><img src="https://agentmods.dev/badge/skills/exchanet/method_enterprise_builder_planning/phase-5-adr/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/exchanet/method_enterprise_builder_planning/phase-5-adr"><img src="https://agentmods.dev/badge/skills/exchanet/method_enterprise_builder_planning/phase-5-adr.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.00017 | $0.00761 |
| Opus 5.5 | $0.00007 | $0.00304 |
| Sonnet 5.5 | $0.00003 | $0.00152 |
| Haiku 4.5 | $0.00002 | $0.00076 |
Grade A, and why
phase-5-adr scanned grade A with 1 finding 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 2mo 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
subprocess.run(['node', '--experimental-strip-types', How it starts
The opening of the file, as written. The whole thing — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Phase 5 — Architecture Decisions (ADR)
Purpose
Execute Phase 5: apply the architecture decision tree, create ADRs for every significant decision, generate C4 diagrams, and validate all ADRs before marking as Accepted.
When to use
- Phase 5 of the full 8-phase cycle
- When the user needs architecture guidance independently
- When designing a new module or refactoring an existing system
Decision Tree
Answer these questions in order to select the primary architectural pattern:
-
Single team or multiple autonomous teams?
- Single → Modular Monolith
- Multiple → Microservices
-
Does business complexity require a rich domain model?
- Yes → Hexagonal Architecture / DDD
- No → Layered Architecture
-
Is full state audit trail required?
- Yes → Event Sourcing
- No → Standard persistence
-
Are reads and writes radically different in volume?
- Yes → CQRS
- No → Standard CRUD
-
Are there distributed transactions across services?
- Yes → Saga pattern (Orchestration or Choreography)
- No → Local transactions
ADR Template (mandatory sections)
Every ADR must include:
# ADR-NNN: Short description of the decision
**Date:** YYYY-MM-DD
**Status:** Proposed | Accepted | Deprecated | Superseded
**Deciders:** Name, Role
## Context
[2-3 paragraphs: problem, constraints, why decide now]
## Decision
[Clear statement of the decision]
## Alternatives Considered
| Alternative | Pros | Cons | Why rejected |
|---|---|---|---|
| Option A | ... | ... | Rejected because [reason] |
| Option B | ... | ... | Rejected because [reason] |
## Consequences
**Positive:**
- [benefit 1]
**Negative:**
- [drawback 1] — mitigated by [mitigation]
## Compliance Impact
[State which standards affected, or confirm no impact]
Validation step
After generating each ADR, validate it:
node packs/enterprise-architecture-pack/validators/adr-validator/src/index.ts \
--format=console docs/adr/ADR-NNN-title.md
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.
- 2mo ago First seen · 118 lines · 17 tokens per session scan A b35f0426b825
phase-5-adr is a skill published in the GitHub repository exchanet/method_enterprise_builder_planning (2 stars, last pushed 8mo ago), licensed MIT. It adds 17 tokens to every session and 761 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
adr-documentation
Architecture Decision Records (ADR) documentation practice. Use when documenting architectural decisions, recording technical trade-offs, creating decision logs, or establishing architectural patterns. Trigger keywords - "ADR", "architecture decision", "decision record", "trade-offs", "architectural decision"…
adr-writing
Write Architecture Decision Records future engineers will actually read. Invoke when making a non-trivial architectural choice that you want to defend later.
adr
Architecture Decision Record (ADR) — Philosophy-First: Creates well-structured ADRs using a 3-phase process: (1) Define the architectural philosophy and identity of the system, (2) Explore options through the lens of that philosophy, (3) Adversarial review by a devil's advocate agent. Use this skill whenever the user…
architecture-decision-record-creator
Create structured Architecture Decision Records (ADRs) with 7 sections to document architecture decisions with full justification. Use this skill whenever the user has made or needs to make an architecture decision, wants to document why a technical choice was made, is choosing between technologies or patterns, needs…
architecture-decision-records
Write and maintain Architecture Decision Records (ADRs) following best practices for technical decision documentation. Use when documenting significant technical decisions, reviewing past architectural choices, or establishing decision processes.
product-data-cleanup
Clean a local FF&E CSV schedule by normalizing casing, dimensions, units, language, materials, and formatting. Use when asked to clean, fix, or standardize product data.