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/bdfinst/agentic-dev-teamWrote 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/bdfinst/agentic-dev-team/twelve-factor-audit)<a href="https://agentmods.dev/agents/bdfinst/agentic-dev-team/twelve-factor-audit"><img src="https://agentmods.dev/badge/agents/bdfinst/agentic-dev-team/twelve-factor-audit/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/bdfinst/agentic-dev-team/twelve-factor-audit"><img src="https://agentmods.dev/badge/agents/bdfinst/agentic-dev-team/twelve-factor-audit.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.00023 | $0.00570 |
| Opus 5.5 | $0.00009 | $0.00228 |
| Sonnet 5.5 | $0.00005 | $0.00114 |
| Haiku 4.5 | $0.00002 | $0.00057 |
Grade A, and why
twelve-factor-audit 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 1mo 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 — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Twelve-Factor Audit
Output JSON:
{"status": "pass|warn|fail|skip", "issues": [{"severity": "error|warning|suggestion", "confidence": "high|medium|none", "file": "", "line": 0, "message": "", "suggestedFix": ""}], "summary": ""}
Status: pass=12-factor compliant, warn=violations detected, fail=critical anti-patterns Severity: error=security or reliability risk, warning=operational concern, suggestion=best practice Confidence: high=mechanical (hardcoded config, missing health check); medium=design judgment; none=infrastructure context needed
Context needs: project-structure
Activates when
Service/API project detected: has Dockerfile, server entry point, or cloud config (Kubernetes manifests, cloud formation, etc.).
Skip
Return skip when project is a library, CLI tool, or static site without a server component.
Detect
| Factor | What to check |
|---|---|
| I. Codebase | Single repo per service? Multiple deploys from one codebase? |
| II. Dependencies | All deps declared (lockfile committed)? No system-level assumptions? |
| III. Config | Config in env vars? No hardcoded URLs, credentials, or feature flags in code? |
| IV. Backing services | Database, cache, queue treated as attached resources? Connection strings via env? |
| V. Build, release, run | Strict separation? Build produces artifact, release combines with config, run executes? |
| VI. Processes | Stateless processes? No sticky sessions? No local filesystem for shared state? |
| VII. Port binding | Self-contained via port binding? Not relying on runtime injection into a webserver? |
| VIII. Concurrency | Scale out via process model? No in-memory state that prevents horizontal scaling? |
| IX. Disposability | Fast startup? Graceful shutdown? SIGTERM handling? |
| X. Dev/prod parity | Same backing services in dev/prod? No "works on my machine" patterns? |
| XI. Logs | Treat logs as event streams? Write to stdout, not files? No log file rotation in app? |
| XII. Admin processes | One-off tasks as scripts? Database migrations as code? Not manual SQL? |
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.
- 1mo ago First seen · 50 lines · 23 tokens per session scan A 6ff2f15e54c5
twelve-factor-audit is an agent published in the GitHub repository bdfinst/agentic-dev-team (295 stars, last pushed 4d ago), licensed MIT. It adds 23 tokens to every session and 570 once invoked, about $0.0001 per session on Opus 5.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-09-05.
Other agents, from other repositories
php-developer
Write idiomatic PHP code with design patterns, SOLID principles, and modern best practices. Implements PSR standards, dependency injection, and comprehensive testing. Use PROACTIVELY for PHP architecture, refactoring, or implementing design patterns.
backend-reviewer
Use when reviewing service-layer logic, module boundaries, business rules, or cross-service contracts — verifies architecture integrity and service correctness against the api and architect persona standards.
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…
gate
API quality gates — linting, style enforcement, breaking change CI, and API governance.
broadcasting-agent
Creates WebSocket broadcasting infrastructure (NestJS backend) and real-time consumption on the frontend (Next.js or React). Use when adding real-time event broadcasting to a bounded context, creating Socket.IO gateways, or implementing frontend event listeners. Dispatched after infrastructure layer is complete.
dotnet-architecture-reviewer
Reviews a .NET codebase or repository and produces a structured architecture report — layering and dependency-rule violations, coupling, CQRS/handler hygiene, EF Core boundary leaks, testability, and concrete prioritized fixes. Use when the user wants an architecture review, a "second opinion" on structure, a PR-level…