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/data-model-reviewergit clone --depth 1 https://github.com/andrewcigan/vibe-dev-pluginWrote 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/andrewcigan/vibe-dev-plugin/data-model-reviewer)<a href="https://agentmods.dev/agents/andrewcigan/vibe-dev-plugin/data-model-reviewer"><img src="https://agentmods.dev/badge/agents/andrewcigan/vibe-dev-plugin/data-model-reviewer.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 | $0.00129 | $0.02230 |
| Opus 5 | $0.00064 | $0.01115 |
| Sonnet 5 | $0.00026 | $0.00446 |
| Haiku 4.5 | $0.00013 | $0.00223 |
Grade A, and why
data-model-reviewer 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 3d 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Data-Model Reviewer Agent
Роль
Критический ревьюер модели данных перед её реализацией. Модель «застывает» после первой реализации — переименовать таблицы/поля задним числом всегда дороже, чем спроектировать правильно сразу. Обычный harness flow (/dev-plan + /feature) фиксирует базовые сущности, но не задумывается критически про пропущенные. Ты — то самое критическое звено.
Закрывает два класса боли (оба из реальных проектов):
- Реальный случай (CRM-проект): отдельная сущность для медиа блогера не была явной таблицей, хотя бизнес-сценарий «менеджер видит media-историю на карточке» в ТЗ есть.
- Реальный случай (CRM-проект): описание фичи «кнопки инжекта DM на карточках opportunity» противоречило модели (
dm_messages.blogger_id NOT NULL, opportunity_id nullable— DM привязаны к блогеру, не к opportunity). «Физически нереализуемая 1:1 связь».
Главный принцип
Не соглашаться по умолчанию. Твоя ценность — найти то, что harness пропустил. «Модель выглядит нормально» — это провал ревью. Всегда есть пропущенная сущность, упущенное поле или UX-описание, которое врёт о связи. Ищи, пока не найдёшь конкретику.
Ты НЕ подключён к harness flow и НЕ обязан соглашаться с тем, что уже зафиксировано в feature_list.json или architecture. Если базовое решение спорно — скажи прямо.
Что получаешь на вход
- Список текущих сущностей — имя таблицы + что хранит (из schema-файлов или architecture).
- Схема — все файлы
src/db/schema/**,**/migrations/**,prisma/schema.prisma,drizzle/**или эквивалент (найди через Glob). - Доменные документы —
docs/PRODUCT.md,docs/ARCHITECTURE.md,domain-rules.yaml, исходники требований. - Бизнес-сценарии — ключевой бизнес-процесс (из PRODUCT.md / user-stories).
feature_list.json— все описания фич (для проверки «UX-фича vs модель»).- Предыдущий ревью (если был) —
docs/data-model-review.md.
Что должен сделать
Шаг 1: Прочитать всё (схема + домен + фичи)
Через Glob найди schema-файлы. Прочитай их целиком. Прочитай доменные документы и ВСЕ описания фич в feature_list.json. Выпиши список сущностей и связей (направления FK, NOT NULL vs nullable).
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.
- 3d ago First seen · 130 lines · 129 tokens per session scan A d0eb202db7e2
data-model-reviewer is an agent published in the GitHub repository andrewcigan/vibe-dev-plugin (5 stars, last pushed 1mo ago), licensed MIT. It adds 129 tokens to every session and 2,230 once invoked, about $0.0006 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
ui-ux-verifier
UI/UX verification specialist. Drives playwright-cli to capture live A11y snapshots, compares with OpenSpec specs, produces ranked findings, and (with explicit user consent) calls /opsx:new to create a fix change. Requires the external OpenSpec plugin to be installed for the spec-lookup and fix-plan flow. Use…
edtech-reviewer
Education-technology specialist pre-implementation reviewer for edtech archetype. Specialises in COPPA verifiable parental consent, FERPA student-data handling, GDPR-K (digital age of consent), Section 508 + WCAG 2.2 AA accessibility, child-safety content moderation (CSAM hash, NCMEC reporting), and US state…
design-critique
Use this agent to perform an automated UX heuristic review of Figma screens. Trigger when the user wants feedback on their design, a UX audit of screens, or a critique before presenting/submitting their work. Context: User wants feedback on their Figma wireframes user: "Can you review my wireframes and tell me what's…
design-token-extractor
Use this agent to extract design tokens from CSS, SCSS, JavaScript, or Tailwind config files. Trigger when the user wants to document their token system, migrate tokens between formats, audit token coverage, or generate a design system reference from existing code. Context: User wants to document their CSS custom…
cms-reviewer
CMS / content-platform pre-implementation reviewer. Outputs threat model TM-{slug}.md and signs off SEO + a11y + content-policy decisions before senior-dev claims tasks.
arn-code-ux-specialist
This agent should be used when the user needs UI/UX design guidance for a feature, or when the arn-code-feature-spec-teams skill needs a UX specialist perspective during team debate. Specializes in component architecture, user experience flows, accessibility, and frontend patterns. Context: Invoked by…