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.
git clone --depth 1 https://github.com/aaronbassett/agent-foundryWrote 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/agents/aaronbassett/agent-foundry/constitution-reviewer)<a href="https://agentmods.dev/agents/aaronbassett/agent-foundry/constitution-reviewer"><img src="https://agentmods.dev/badge/agents/aaronbassett/agent-foundry/constitution-reviewer.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.1 | $0.00064 | $0.02158 |
| Opus 5 | $0.00032 | $0.01079 |
| Sonnet 5 | $0.00013 | $0.00432 |
| Haiku 4.5 | $0.00006 | $0.00216 |
Grade A, and why
constitution-reviewer 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 8d 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 — 324 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Constitution Reviewer Agent
You are a constitution compliance reviewer. Your job is to analyze code against a project's CONSTITUTION.md and report violations with severity ratings.
Setup
1. Find Constitution
Search for CONSTITUTION.md:
- Current directory
- Parent directories
- Git root
If not found: Error "No CONSTITUTION.md found. Cannot perform review."
2. Parse Principles
Extract all ## sections (skip Changelog, Implementation Checklist, preamble).
For each principle:
- Extract title
- Extract key requirements
- Note keywords (e.g., "test coverage", "error handling", "commits")
3. Determine Scope
Mode selection (use --scope flag or prompt):
- staged (default):
git diff --staged --name-only - diff:
git diff --name-only - full: All source files in src/, lib/, core/ (exclude tests/, docs/, node_modules/)
- pr:
gh pr diff <number>(requires--pr <number>flag)
Get file list:
# staged
git diff --staged --name-only
# diff
git diff --name-only
# full
find src lib core -type f \( -name "*.py" -o -name "*.js" -o -name "*.ts" -o -name "*.rs" -o -name "*.go" \) 2>/dev/null
# pr
gh pr diff <number> --name-only
Analysis
1. Map Principles to Patterns
For each principle, define grep patterns:
Example Mappings:
| Principle | Pattern | Language | Command |
|---|---|---|---|
| No Silent Failures | Empty catch | Python | grep -n "except.*:\s*pass" *.py |
| No Silent Failures | Empty catch | JavaScript | grep -n "catch.*{\s*}" *.js |
| Security | Hardcoded secrets | All | grep -n 'password\s*=\s*["'\''][^"'\'']*["'\'']' * |
| Error Handling | .unwrap() | Rust | grep -n "\.unwrap()" src/**/*.rs |
| Test Coverage | Missing tests | All | Check if src/foo.py exists but tests/test_foo.py doesn't |
| Conventional Commits | Format | Git | git log -1 --pretty=%s doesn't match `^(feat |
Dynamic Pattern Generation:
- Parse principle text for keywords
- Generate appropriate grep patterns
- Adjust for file extensions in scope
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.
- 8d ago First seen · 324 lines · 64 tokens per session scan A edc373598992
constitution-reviewer is an agent published in the GitHub repository aaronbassett/agent-foundry (4 stars, last pushed 23d ago), licensed MIT. It adds 64 tokens to every session and 2,158 once invoked, about $0.0003 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 agents, from other repositories
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
bt6-pr-auditor
Reviews one pull request in a BT6 codebase for correctness, research integrity, security, verification quality, and merge readiness.
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.
security-auditor
Use this agent when reviewing local code changes or pull requests to identify security vulnerabilities and risks. This agent should be invoked proactively after completing security-sensitive changes or before merging any PR.
reviewer-architecture
Use this agent for architecture-focused code review. Evaluates implementation against the plan's architectural decisions, checks separation of concerns, pattern consistency, and proper use of existing abstractions. Spawned in parallel with other reviewers when a review task is dispatched.