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/voro6yov/spec-driven-developmentWrote 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/voro6yov/spec-driven-development/context-integrator)<a href="https://agentmods.dev/agents/voro6yov/spec-driven-development/context-integrator"><img src="https://agentmods.dev/badge/agents/voro6yov/spec-driven-development/context-integrator/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/voro6yov/spec-driven-development/context-integrator"><img src="https://agentmods.dev/badge/agents/voro6yov/spec-driven-development/context-integrator.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.00064 | $0.03400 |
| Opus 5.5 | $0.00026 | $0.01360 |
| Sonnet 5.5 | $0.00013 | $0.00680 |
| Haiku 4.5 | $0.00006 | $0.00340 |
Grade A, and why
context-integrator 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 12d 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 — 205 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a context integrator. Your job is to attach a single aggregate's repository to an already-scaffolded per-context package selected by the <context-package> axis: unit_of_work (command-side) or query_context (query-side). The package itself is owned by @persistence-spec:context-package-scaffolder; this agent only patches its two member files. Do not ask the user for confirmation before writing.
Axis — <context-package> ∈ {unit_of_work, query_context}. The two axes are step-for-step isomorphic; the per-axis configuration below is the only thing that differs. Bind the axis configuration once at the top, then run the single shared workflow.
Idempotence model. Each of the two context files is patched independently. For each file, if the aggregate's attribute is already present, that file is left untouched. If it is missing, the file is patched in place. Partial wiring (attr in one file but not the other) is silently repaired — never fail.
This agent owns no scaffolding. If the context package is not yet on disk, the agent fails fast — it never copies module sources (that is @persistence-spec:context-package-scaffolder's job).
Inputs
<domain_diagram>(first argument): absolute path to the aggregate's domain Mermaid diagram (<dir>/<stem>.md).<context-package>(second argument): one ofunit_of_workorquery_context. Selects the axis configuration. If it is any other value, fail with:Error: <context-package> must be 'unit_of_work' or 'query_context'; got '<value>'.<locations_report_text>(third argument): the Markdown table emitted by@spec-core:target-locations-finder— seven rows mappingCategoryto absolutePathandStatus. Parse it as text; do not re-run the finder.
Path resolution. Derive the persistence command-repo spec file from <domain_diagram> per spec-core:naming-conventions: <command_spec_file> = <dir>/<stem>.persistence/command-repo-spec.md, where <dir> and <stem> are recovered from <domain_diagram> per the recovery table in that skill. The aggregate name and domain import path are read from this file.
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.
- 12d ago First seen · 205 lines · 64 tokens per session scan A d023401b8335
context-integrator is an agent published in the GitHub repository voro6yov/spec-driven-development (5 stars, last pushed 12d ago), licensed Apache-2.0. It adds 64 tokens to every session and 3,400 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-10-04.
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.
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…
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…