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/existential-birds/amelia/12-factor-agents-analysisgit clone --depth 1 https://github.com/existential-birds/ameliaWrote 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/existential-birds/amelia/12-factor-agents-analysis)<a href="https://agentmods.dev/commands/existential-birds/amelia/12-factor-agents-analysis"><img src="https://agentmods.dev/badge/commands/existential-birds/amelia/12-factor-agents-analysis.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.00012 | $0.00654 |
| Opus 5 | $0.00006 | $0.00327 |
| Sonnet 5 | $0.00002 | $0.00131 |
| Haiku 4.5 | $0.00001 | $0.00065 |
Grade A, and why
12-factor-agents-analysis 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 5d 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
12-Factor Agents Compliance Analysis
You are performing a comprehensive compliance analysis against the 12-Factor Agents methodology.
Use the agent-architecture-analysis skill to guide this analysis.
Target Codebase
Path: $ARGUMENTS (default: current working directory)
Analysis Scope
Evaluate all 13 factors:
- Natural Language → Tool Calls - Schema-validated LLM outputs
- Own Your Prompts - Templated, versioned, externalized prompts
- Own Your Context Window - Custom context formatting, token optimization
- Tools Are Structured Outputs - Deterministic handlers, validated schemas
- Unify Execution State - Single source of truth for all state
- Launch/Pause/Resume - APIs for workflow control
- Contact Humans with Tools - Structured human contact as tool calls
- Own Your Control Flow - Custom routing, not framework defaults
- Compact Errors into Context - Self-healing with retry thresholds
- Small, Focused Agents - Narrow responsibilities, step limits
- Trigger from Anywhere - Multi-channel triggers (CLI, REST, webhooks)
- Stateless Reducer - Pure functions, no side effects
- Pre-fetch Context - Proactive context gathering
Workflow
- Use the skill - Read
.claude/skills/agent-architecture-analysis/SKILL.mdfor search patterns - Run searches - Use grep patterns from the skill for each factor
- Evaluate compliance - Strong/Partial/Weak per factor
- Document evidence - File:line references for findings
- Identify gaps - What's missing vs. 12-Factor ideal
- Provide recommendations - Actionable improvements
Output Format
Executive Summary
| Factor | Status | Key Finding |
|---|---|---|
| F1: Natural Language → Tool Calls | Strong/Partial/Weak | [Summary] |
| ... | ... | ... |
Overall: X Strong, Y Partial, Z Weak
Detailed Findings
For each factor with gaps:
- Current State: What exists
- Evidence: File:line references
- Gap: What's missing
- Recommendation: How to improve
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.
- 5d ago First seen · 83 lines · 12 tokens per session scan A 20809c33d7f4
12-factor-agents-analysis is a command published in the GitHub repository existential-birds/amelia (21 stars, last pushed 25d ago), licensed Apache-2.0. It adds 12 tokens to every session and 654 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
Hexagonal.Gatekeeper
Your role is to perform a deep, architecture-focused code review on a specific branch. You must validate that all changes strictly follow Hexagonal Architecture (Ports & Adapters) principles and align with the existing codebase patterns.
PyTest.GateKeeper
You are a Senior QA Automation Engineer with deep expertise in Python testing and the pytest framework.
new-agent
Create a new AgentShip agent using the standard 2-file pattern.
digest
Generate a daily or weekly digest of activity across all connected sources.
start
Initialize the productivity system and open the dashboard.
update
Sync tasks and refresh memory from your current activity.