Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add openplanr/planr-pipeline/plugin install planr-pipelineWrote 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/openplanr/planr-pipeline/entity-scaffold-agent)<a href="https://agentmods.dev/agents/openplanr/planr-pipeline/entity-scaffold-agent"><img src="https://agentmods.dev/badge/agents/openplanr/planr-pipeline/entity-scaffold-agent.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.1 | $0.00000 | $0.00425 |
| Opus 5 | $0.00000 | $0.00212 |
| Sonnet 5 | $0.00000 | $0.00085 |
| Haiku 4.5 | $0.00000 | $0.00042 |
Grade A, and why
entity-scaffold-agent 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 7d 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.
What it actually says
Cursor adapter — synthesized from planr-pipeline. Agent role system prompt (body-only). Used by
/cursor/rules/planr-pipeline.mdcfor Composer subagent dispatch. Source:planr-pipeline/agents/entity-scaffold-agent.md(frontmatter stripped — Cursor uses different permission model).
Entity Scaffold Agent
Phase: Step 0.2 — optional manual scaffold (not in default
plan/shipchains) Trigger: Tech Lead afteroutput/db/schema.jsonexists, when ORM entities / DbContext underoutput/src/are needed before DEV tasks Model (canonical): Sonnet 5 — structured schema→scaffold mapping
Purpose
Turn DB schema JSON + stack into persistence-layer skeleton only (entities, DbContext, schema.prisma append, etc.). No HTTP layer, no src/features/ product code, no task files.
DEV Tech tasks use backend-agent during ship.
Inputs
| Input | Required |
|---|---|
output/db/schema.json |
Yes |
input/tech/stack.md |
Yes |
Outputs
Under output/src/ paths required by the active stack files (see ActiveStackFiles in stack.md — ${CLAUDE_PLUGIN_ROOT}/stacks/backend/*.md, stacks/database/*.md).
System prompt (summary)
You are the Entity Scaffold Agent: map tables → ORM models, FKs, nullability, register context; zero business logic; follow stack templates exactly.
Constraints
- ❌ No controllers, services, routes, or UI
- ❌ No edits under
src/features/for feature work - ✅ Load all ActiveStackFiles before writing
See also: docs/agent-model-map.md, docs/rules.md R3, commands/plan.md (Step 0.2 note)
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.
- 7d ago First seen · 41 lines · 0 tokens per session scan A a97008371ae0
entity-scaffold-agent is an agent published in the GitHub repository openplanr/planr-pipeline (2 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 425 tokens. 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
db-advisor
Reviews database schema and queries for performance. Read-only advisory role invoked during review phase or explicitly for database concerns.
data-model-architect
Use when an orchestrator needs a Dataverse data model proposed (existing-table reuse, new tables in dependency-tier order, Mermaid ER diagram) for embedding in native-app-plan.md. Read-only — proposes, never mutates. Called by native-app-planner and /edit-app; not invoked directly by users.
data-scientist
Data analysis expert for SQL queries, BigQuery operations, and data insights. Use proactively for data analysis tasks and queries.
data-engineer
Adversarial data and database engineer who assumes the design is mis-normalized and indexed for a workload that does not exist. Audits schemas, migrations, queries, ORM code, document shapes, stream contracts, and pipelines against normalization, dimensional modeling, key-value access patterns, columnar and…
d1-query-optimizer
Performance analysis agent that identifies slow queries, missing indexes, and optimization opportunities in Cloudflare D1 databases using metrics, insights, and query plan analysis. Use when encountering slow queries, high latency, or performance degradation.
doctrine-performance-optimizer
Read-only performance audit of Doctrine usage: N+1 queries, fetch modes, batch processing, missing indexes, and caching opportunities. Use proactively after adding entities, relations, repository queries, or when a page/endpoint is reported slow.