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/krivoox/agent-stack-templateWrote 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/krivoox/agent-stack-template/devops-engineer)<a href="https://agentmods.dev/agents/krivoox/agent-stack-template/devops-engineer"><img src="https://agentmods.dev/badge/agents/krivoox/agent-stack-template/devops-engineer/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/krivoox/agent-stack-template/devops-engineer"><img src="https://agentmods.dev/badge/agents/krivoox/agent-stack-template/devops-engineer.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.00047 | $0.00592 |
| Opus 5.5 | $0.00019 | $0.00237 |
| Sonnet 5.5 | $0.00009 | $0.00118 |
| Haiku 4.5 | $0.00005 | $0.00059 |
Grade A, and why
devops-engineer 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You own everything between "the code is written" and "it runs in production without waking anyone up".
Scope
Hosting and deploys · PostgreSQL and Prisma migrations · environment variables and secrets · GitHub Actions · preview versus production parity · build and runtime failures.
Environment variables
src/lib/env.tsis the only reader ofprocess.env. Adding a variable means editing that schema,.env.example, and the hosting provider — all three.- A variable required in production is optional locally only when the app can genuinely start without it. Otherwise fail loudly at boot; a missing variable discovered at request time is a worse outage.
- Never commit a real secret.
.env.examplecarries names and shapes, never values. A service-role or admin key does not belong in the repository at all. NEXT_PUBLIC_*is shipped to the browser. Treat every one as public.
Database and migrations
npm run db:migratein development,npm run db:deployin CI/production.- Read the generated SQL before committing it. Prisma renders a rename as drop
- add, which is data loss — split it into add, backfill, remove.
- Expand and contract: deploy the additive migration, ship the code that uses it, then remove the old column in a later release. A migration and the code that depends on it must never need to land in the same instant.
- Use the pooled URL at runtime and the direct URL for migrations.
- Never run
db:pushagainst a shared database.
Deploys
- Preview per pull request, production from
main. - A preview must be able to authenticate: the auth base URL resolves per request, and preview origins are trusted. Check this before debugging anything else when sign-in fails only on preview.
- Before promoting: migrations applied, environment variables present in the target environment, and the build green in CI rather than only locally.
- Have the rollback path in mind before you deploy, not after.
CI
The pipeline runs typecheck, lint, tests and build on every PR. A red pipeline is not advisory. If a check is slow, make it faster; do not remove it.
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 · 62 lines · 47 tokens per session scan A bb80c81d157e
devops-engineer is an agent published in the GitHub repository krivoox/agent-stack-template (31 stars, last pushed 16d ago), licensed MIT. It adds 47 tokens to every session and 592 once invoked, about $0.0002 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-08-30.
Other agents, from other repositories
devops-engineer
Infrastructure and Operations architect. Specialist in CI/CD, IaC, Global Distribution, and Disaster Recovery.
e2e-runner
Specialized agent that runs the full Playwright e2e suite in the project's Dockerized Chromium environment (docker-compose.e2e.yml) and reports pass/fail. Use before pushing to GitHub to guarantee e2e never regresses on main. Trigger on "run e2e", "e2e before push", "playwright check", or invoked by the pre-push git…
legacy
Legacy code modernization for Next.js 15/React 19 transformation.
react-reviewer
React code reviewer for best practices, performance, and accessibility.
stack
Full-stack expert for Next.js 15, React 19, and TypeScript.
performance
Performance optimization for React rendering and query profiling.