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 commands/commerce-atoms/agents/validate-architecturegit clone --depth 1 https://github.com/commerce-atoms/agentsWrote 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/commands/commerce-atoms/agents/validate-architecture)<a href="https://agentmods.dev/commands/commerce-atoms/agents/validate-architecture"><img src="https://agentmods.dev/badge/commands/commerce-atoms/agents/validate-architecture.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.00026 | $0.00366 |
| Opus 5 | $0.00013 | $0.00183 |
| Sonnet 5 | $0.00005 | $0.00073 |
| Haiku 4.5 | $0.00003 | $0.00037 |
Grade A, and why
validate-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 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.
What it actually says
/validate-architecture
Run the architecture validators against a Hydrogen storefront project.
Workflow
-
Resolve the target directory:
- If the user supplied a path, use it.
- Otherwise, use the current working directory.
-
Invoke the CLI:
npx @commerce-atoms/agents validate-architecture --out <path> -
Read the human-readable output. If exit code is non-zero, summarise violations grouped by
codefor the user. -
After structural changes (new module, manifest edits, shared-folder promotions), paste the summary into the PR or notes before marking work complete.
Output expectations
- PASS — exit 0, no further action needed.
- WARN — exit 0 (unless
--strict), but surface the warnings to the user with their remedies. - FAIL — exit 1, list every error with file path and remedy. Do not mark the work complete until errors are addressed or explicitly accepted.
See also
skills/validate-architecture/SKILL.md— the skill definition this command wraps.AGENTS.md §3— the rules being validated.- ADR 003 — why this skill exists in
agents/rather than as a separate MCP server.
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 · 39 lines · 26 tokens per session scan A b66c83fcc244
validate-architecture is a command published in the GitHub repository commerce-atoms/agents (1 stars, last pushed 4mo ago), licensed MIT. It adds 26 tokens to every session and 366 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 commands, from other repositories
core-review
Review code changes against SpecOps project-specific patterns. Catches recurring failure modes from real PRs — tool abstraction violations, generated file drift, cross-platform gaps, variable inconsistencies, and more. Complements full-review-gate (generic quality) and pr-fix (applying bot comments).
ship-pr
Commit all changes to a new branch, push, and open a PR for review. The original branch stays clean.
brownfield-map
Run a complete brownfield analysis on the codebase and generate MASTER.md, summaries, risk scores, and all derived analytics.
rclone_convmv
Convert file and directory names in place.
rclone_copy
Copy files from source to dest, skipping identical files.
rclone_listremotes
List all the remotes in the config file and defined in environment variables.