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/agricidaniel/ace-claude-code/validate-zonesgit clone --depth 1 https://github.com/AgriciDaniel/ace-claude-codeWrote 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/agricidaniel/ace-claude-code/validate-zones)<a href="https://agentmods.dev/commands/agricidaniel/ace-claude-code/validate-zones"><img src="https://agentmods.dev/badge/commands/agricidaniel/ace-claude-code/validate-zones.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.00014 | $0.02503 |
| Opus 5 | $0.00007 | $0.01252 |
| Sonnet 5 | $0.00003 | $0.00501 |
| Haiku 4.5 | $0.00001 | $0.00250 |
Grade A, and why
ace:validate-zones 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 — 439 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ensures no overlapping ownership patterns between zones, no conflicts between owns and forbidden lists, and that all source files are covered by some zone.
Required: @.ace/project-types.json @.ace/config.json (for current project type)
Scan: Project source files to check coverage
1. Load Zone Configuration
+==============================================================+
| ZONE VALIDATION |
+==============================================================+
Loading zone configuration...
Load project-types.json and determine target project type:
if $ARGUMENTS provided:
project_type = $ARGUMENTS
else:
Read config.json for project.type
if project_type not found in project-types.json:
Error: "Unknown project type: [type]"
Show available types
Display loaded configuration:
PROJECT TYPE: [type]
Name: [project name]
ZONES:
+--------+-------------------+--------------------------------+
| Zone | Name | Responsibility |
+--------+-------------------+--------------------------------+
| ALPHA | [zone name] | [responsibility] |
| BETA | [zone name] | [responsibility] |
| GAMMA | [zone name] | [responsibility] |
+--------+-------------------+--------------------------------+
+==============================================================+
2. Check Ownership Overlaps
Compare "owns" patterns across all zones:
OWNERSHIP OVERLAP CHECK:
Comparing zone ownership patterns...
ALPHA owns:
- src/models/**
- src/schemas/**
- src/types/**
BETA owns:
- src/services/**
- src/utils/**
- src/middleware/**
GAMMA owns:
- src/routes/**
- src/controllers/**
- src/app.ts
Checking for overlaps...
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 · 439 lines · 14 tokens per session scan A 58f997dfaf0a
ace:validate-zones is a command published in the GitHub repository AgriciDaniel/ace-claude-code (24 stars, last pushed 4mo ago), licensed MIT. It adds 14 tokens to every session and 2,503 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-30.
Other commands, from other repositories
canvas
AI-orchestrated visual canvas production — create, populate, layout, present, generate, and export Obsidian canvases.
document
Generate documentation for code.
test
Generate comprehensive tests for a file or function.
review
Review code for best practices and issues.
fix-issue
Analyze and fix a GitHub issue.
migrate
Create migration plan for upgrade.