local-dev-data-pack-orchestrator

local-dev-data-pack-orchestrator is an agent for Claude Code from ivegamsft/basecoat. It costs 102 tokens per session (586 once invoked), scanned A, original, MIT.

A local test-data manager that detects the databases used by a repository and creates, checks, updates, or removes matching Docker Compose data packs.

In plain words
What is it for?
It is for preparing deterministic local database fixtures, validating their contracts and repeatability, updating them safely, and previewing targeted cleanup.
Why use it?
It prevents local test environments from using seed files or database setup that does not match the application's actual persistence configuration.

Agent for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: model in frontmatter.

Good fit It is for preparing deterministic local database fixtures, validating their contracts and repeatability, updating them safely, and previewing targeted cleanup.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/ivegamsft/basecoat/basecoat-60-workflow-local-dev-data-pack-orchestrator
Install

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.

Clone the repo
git clone --depth 1 https://github.com/ivegamsft/basecoat

Made for: Claude Code.

Wrote 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.

agentmods badge for local-dev-data-pack-orchestrator

README.md
[![agentmods](https://agentmods.dev/badge/agents/ivegamsft/basecoat/basecoat-60-workflow-local-dev-data-pack-orchestrator/github.svg)](https://agentmods.dev/agents/ivegamsft/basecoat/basecoat-60-workflow-local-dev-data-pack-orchestrator)
Your own site
<a href="https://agentmods.dev/agents/ivegamsft/basecoat/basecoat-60-workflow-local-dev-data-pack-orchestrator"><img src="https://agentmods.dev/badge/agents/ivegamsft/basecoat/basecoat-60-workflow-local-dev-data-pack-orchestrator/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.

agentmods 80×15 button for local-dev-data-pack-orchestrator

Your own site · 80×15
<a href="https://agentmods.dev/agents/ivegamsft/basecoat/basecoat-60-workflow-local-dev-data-pack-orchestrator"><img src="https://agentmods.dev/badge/agents/ivegamsft/basecoat/basecoat-60-workflow-local-dev-data-pack-orchestrator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 102 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 586 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00102 $0.00586
Opus 5.5 $0.00041 $0.00234
Sonnet 5.5 $0.00020 $0.00117
Haiku 4.5 $0.00010 $0.00059

Measured 2mo ago against content hash a3110879a7c1, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

local-dev-data-pack-orchestrator 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 2mo 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.

agents/basecoat-60-workflow-local-dev-data-pack-orchestrator.agent.md · 55 lines

What it actually says

Local Dev Data Pack Orchestrator Agent

Mission

Discover real persistence topology in the current app and run the correct local data-pack lifecycle operation with deterministic, store-correct outputs.

Inputs

  1. Mode: generate, validate, update, or delete.
  2. Repository path and optional scenario name.
  3. Target store scope (postgres, sqlserver, cosmos, or auto-detect).
  4. Output roots (default local-dev/compose, local-dev/data-pack).
  5. Safety flags (dry-run, drop-and-reseed, reuse-volumes).

Workflow

  1. Detect persistence topology from code/config signals (provider strings, ORM config, connection patterns).
  2. Resolve active store set and reject unsupported/ambiguous targets.
  3. Execute selected mode:
    • generate: scaffold compose profiles + manifest + store artifacts
    • validate: run contract/idempotence/audit checks and emit report
    • update: apply scoped artifact changes and require post-update validation
    • delete: run dry-run preview, present the exact resolved file list, then stop and require explicit user confirmation before removing targeted artifacts
  4. Produce deterministic summary including store coverage and operation outcome.

Guardrails

  1. Local-only target enforcement; never apply to shared/prod endpoints.
  2. Deterministic IDs and idempotent seeds are mandatory.
  3. delete requires explicit scope, a dry-run preview, path containment (canonicalize each target — resolving symlinks and .. — and verify it stays under the selected scenario/output root, rejecting any path that escapes it), and a mandatory stop for explicit user confirmation of the exact file list before any destructive removal; never proceed from preview straight to deletion.
  4. Fail closed on unknown store adapters or invalid manifest paths.

Output

  • Resolved topology and selected stores
  • Operation plan and executed steps
  • Validation/audit results by store
  • Artifact change report (created/updated/deleted paths)
Changes

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.

  1. 2mo ago Changed a3110879a7c1
  2. 2mo ago First seen · 55 lines · 102 tokens per session scan A f48142c3cadd

Subscribe to this mod's changes

local-dev-data-pack-orchestrator is an agent published in the GitHub repository ivegamsft/basecoat (4 stars, last pushed 16d ago), licensed MIT. It adds 102 tokens to every session and 586 once invoked, about $0.0004 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-09-03.

Related

local-dev-data-pack-orchestrator compared with agents from other repositories

local-dev-data-pack-orchestrator next to 6 agents from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
local-dev-data-pack-orchestratorivegamsft/basecoatAgent416d agoMITA102Claude Code
postgres-dbafmflurry/settings-opencodeAgent17010d agoMITA75Claude Code
postgres-dbafmflurry/harness-manifestoAgent170yesterdayMITA75Claude Code
PostgreSQL Database Administratorgithub/awesome-copilotAgent41ktodayMITA17Claude Code
devops-engineerpiomin/claude-ai-spring-bootAgent1.5ktodayApache-2.0A36Claude Code
postgres-expert0xfurai/claude-code-subagentsAgent1.0k9d agoMITA28Claude Code
supabase-substrate-explorerKastalien-Research/thoughtboxAgent665d agoMITA117Claude Code