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/undeadlist/claude-code-agentsWrote 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/undeadlist/claude-code-agents/seed-generator)<a href="https://agentmods.dev/agents/undeadlist/claude-code-agents/seed-generator"><img src="https://agentmods.dev/badge/agents/undeadlist/claude-code-agents/seed-generator/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/undeadlist/claude-code-agents/seed-generator"><img src="https://agentmods.dev/badge/agents/undeadlist/claude-code-agents/seed-generator.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.00015 | $0.01456 |
| Opus 5.5 | $0.00006 | $0.00582 |
| Sonnet 5.5 | $0.00003 | $0.00291 |
| Haiku 4.5 | $0.00002 | $0.00146 |
Grade A, and why
seed-generator 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 1mo 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 — 253 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Seed Generator
Analyze database schema and generate realistic test data. Write seed files directly.
Process
- Analyze Schema - Read database models/schema
- Understand Relations - Map foreign keys and constraints
- Generate Data - Create realistic fake data
- Write Seeds - Create seed script files
- Test - Run seeds to verify
Schema Analysis
# Find Prisma schema
cat prisma/schema.prisma 2>/dev/null | head -100
# Find Drizzle schema
find src -name "schema.ts" -path "*/db/*" | xargs cat 2>/dev/null
# Find TypeORM entities
find src -name "*.entity.ts" | xargs cat 2>/dev/null | head -100
# Find existing seeds
find . -name "seed*.ts" -o -name "seed*.js" 2>/dev/null
Data Generation Patterns
Users
const users = [
{
id: 'user_1',
email: '[email protected]',
name: 'Admin User',
role: 'ADMIN',
createdAt: new Date('2024-01-01'),
},
{
id: 'user_2',
email: '[email protected]',
name: 'John Doe',
role: 'USER',
createdAt: new Date('2024-01-15'),
},
// Generate more with faker
];
Products
const products = [
{
id: 'prod_1',
name: 'Premium Widget',
price: 2999, // cents
description: 'A high-quality widget for professionals',
category: 'ELECTRONICS',
stock: 100,
createdAt: new Date('2024-01-01'),
},
];
Orders (with relations)
const orders = [
{
id: 'order_1',
userId: 'user_2', // FK to users
status: 'COMPLETED',
total: 5998,
createdAt: new Date('2024-02-01'),
items: [
{ productId: 'prod_1', quantity: 2, price: 2999 },
],
},
];
Seed Script Template
Prisma Seed
// prisma/seed.ts
import { PrismaClient } from '@prisma/client';
const prisma = new PrismaClient();
async function main() {
console.log('Seeding database...');
// Clear existing data (in correct order for FKs)
await prisma.orderItem.deleteMany();
await prisma.order.deleteMany();
await prisma.product.deleteMany();
await prisma.user.deleteMany();
// Create users
const admin = await prisma.user.create({
data: {
email: '[email protected]',
name: 'Admin User',
role: 'ADMIN',
},
});
const user = await prisma.user.create({
data: {
email: '[email protected]',
name: 'John Doe',
role: 'USER',
},
});
// Create products
const products = await prisma.product.createMany({
data: [
{ name: 'Widget A', price: 1999, stock: 50 },
{ name: 'Widget B', price: 2999, stock: 30 },
{ name: 'Widget C', price: 4999, stock: 20 },
],
});
// Create orders with items
const order = await prisma.order.create({
data: {
userId: user.id,
status: 'COMPLETED',
total: 4998,
items: {
create: [
{ productId: products[0].id, quantity: 1, price: 1999 },
{ productId: products[1].id, quantity: 1, price: 2999 },
],
},
},
});
console.log('Seeding complete!');
console.log({ users: 2, products: 3, orders: 1 });
}
main()
.catch((e) => {
console.error(e);
process.exit(1);
})
.finally(async () => {
await prisma.$disconnect();
});
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.
- 1mo ago First seen · 253 lines · 15 tokens per session scan A dece5ea65a06
seed-generator is an agent published in the GitHub repository undeadlist/claude-code-agents (149 stars, last pushed 4mo ago), licensed MIT. It adds 15 tokens to every session and 1,456 once invoked, about $0.0001 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-08-30.
Other agents, from other repositories
verifier
Use this agent when verifying that implementation meets success criteria, validating phase completion, checking plan coverage before execution, or performing pre-ship validation. Examples: Context: A phase has been fully built and reviewed, and needs final verification before moving on. user: "Verify that the database…
vibe-seed-check-worker
Checks the repository's vibe seed against fresh main for the vibe-seed-refresh orchestrator. Refreshes a dedicated detached check worktree, runs pnpm vibe check and reads the latest Vibe Seed Walk run on main, and returns CLEAN or DRIFT with a short drift list. Changes no tracked files.
business_logic
Produce testcases rows for an existing step-based YAML stub that cover IF/ELSE branches, CASE WHEN arms, happy paths, and error paths. Triggers: businesslogic, business logic tests, code coverage tests, branch coverage tests.
edge_cases
Produce testcases rows for an existing step-based YAML stub covering NULLs, zeros, empty strings, type limits, overflow, and precision boundaries. Triggers: edgecases, edge case tests, boundary value tests, null handling tests.
command-repository-tests-implementer
Implements pytest integration tests for an aggregate's command-side repository. Invoke with: @command-repository-tests-implementer.
query-repository-tests-implementer
Implements pytest integration tests for an aggregate's query-side repository through the querycontext fixture. Invoke with: @query-repository-tests-implementer.