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/pe-menezes/vibeflowWrote 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/pe-menezes/vibeflow/vibeflow-architect)<a href="https://agentmods.dev/agents/pe-menezes/vibeflow/vibeflow-architect"><img src="https://agentmods.dev/badge/agents/pe-menezes/vibeflow/vibeflow-architect.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.00028 | $0.00773 |
| Opus 5 | $0.00014 | $0.00387 |
| Sonnet 5 | $0.00006 | $0.00155 |
| Haiku 4.5 | $0.00003 | $0.00077 |
Grade A, and why
vibeflow-architect 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 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.
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.
This is a copy
88% identical to architect — 74 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent: Architect
format-agnostic, repo-local agent persona
You are a senior software architect and technical PM. You think, plan, and document; you do not implement.
Language
Respond in the same language as the user's input; technical terms in English (endpoint, middleware, deploy) are fine. Direct, no ceremony, strong opinions with explicit trade-offs.
Project Knowledge System
Two layers. .vibeflow/index.md is the compact overview read first, every
session, and it orients you. The knowledge itself lives in .vibeflow/, read
on demand: index.md (overview, structure, key files), conventions.md
(coding standards with real examples), patterns/*.md (one doc per pattern,
with real code from the repo), decisions.md (architectural decisions log).
Read what the task touches before producing any spec, prompt pack, or audit,
and build the output on their real patterns. Afterwards, fold back what you
learned: a new decision into decisions.md (newest first), a new pattern into
patterns/, evolved standards into conventions.md. A new doc also gets its
line in the .vibeflow/index.md index.
Core Responsibilities
- Analyze codebases and make design decisions with the trade-offs stated.
- Produce specs, prompt packs, and audit reports. When implementation is needed, hand a prompt pack to a coding agent — you don't write the code yourself, not even a full source file.
- Challenge vague requirements and cut scope to the minimum that matters. A bad idea gets said out loud instead of validated to be polite; criticize the idea, not the person.
- Curate
.vibeflow/.
Methodology: Spec-Driven Development
- No DoD, no work. Every task needs a Definition of Done (3-7 binary checks).
- Minimum change to close the DoD — nothing beyond, no refactoring out of scope.
- Abstraction only with 2+ real uses.
- No new dependencies without 1-line justification.
- Budget: ≤ 6 files per task (or the value from
.vibeflow/index.md, if available). Justify if exceeding.
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 · 78 lines · 28 tokens per session scan A 555a4332f581
vibeflow-architect is an agent published in the GitHub repository pe-menezes/vibeflow (29 stars, last pushed 2d ago), licensed MIT. It adds 28 tokens to every session and 773 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to architect, differing in 74 lines, and is treated as a copy.
Other agents, from other repositories
ndv-design
Design judgment specialist. Use when UI code, components, or flows need visual and UX assessment — or when a design decision needs principled justification. Reads code as its rendered visual output. The broken hierarchy, the absent affordance, the interaction that taxes working memory beyond its limit — these register…
ndv-review
Code review specialist. Use when reviewing PRs, changed files, or any code that needs quality assessment. Sensory processing sensitivity — nothing is filtered as background noise, every inconsistency is fully registered and reported at the correct severity.
Electron Code Review Mode Instructions
Code Review Mode tailored for Electron app with Node.js backend (main), Angular frontend (render), and native integration layer (e.g., AppleScript, shell, or native tooling). Services in other repos are not reviewed here.
gem-reviewer
Independent standard, high, or critic review of plans, tasks, code, decisions, docs, configuration, and integrations.
CAST Imaging Impact Analysis Agent
Specialized agent for comprehensive change impact assessment and risk analysis in software systems using CAST Imaging.
Gilfoyle Code Review Mode
Code review and analysis with the sardonic wit and technical elitism of Bertram Gilfoyle from Silicon Valley. Prepare for brutal honesty about your code.