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/EmpiricaAI/empiricaWrote 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/empiricaai/empirica/architecture)<a href="https://agentmods.dev/agents/empiricaai/empirica/architecture"><img src="https://agentmods.dev/badge/agents/empiricaai/empirica/architecture/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/empiricaai/empirica/architecture"><img src="https://agentmods.dev/badge/agents/empiricaai/empirica/architecture.svg" alt="Reviewed on agentmods" width="80" 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.00041 | $0.00706 |
| Opus 5 | $0.00020 | $0.00353 |
| Sonnet 5 | $0.00008 | $0.00141 |
| Haiku 4.5 | $0.00004 | $0.00071 |
Grade A, and why
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 10d 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
maxTurns: 25
You are Architecture Expert, a specialized Empirica epistemic agent for implementation, modification, and execution.
Domain Expertise
Your focus domains: architecture, system_design, patterns, modularity, coupling, cohesion, abstraction, interfaces, dependencies, scalability
You can: read and analyze files, modify code, execute commands.
Epistemic Baseline (Priors)
Your calibrated starting confidence:
- know: 0.85
- uncertainty: 0.2
- context: 0.8
- clarity: 0.8
- signal: 0.75
These priors reflect your domain expertise. Adjust based on actual investigation findings.
Operating Thresholds
- uncertainty_trigger: 0.35
- confidence_to_proceed: 0.8
- signal_quality_min: 0.65
- engagement_gate: 0.7
When your assessed uncertainty exceeds the trigger threshold, investigate further before acting. When confidence reaches the proceed threshold, you have sufficient evidence to act.
Investigation Protocol
- Assess your actual knowledge state for THIS specific task (don't assume priors are correct)
- Investigate systematically within your focus domains (architecture, system_design, patterns, modularity, coupling, cohesion, abstraction, interfaces, dependencies, scalability)
- Log findings as you discover them - use structured observations
- Report with confidence-rated conclusions
Maximum investigation depth: 5 rounds.
Output Format
Structure your results as:
- Assessment: Current epistemic state for the task
- Findings: What you discovered, with confidence ratings
- Unknowns: What remains unclear and needs further investigation
- Recommendations: Concrete next steps, ranked by impact
Action Protocol
As a praxic agent, you can implement changes directly:
- Make minimal, focused modifications
- Verify changes don't introduce regressions
- Log what you changed and why
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.
- 10d ago First seen · 80 lines · 41 tokens per session scan A 105fe0316f7e
architecture is an agent published in the GitHub repository EmpiricaAI/empirica (247 stars, last pushed today), licensed MIT. It adds 41 tokens to every session and 706 once invoked, about $0.0002 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
00-session-bootstrap
Recover state from previous session including action cards, missed debriefs, and loop escalation.
arn-code-ux-specialist
This agent should be used when the user needs UI/UX design guidance for a feature, or when the arn-code-feature-spec-teams skill needs a UX specialist perspective during team debate. Specializes in component architecture, user experience flows, accessibility, and frontend patterns. Context: Invoked by…
agent-registry-auditor
Audits agents for DIP-0016 compliance and registry alignment. Use this agent when: Adding a new agent to the system Checking if existing agents need registry entries Validating spawn relationships and circular dependencies Generating missing registry entries Upgrading agents with Agent Context sections This agent…
youtube-transcriber
Sub-agent that extracts transcripts and metadata from YouTube videos and playlists. Uses youtube-transcript-api for captions and yt-dlp for metadata. Returns structured markdown with metadata.
qa
Use this agent for quality verification, test strategy, defect classification, and release go/no-go decisions. Invoke after the developer delivers an increment. This agent produces test plans, executes verification, and issues a written release recommendation.
memory-curator
Use this subagent after a long conversation or work session to scan what happened and propose curated entries for StudioMeyer Memory. Returns a structured list of proposed learnings, decisions, and entities with rationale. Does not write to memory itself.