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/exchanet/method_enterprise_builder_planning/validate-adrnpx skills add exchanet/method_enterprise_builder_planning --skill validate-adrgit clone --depth 1 https://github.com/exchanet/method_enterprise_builder_planningWrote 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/validate-adr)<a href="https://agentmods.dev/skills/exchanet/method_enterprise_builder_planning/validate-adr"><img src="https://agentmods.dev/badge/skills/exchanet/method_enterprise_builder_planning/validate-adr.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.00017 | $0.00623 |
| Opus 5 | $0.00009 | $0.00311 |
| Sonnet 5 | $0.00003 | $0.00125 |
| Haiku 4.5 | $0.00002 | $0.00062 |
Grade A, and why
validate-adr 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 4d 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Validate ADR
Purpose
Run the enterprise ADR Validator against one or more ADR files to check compliance with 11 validation rules.
When to use
- After generating any ADR in Phase 5
- Before marking an ADR as Accepted
- When the user explicitly requests ADR validation
- As part of the Phase 5 gate check
How to run
# Single ADR
node packs/enterprise-architecture-pack/validators/adr-validator/src/index.ts \
--format=console docs/adr/ADR-001-isolation.md
# All ADRs in directory
node packs/enterprise-architecture-pack/validators/adr-validator/src/index.ts \
--strict docs/adr/
Rules checked
| Rule ID | Severity | Check |
|---|---|---|
| ADR-STR-001 | error | Required sections (Context, Decision) present |
| ADR-STR-002 | error | ADR has a title |
| ADR-STR-003 | warning | Context section is not empty (≥50 chars) |
| ADR-ENT-001 | error | ≥2 alternatives documented |
| ADR-ENT-002 | error | Alternatives include rejection reasons |
| ADR-ENT-003 | error | Compliance Impact section present |
| ADR-ENT-004 | error | Valid status (Proposed/Accepted/Deprecated/Superseded) |
| ADR-ENT-005 | error | ISO 8601 date format (YYYY-MM-DD) |
| ADR-COMP-001 | warning | Security ADRs reference a compliance standard |
| ADR-COMP-002 | warning | Consequences section present |
| ADR-COMP-003 | warning | Regulated ADRs name their deciders |
Output interpretation
Console format:
✓ docs/adr/ADR-001-isolation.md — PASS
✗ docs/adr/ADR-002-saga.md — FAIL
✗ [ADR-ENT-001] Enterprise ADRs must document at least 2 alternatives.
→ Add a table with at least 2 alternative approaches...
Gate rule: An ADR with any error-severity violation cannot be marked as Accepted.
Fix all errors, re-run the validator, confirm ALL PASSED, then mark the ADR as Accepted.
Integration with Phase 5
After generating an ADR:
- Save the file:
docs/adr/ADR-NNN-title.md - Load
@skill validate-adr - Run the validator (terminal command or code execution)
- If FAIL: fix violations, re-run validator
- If PASS: mark ADR as Accepted, proceed to next decision
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.
- 4d ago First seen · 73 lines · 17 tokens per session scan A 7bea4946386a
validate-adr is a skill published in the GitHub repository exchanet/method_enterprise_builder_planning (2 stars, last pushed 6mo ago), licensed MIT. It adds 17 tokens to every session and 623 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
studio
Architecture Studio control plane — initialize or inspect a studio workspace, create and register projects, or route an architecture/AEC task to the right agent or skill. Use when the user runs /as:studio, asks to set up or open their studio, manage its projects, or describes a task without naming a skill.
workplan
Create a durable, execution-ready work plan for repository changes, operations, research, or AEC project delivery. Use when the user asks to plan, scope, sequence, coordinate, or break down multi-step work before acting. Do not use for floor plans, site plans, space planning, zoning calculations, building-code…
meeting-minutes
Turn a meeting transcript, notes, or conversation into collision-safe, source-linked minutes in meetings/YYYY-MM-DD-slug.md. Use for project meeting records, attendance, discussion, stated information, decisions, action candidates, and open questions. Saving minutes never changes PROJECT.md, decisions/, or TASKS.md…
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.
product-research
Find and compare current FF&E candidates from a design brief, with sourced purchasing facts and optional CSV-library save. Use to research or source products; not to match from an image or pair coordinating items.
spec-writer
Turn a material or product list into CSI MasterFormat outline specifications with three-part sections and review flags. Use to write specs; use epd-to-spec for embodied-carbon requirements.