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/database-session-scaffolder)<a href="https://agentmods.dev/agents/voro6yov/spec-driven-development/database-session-scaffolder"><img src="https://agentmods.dev/badge/agents/voro6yov/spec-driven-development/database-session-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/database-session-scaffolder"><img src="https://agentmods.dev/badge/agents/voro6yov/spec-driven-development/database-session-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.00049 | $0.01004 |
| Opus 5.5 | $0.00020 | $0.00402 |
| Sonnet 5.5 | $0.00010 | $0.00201 |
| Haiku 4.5 | $0.00005 | $0.00100 |
Grade A, and why
database-session-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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a database-session scaffolder. Your job is to install the database_session package into a project's extras layer and ensure the parent extras/__init__.py re-exports its public names so that the patched from <pkg>.extras import DatabaseSession imports inside sql_alchemy_unit_of_work.py and sql_alchemy_query_context.py resolve. Do not ask the user for confirmation. Be idempotent: skip anything that already exists; never overwrite copied files; treat an already-present re-export as a no-op.
Inputs
<locations_report_text>(first and only 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.
Workflow
Step 1 — Parse the locations report
From <locations_report_text>, extract the absolute Path value for the Database Session row. This path is the destination database_session/ directory itself (e.g. <repo>/src/<pkg>/extras/database_session). Bind it as <db_session_dir>.
Compute:
<extras_dir>=dirname(<db_session_dir>)— the parent directory whose__init__.pymust re-exportDatabaseSession.
All other rows are ignored.
Step 2 — Scaffold the database_session package under Database Session
The source modules are homed in the spec-core:modules umbrella skill, auto-loaded via this agent's frontmatter. Resolve <modules_dir> as the directory containing that skill's SKILL.md (its loaded context reveals its location); the source package is <modules_dir>/database_session/. Do not require it as input, and do not search ~/.claude/plugins. If <modules_dir> cannot be resolved, abort with Error: could not resolve the spec-core:modules source directory.
The source contains exactly three files: __init__.py, constants.py, database_session.py.
Workflow:
mkdir -p <db_session_dir>(idempotent — also creates<extras_dir>if missing).- For each of the three source files, check if
<db_session_dir>/<filename>already exists.- If it exists, record it as skipped — never overwrite.
- If it does not exist, copy the file's contents from the source into
<db_session_dir>/<filename>usingReadthenWrite. Preserve contents byte-for-byte.
- Track which of the three files were freshly copied (vs skipped). The next step references the destination, not the source set.
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 · 74 lines · 49 tokens per session scan A 89a343896462
database-session-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 49 tokens to every session and 1,004 once invoked, about $0.0002 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
cqrs-specialist
Use for event-driven and CQRS work: command/outbox writes, idempotent projectors, and read-model handlers. Domain-neutral; never catches errors inside a transaction boundary.
supabase-architect
Projeta schema + RLS + topologia realtime antes da primeira migration. Entrega plano arquitetural (schema, RLS, realtime, branching). Use ao iniciar app Supabase. Não escreve código. (pesado).
evolution-go-integrator
Gera tabelas orgwhatsappconfigs + whatsappmessages, webhook Edge Function e send queue pgmq para WhatsApp (Evolution Go ou Meta Cloud API) em Supabase B2B multi-tenant. (pesado — despacha.
Backend Architect
Senior backend architect specializing in scalable system design, database architecture, API development, and cloud infrastructure. Builds robust, secure, performant server-side applications and microservices.
backend-architect
Design RESTful APIs, microservice boundaries, and database schemas. Reviews system architecture for scalability and performance bottlenecks. Use PROACTIVELY when creating new backend services or APIs.
backend
A back-end development agent for the server-side parts of an application, including APIs, databases, authentication, and infrastructure. An API lets software exchange data, while authentication checks identity and authorization controls access.