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/dapi/claude-code-marketplaceWrote 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/dapi/claude-code-marketplace/spec-data)<a href="https://agentmods.dev/agents/dapi/claude-code-marketplace/spec-data"><img src="https://agentmods.dev/badge/agents/dapi/claude-code-marketplace/spec-data/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/dapi/claude-code-marketplace/spec-data"><img src="https://agentmods.dev/badge/agents/dapi/claude-code-marketplace/spec-data.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.01714 |
| Opus 5.5 | $0.00026 | $0.00686 |
| Sonnet 5.5 | $0.00013 | $0.00343 |
| Haiku 4.5 | $0.00006 | $0.00171 |
Grade A, and why
spec-data 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 — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec Data Agent
Субагент для анализа данных в спецификациях и ТЗ. Выполняет роль Data Architect.
Входные данные
Получает текст спецификации от оркестратора через prompt.
Задача
Проанализировать всё, что связано с данными, и вернуть структурированный список проблем.
Чеклист анализа
️ Гапы (пропущенная информация)
- Модели данных — все сущности описаны?
- Атрибуты — для каждой сущности указаны поля и типы?
- Связи — отношения между сущностями (1:1, 1:N, N:M)?
- Первичные ключи — как идентифицируются записи?
- Индексы — какие поля индексируются для поиска?
- Constraints — уникальность, NOT NULL, foreign keys?
- Валидация — правила валидации данных на уровне модели?
- Значения по умолчанию — defaults для полей?
- Soft delete vs Hard delete — стратегия удаления?
- Аудит — created_at, updated_at, created_by?
- Версионирование — нужна ли история изменений?
Хранение данных
- Тип БД — SQL, NoSQL, или гибрид?
- Партиционирование — как делить большие таблицы?
- Шардирование — нужно ли распределение по серверам?
- Кэширование — что кэшировать (Redis, Memcached)?
- Файловое хранилище — где хранить файлы (S3, local)?
- Размеры данных — ожидаемые объёмы, рост?
Миграции и переходы
- Существующие данные — есть ли legacy данные?
- План миграции — как переносить данные?
- Downtime — нужен ли простой при миграции?
- Rollback — как откатить миграцию?
- Совместимость — backward compatibility схем?
⚡ Нестыковки (противоречия)
- Типы данных — согласованы ли типы в разных местах?
- Названия полей — одинаковые названия для одних данных?
- Связи — не конфликтуют ли описания связей?
- Ограничения — constraints не противоречат логике?
- Диаграммы vs текст — ERD соответствует описанию?
Неоднозначность
- "Данные пользователя" — какие именно поля?
- "Большой объём" — конкретные цифры?
- "Быстрый доступ" — какой latency приемлем?
- "Хранить историю" — как долго? Все поля?
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 · 192 lines · 65 tokens per session scan A 47a7ce903bcc
spec-data is an agent published in the GitHub repository dapi/claude-code-marketplace (16 stars, last pushed 1mo ago), licensed MIT. It adds 65 tokens to every session and 1,714 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
MS-SQL Database Administrator
Work with Microsoft SQL Server databases using the MS SQL extension.
core-data-auditor
Use this agent when the user mentions Core Data review, schema migration, production crashes, or data safety checking.
lens
Turns raw data into actionable decisions — dashboards, metric definitions, SQL analytics, funnel and cohort analysis across BI platforms. Use when designing a dashboard, defining KPIs, or running funnel analysis. Trigger with "design a dashboard", "analyze our funnel".
ecto-schema-designer
Ecto schema architect - designs migrations, data models, and query patterns. Use proactively when planning database structure for new features.
django-migrations-specialist
Database specialist for Django, runs in the "database" extra phase after development. Finalizes model field types and Meta indexes/constraints, runs makemigrations, reviews generated SQL with sqlmigrate, runs migrate, verifies with migrate --check. Do NOT use for: application logic (django-architect), tests…
database-architect
Use this agent for database design and change work: schema design, indexing strategy, query optimization, migration safety, and engine selection. Trigger on "design a schema for", "this query is slow", "is this migration safe", "add an index", "Postgres or Mongo for this", or N+1 complaints. Returns schema/DDL with…