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/stuartshields/claude-setupWrote 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/stuartshields/claude-setup/seed-generator)<a href="https://agentmods.dev/agents/stuartshields/claude-setup/seed-generator"><img src="https://agentmods.dev/badge/agents/stuartshields/claude-setup/seed-generator.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.00042 | $0.00828 |
| Opus 5 | $0.00021 | $0.00414 |
| Sonnet 5 | $0.00008 | $0.00166 |
| Haiku 4.5 | $0.00004 | $0.00083 |
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 6d 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 — 121 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 Detection
Detect the ORM/schema approach before generating:
- Prisma:
prisma/schema.prisma - Drizzle:
src/**/schema.tsin db directories - TypeORM:
src/**/*.entity.ts - Raw SQL:
migrations/*.sql
Check for existing seeds before creating new ones.
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'),
},
];
Relational Data (Orders referencing Users)
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 },
],
},
];
Data Requirements by Environment
| Environment | Volume | Characteristics |
|---|---|---|
| Development | 10-50 records | Predictable IDs, known test accounts, edge cases |
| Testing | Minimal | Deterministic, covers all code paths, fast create/destroy |
| Demo/Staging | 100-1000 records | Realistic volume, varied statuses/dates, visually appealing |
Output Report
After generating seeds:
## Seed Data Report
### Generated Files
| File | Purpose |
|------|---------|
| `prisma/seed.ts` | Main seed script |
### Data Summary
| Table | Records | Notes |
|-------|---------|-------|
| users | 5 | 1 admin, 4 regular |
| products | 20 | Various categories |
| orders | 10 | Mixed statuses |
### Test Accounts
| Email | Password | Role |
|-------|----------|------|
| [email protected] | admin123 | ADMIN |
| [email protected] | user123 | USER |
### Run Seeds
```bash
npx prisma db seed
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.
- 6d ago First seen · 121 lines · 42 tokens per session scan A f19411cdd567
seed-generator is an agent published in the GitHub repository stuartshields/claude-setup (2 stars, last pushed 3mo ago), licensed MIT. It adds 42 tokens to every session and 828 once invoked, about $0.0002 per session on Opus 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-31.
Other agents, from other repositories
convex-expert
Expert Convex backend developer for queries, mutations, actions, schemas, auth, scheduling, components, and database operations. Use PROACTIVELY when working in convex/ directory, implementing backend features, debugging Convex functions, or using Convex components.
database-migrations
Role: Database Migration Safety Reviewer. Task: Ensure all schema migrations are safe for zero-downtime production deployments and are fully reversible where possible.
cover-letter-writer
Writes a tailored LaTeX cover letter using job analysis and resume summary. Follows strict anti-echo rules — no mirroring the job post, no filler, B2 English. Saves saifcoverletter.tex to the output folder.
resume-tailor
Tailors the candidate's resume LaTeX file to a specific job using masterdata.yaml and job analysis output. Selects relevant bullets, reorders skills, and weaves in ATS keywords. Saves saifresume.tex to the output folder.
job-analyzer
Extracts structured info from a job post — company name, job title, job type, key skills, ATS keywords, responsibilities, and address. Always run this first before resume or cover letter agents.
symfony-specialist
Use when building Symfony 6+/7+/8+ applications, architecting Doctrine ORM entities with complex relationships, implementing Messenger component for async processing, or optimizing API Platform performance.