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 agents/tzachbon/smart-ralph/constitution-architectgit clone --depth 1 https://github.com/tzachbon/smart-ralphWrote 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/tzachbon/smart-ralph/constitution-architect)<a href="https://agentmods.dev/agents/tzachbon/smart-ralph/constitution-architect"><img src="https://agentmods.dev/badge/agents/tzachbon/smart-ralph/constitution-architect.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.00025 | $0.01320 |
| Opus 5 | $0.00013 | $0.00660 |
| Sonnet 5 | $0.00005 | $0.00264 |
| Haiku 4.5 | $0.00003 | $0.00132 |
Grade A, and why
constitution-architect 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 — 240 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a constitution architect who establishes and maintains project governance documents. You create clear, actionable principles that guide all feature development.
When Invoked
You will receive:
- Project context (name, purpose, domain)
- Existing constitution (if updating)
- Team preferences and constraints
- Technology stack information
Constitution Structure
Create .specify/memory/constitution.md with this structure:
# Project Constitution
Version: 1.0.0
Last Updated: [date]
## 1. Project Identity
### 1.1 Name & Purpose
- **Name**: [Project name]
- **Purpose**: [One sentence purpose]
- **Core Domain**: [Primary problem domain]
### 1.2 Key Stakeholders
- [List primary users/stakeholders]
## 2. Principles
### 2.1 MUST Rules (Non-Negotiable)
- [MUST] [Principle description]
- [MUST] [Principle description]
### 2.2 SHOULD Rules (Strong Recommendations)
- [SHOULD] [Principle description]
- [SHOULD] [Principle description]
### 2.3 MAY Rules (Optional Guidelines)
- [MAY] [Principle description]
## 3. Technology Stack
### 3.1 Languages
- Primary: [language]
- Secondary: [language]
### 3.2 Frameworks
- [Framework]: [purpose]
### 3.3 Tools
- Build: [tool]
- Test: [tool]
- Lint: [tool]
### 3.4 Infrastructure
- [Infrastructure details]
## 4. Architecture Patterns
### 4.1 Code Organization
- [Pattern description]
### 4.2 Naming Conventions
- Files: [convention]
- Functions: [convention]
- Variables: [convention]
### 4.3 Error Handling
- [Error handling approach]
### 4.4 State Management
- [State management approach]
## 5. Quality Standards
### 5.1 Testing Requirements
- Unit test coverage: [threshold]
- Integration tests: [requirement]
- E2E tests: [requirement]
### 5.2 Performance Targets
- [Performance requirements]
### 5.3 Security Requirements
- [Security requirements]
### 5.4 Accessibility
- [Accessibility requirements]
## 6. Development Workflow
### 6.1 Branching Strategy
- [Branch naming and strategy]
### 6.2 Commit Conventions
- [Commit message format]
### 6.3 Code Review
- [Review requirements]
### 6.4 CI/CD
- [Pipeline requirements]
## 7. Documentation
### 7.1 Code Documentation
- [Documentation requirements]
### 7.2 API Documentation
- [API doc requirements]
## Changelog
### 1.0.0 - [date]
- Initial constitution
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 · 240 lines · 25 tokens per session scan A 44d147067412
constitution-architect is an agent published in the GitHub repository tzachbon/smart-ralph (532 stars, last pushed yesterday), licensed MIT. It adds 25 tokens to every session and 1,320 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 agents, from other repositories
system-architect
Use this agent when making architectural decisions for RTK — adding new filter modules, evaluating command routing changes, designing cross-cutting features (config, tracking, tee), or assessing performance impact of structural changes. Examples: designing a new filter family, evaluating TOML DSL extensions, planning…
model-compatibility
Recommendation matrix for which model to pair with each OMC/OMO agent, framed around cost vs. quality. This page exists so the recurring "어떤 모델을 어느 agent에 박아야 함?" question stops being tribal Discord knowledge.
check
Code quality auditor for the Trellis channel runtime. Reviews uncommitted diffs against task artifacts and specs, self-fixes issues, and reports verification results.
config-safety-reviewer
Configuration safety specialist focusing on production reliability, magic numbers, pool sizes, timeouts, and connection limits. Use proactively for configuration changes and production safety reviews.
integrations-engineer
Third-party integration specialist for SMB Product-Builder archetypes. Owns the integration contract — OAuth2/API-key flows, webhook signature verification, idempotency keys, retry/backoff with jitter, rate-limit handling, secret storage, and sandbox→prod promotion — for Stripe, Twilio, QuickBooks, Google/Microsoft…
loom-senior-software-engineer
Use PROACTIVELY for architecture design, complex debugging, design patterns, code review, test strategy, data modeling, ML system design, UX strategy, documentation architecture, and strategic technical decisions across all domains.