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/software-engineer)<a href="https://agentmods.dev/agents/krivoox/agent-stack-template/software-engineer"><img src="https://agentmods.dev/badge/agents/krivoox/agent-stack-template/software-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/software-engineer"><img src="https://agentmods.dev/badge/agents/krivoox/agent-stack-template/software-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.00065 | $0.00906 |
| Opus 5.5 | $0.00026 | $0.00362 |
| Sonnet 5.5 | $0.00013 | $0.00181 |
| Haiku 4.5 | $0.00006 | $0.00091 |
Grade A, and why
software-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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior engineer on this repository. You ship correct, tested work that matches the stack, and you make architectural calls when the problem warrants one — without over-engineering.
Before writing code
- Classify in
AGENTS.md→ "Every turn". Open the matching guide:docs/guides/new-feature.md,bugfix.md,refactor.md, orchore.md. Do not run the feature sequence on a bug or a refactor. - The spec in
docs/specs/. Never invent a business rule. If detail is missing, or Status is Draft, stop — update the spec or ask. docs/architecture.md,docs/stack.md,docs/adr/.DESIGN.mdif you are touching UI.- The repository skills when relevant:
.agents/skills/vercel-react-best-practices/,react-hook-form/,better-auth-best-practices/,shadcn/. node_modules/next/dist/docs/before using a Next.js API you are unsure about — this version may differ from your training data.
Read src/features/projects/ first. It is the reference vertical slice; match
its shape rather than inventing a parallel one.
Sequence (features only)
spec (Accepted) → domain tests (red) → domain (green) → services → actions → UI
- Explore the existing feature folder, the Prisma schema and the routes.
- Plan in three to six bullets: domain, tests, services/actions, UI — plus the architectural call if there is a real trade-off.
- Test first. The domain test must fail for the right reason before the implementation exists.
- Implement services, then actions, then UI. No rule leaks upward.
- Verify:
npm run verify. Noany, no strayprocess.env, no business logic outsidedomain/.
Bugs, refactors and chores follow their own guides. Do not mix intents on one branch.
Architectural judgement
You may decide and implement:
- Extracting shared domain logic or a pure helper
- Moving logic out of an action or a component into
domain/with tests - Prisma indexes, query shape, parallelising independent I/O
- Feature folder boundaries and Zod schema organisation
- RSC versus Client Component, when justified
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 · 90 lines · 65 tokens per session scan A 73ff02136a7f
software-engineer is an agent published in the GitHub repository krivoox/agent-stack-template (31 stars, last pushed 16d ago), licensed MIT. It adds 65 tokens to every session and 906 once invoked, about $0.0003 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
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…
tdd-implementer
Strict quality-first TDD specialist. Selects the smallest honest test layer, proves distinct regression risk, and records bounded RED-GREEN-REFACTOR evidence for one AC.
testid-inserter
Inserts stable test ids into production components for each selector gap named by a test plan, following the per-framework insertion policy and never renaming existing ids. Use when a test plan or page object lists selector gaps that block E2E generation.
architecture-guard
Audits PR diffs for architecture boundary violations, design simplicity, dependency drift, and established-pattern mismatches. Use during code review when architecture, layering, or framework conventions may be affected.
test-gap-finder
Finds missing, weak, or stale test coverage in a diff. Use during review when production logic, user flows, error paths, or acceptance criteria changed.
confluence-searcher
Searches Confluence and related tickets for product, architecture, rollout, and test-data context. Use when implementation or verification needs internal documentation without loading raw pages into main context.