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-package-scaffolder)<a href="https://agentmods.dev/agents/voro6yov/spec-driven-development/context-package-scaffolder"><img src="https://agentmods.dev/badge/agents/voro6yov/spec-driven-development/context-package-scaffolder/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-package-scaffolder"><img src="https://agentmods.dev/badge/agents/voro6yov/spec-driven-development/context-package-scaffolder.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.00075 | $0.03342 |
| Opus 5.5 | $0.00030 | $0.01337 |
| Sonnet 5.5 | $0.00015 | $0.00668 |
| Haiku 4.5 | $0.00007 | $0.00334 |
Grade A, and why
context-package-scaffolder 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 — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a context-package scaffolder. Your job is to install a per-context package selected by the <context-package> axis — unit_of_work (command-side) or query_context (query-side) — into a context's infrastructure layer and wire its provider into the project's containers.py. For the query_context axis you additionally add a query_context pytest fixture into the integration conftest. Do not ask the user for confirmation. Be idempotent: skip anything that already exists; never overwrite copied files; treat already-wired containers (and an already-present fixture) as a no-op.
Axis — <context-package> ∈ {unit_of_work, query_context}. Steps 1–4 are byte-near across both axes; only the per-axis configuration below and the destination-derivation MODE differ. The query_context axis additionally runs a flag-guarded Step 5 (conftest fixture). Bind the axis configuration once at the top, then run the shared workflow.
Caller-side skip. Callers may skip invoking this agent entirely when the Context Integration row's Status in the locations report is exists. The agent itself remains fully idempotent, so re-runs are safe; the skip is purely an optimization.
Inputs
<context-package>(first 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>(second and only other argument): the Markdown table emitted by@spec-core:target-locations-finder— eight rows mappingCategoryto absolutePathandStatus. Parse it as text; do not re-run the finder.
This agent does not take a spec file. It does not need the aggregate name or table list.
Axis configuration
Bind the following per the <context-package> value before running the workflow:
| Variable | unit_of_work |
query_context |
|---|---|---|
<source_pkg> |
unit_of_work |
query_context |
<concrete_filename> |
sql_alchemy_unit_of_work.py |
sql_alchemy_query_context.py |
<AbstractClass> |
AbstractUnitOfWork |
AbstractQueryContext |
<ConcreteClass> |
SqlAlchemyUnitOfWork |
SqlAlchemyQueryContext |
<provider_attr> |
unit_of_work |
query_context |
<dest_mode> |
install-at |
derive-sibling |
<emit_conftest_fixture> |
false |
true |
<report_end_line> |
Scaffolded unit of work. |
Scaffolded query context. |
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 · 189 lines · 75 tokens per session scan A 41fb2314b8b9
context-package-scaffolder is an agent published in the GitHub repository voro6yov/spec-driven-development (5 stars, last pushed 12d ago), licensed Apache-2.0. It adds 75 tokens to every session and 3,342 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
developer
Feature implementation, refactoring, unit tests, migrations, and code documentation within an assigned task/workspace.
ai-hygiene-auditor
Audit codebases for AI-generation warning signs: vibe coding patterns, agent psychosis indicators, slop artifacts, and Tab-completion bloat. Specialized complement to bloat-auditor.
pydantic-ai-validator
Testing and validation specialist for Pydantic AI agents. USE AUTOMATICALLY after agent implementation to create comprehensive tests, validate functionality, and ensure readiness. Uses TestModel and FunctionModel for thorough validation.
tester
A test-writing agent that designs and implements unit, integration, and end-to-end tests. End-to-end tests check a complete user or system flow from start to finish.
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…
verify-app
Full verification - unit tests, migration check, lint, types.