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 skills add Vimalk0703/shipworthy --skill twelve-factor-appgit clone --depth 1 https://github.com/Vimalk0703/shipworthyWrote 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/skills/vimalk0703/shipworthy/twelve-factor-app)<a href="https://agentmods.dev/skills/vimalk0703/shipworthy/twelve-factor-app"><img src="https://agentmods.dev/badge/skills/vimalk0703/shipworthy/twelve-factor-app.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.00044 | $0.02789 |
| Opus 5 | $0.00022 | $0.01394 |
| Sonnet 5 | $0.00009 | $0.00558 |
| Haiku 4.5 | $0.00004 | $0.00279 |
Grade A, and why
twelve-factor-app scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- [ ] No dependency is fetched from an unversioned URL or a curl pipe to shell. How it starts
The opening of the file, as written. The whole thing — 278 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Twelve-Factor App (Modern 2025 Interpretation)
Core Principle
The Twelve-Factor App methodology describes how to build software-as-a-service applications that are portable, scalable, and operationally mature. Originally written in 2011 by Heroku engineers, these principles remain foundational -- but the implementation details have evolved with containers, Kubernetes, and serverless.
I. Codebase -- One Codebase, One App
Principle: One codebase tracked in version control, many deploys (staging, production, etc.).
Modern interpretation:
- One Git repository per deployable service (monorepo is acceptable if each service has clear boundaries and independent deployment).
- The same codebase is deployed to dev, staging, and production. Differences between environments come from configuration, not code branches.
- Feature flags control behavior differences, not separate codebases.
Actionable checks:
- Every service has exactly one repository (or one clear path in a monorepo).
- There is no "production branch" that diverges from main -- main is always deployable.
- Environment-specific behavior is controlled by config or feature flags, never by code branching.
II. Dependencies -- Explicitly Declare and Isolate
Principle: Never rely on system-level packages. Declare all dependencies explicitly and isolate them.
Modern interpretation:
- Use lockfiles:
package-lock.json,poetry.lock,go.sum,Cargo.lock. - Container images pin base image versions:
FROM node:20.11.0-slim, notFROM node:latest. - Do not install tools globally in CI/CD -- declare them in the project.
Actionable checks:
- A lockfile exists and is committed to version control.
- Dockerfiles use pinned base image digests or exact version tags.
-
npm install/pip install/go buildworks from a clean clone with no manual steps. - No dependency is fetched from an unversioned URL or a curl pipe to shell.
III. Config -- Store Config in the Environment
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 · 278 lines · 44 tokens per session scan A 498a8642076d
twelve-factor-app is a skill published in the GitHub repository Vimalk0703/shipworthy (7 stars, last pushed 5mo ago), licensed MIT. It adds 44 tokens to every session and 2,789 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
memstack-deployment-docker-setup
Use this skill when the user says 'Docker', 'Dockerfile', 'docker-compose', 'containerize', 'docker-setup', or needs to containerize an application with optimized Docker images and compose configurations. Do NOT use for serverless or static site deployments.
memstack-deployment-railway-deploy
Use this skill when the user says 'deploy to Railway', 'Railway setup', 'railway-deploy', or needs to deploy a Node.js, Python, or Docker application to Railway with environment variables, custom domains, and monitoring. Do NOT use for Netlify, Vercel, or Hetzner deployments.
deploy-gen
Generate deployment configurations (Docker, Kubernetes) for the current project.
docker-devops
Docker/K8s: Dockerfile, multi-stage, compose, manifests, Helm. Triggers: Docker, Dockerfile, container, Kubernetes, k8s, compose, Helm, pod.
health
Service/infra health via liveness/readiness checks, resource usage, quick diagnostics. Triggers: health check, services up, system status, infra health, degraded service.
event-driven-architecture
Kafka, RabbitMQ, SQS/SNS, event sourcing, CQRS, saga patterns, dead letter queues, and idempotency. Use when designing asynchronous systems, implementing message-driven workflows, or building event streaming pipelines.