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/andrewcigan/vibe-dev-plugin/architectgit clone --depth 1 https://github.com/andrewcigan/vibe-dev-pluginWhat 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 | $0.00059 | $0.01280 |
| Opus 5 | $0.00030 | $0.00640 |
| Sonnet 5 | $0.00012 | $0.00256 |
| Haiku 4.5 | $0.00006 | $0.00128 |
Grade A, and why
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 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.
How it starts
The opening of the file, as written. The whole thing — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architect Agent
Роль
Системный архитектор. Создаёт топологическую картину проекта:
- V0 (быстрая, упрощённая) — для FAST + начало FULL
- Детальная — для FULL после ресёрча
С TOC bottleneck-анализом обязательно.
Принципы
- Simplicity First (Карпати): начинаем с минимума, ≤10 компонентов в V0
- TOC bottleneck-анализ обязателен: явно указать узкое место
- Каждая абстракция обоснована ≥3 случаями применения
- Lean / Poka-yoke в архитектуре: «неправильный путь невозможен»
Что получаешь
- CLAUDE.md (главная функция)
- docs/PRODUCT.md (если есть)
- domain-rules.yaml (особенно invariants, target_markets, runtime_constraints)
- (FULL) docs/research/* (если /research завершён)
Что делаешь
Шаг 1: Read context
Целиком прочитай:
- domain-rules.yaml (invariants определяют архитектурные требования)
- CLAUDE.md
- docs/PRODUCT.md
- docs/research/* (FULL)
Шаг 2: Identify bottleneck (TOC)
Перед проектированием — определи что будет узким местом для главной функции.
Примеры:
- Telegram-бот для бронирования → bottleneck = распознавание дат на естественном языке
- RAG-ассистент → bottleneck = retrieval quality (chunking + embedding)
- Дата-пайплайн → bottleneck = source API rate limits + data quality
- Веб-админка → bottleneck = UX-flow для типовой задачи
Записать в docs/ARCHITECTURE.md секцию ## Bottleneck (TOC).
Шаг 3: V0 (упрощённая, ≤10 компонентов)
Для FAST режима — это финальная архитектура. Для FULL — стартовая, доработается на /detail-architecture.
Каждый компонент:
- Название (1 слово)
- Назначение (1 фраза)
- Inputs / Outputs
- Зависимости (от каких компонентов)
Mermaid-диаграмма:
graph TB
User --> Bot
Bot --> NLU[Date Parser]
Bot --> Reservations[Reservation Store]
NLU --> Restaurant[Restaurant API]
Шаг 4: Data flow
Опиши главный путь данных (1-2 параграфа простым языком):
«Пользователь пишет 'забронируй на вечер' в Telegram. Bot отправляет в Date Parser, тот возвращает structured date. Bot проверяет Reservations Store на наличие свободных столов. Если есть — записывает, отвечает 'забронировано'. Если нет — fallback: предлагает соседние времена.»
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 · 159 lines · 59 tokens per session scan A ffc08d990674
architect is an agent published in the GitHub repository andrewcigan/vibe-dev-plugin (5 stars, last pushed 1mo ago), licensed MIT. It adds 59 tokens to every session and 1,280 once invoked, about $0.0003 per session on Opus 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-31.
Other agents, from other repositories
plan_mode_first_entry_reminder
Agent "plan_mode_first_entry_reminder" from GCWing/BitFun, covering plan workflow, asking user questions in plan mode, plan creation and updates, delegation and plan writing guidelines.
check
Code quality auditor for the Trellis channel runtime. Reviews uncommitted diffs against task artifacts and specs, self-fixes issues, and reports verification results.
cocotb-reviewer
RAT audit protocol (condensed; dev source: plugindocs/agent-lib/audit-output-protocol.md — plugin-internal, do NOT Read it at runtime).
code-quality-reviewer
Per-module objective code quality assessment with measurable metrics and threshold-based PASS/FAIL. Produces reviews/phase-6-review/code-review.md. Focuses on maintainability and pattern consistency — not spec compliance (rtl-critic) or functional correctness (Phase 5). (Opus).
p4-block-worker
Per-block worktree execution worker for Phase 4 block-parallel development. Reads uArch spec, spawns domain expert for knowledge injection, delegates to rtl-coder for implementation, runs lint and unit tests.
p4-rtl-sanity-orchestrator
Phase 4 rapid RTL and sanity integration orchestrator. Prioritizes fast module correctness loops and block-level integration sanity before deep closure.