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 agents/f-amine/vibe-stack/rolesgit clone --depth 1 https://github.com/f-amine/vibe-stackWrote 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/f-amine/vibe-stack/roles)<a href="https://agentmods.dev/agents/f-amine/vibe-stack/roles"><img src="https://agentmods.dev/badge/agents/f-amine/vibe-stack/roles.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.00000 | $0.00286 |
| Opus 5 | $0.00000 | $0.00143 |
| Sonnet 5 | $0.00000 | $0.00057 |
| Haiku 4.5 | $0.00000 | $0.00029 |
Grade A, and why
roles 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 2d 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.
What it actually says
Recommended agent roles for the autonomous loop
When spawning ruflo hive-mind spawn, request these 6 specialised workers:
| Role | Skill focus |
|---|---|
architect |
/improve-codebase-architecture, /grill-with-docs, ADR drafting |
coder |
/tdd, feature implementation, refactor execution |
reviewer |
/review, /security-review, code quality, ADR adherence |
tester |
Test gaps, e2e, regression test creation |
triager |
/triage, issue labelling, acceptance-criteria gathering |
researcher |
Web search, library docs, dep upgrades, releasing notes |
Optional 7th if you allow it:
| docs-writer | Updates CONTEXT.md, ADRs, README, docs/ when behaviour changes |
Boundaries per role
codermay write code, never DELETE files, never bump deps, never touchpackages/db/drizzle/migrations withoutreviewerapproval.reviewermay comment on PRs but onlyarchitectmay merge changes affectingCONTEXT.mdordocs/adr/.testermay add tests but never modify production source.researcheris read-only (no writes to repo, only Slack/PR comments).
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.
- 2d ago First seen · 24 lines · 0 tokens per session scan A 45924be73f70
roles is an agent published in the GitHub repository f-amine/vibe-stack (21 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 286 tokens. 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-03.
Other agents, from other repositories
stack-architect
Designs a valid, coherent Better-T-Stack configuration from a high-level product description, then plans and (on confirmation) generates it through the Better-T-Stack MCP server. Use when stack choices are open-ended and you want a recommended end-to-end type-safe setup.
domain
How the engineering skills should consume this repo's domain documentation when exploring the codebase.
issue-tracker
Issues and PRDs for this repo live in GitHub Issues for AmanVarshney01/create-better-t-stack. Use the gh CLI for issue operations.
software-engineer
Implements Accepted specs end to end, fixes bugs, and refactors without changing behaviour. Use proactively for new features once the spec is Accepted, domain/Prisma/Server Action changes, and technical approach decisions. Do not use when the request is a problem without a spec — that is product-manager.
code-reviewer
Reviews a change against this repository's layer, tenancy, security and testing contracts. Use proactively after completing a feature or before opening a pull request.
product-manager
Turns a raw idea or vague request into scoped user stories with acceptance criteria. Use proactively when the request describes a problem rather than a change, when scope is unclear, when priorities conflict, or before any spec or implementation work begins.