Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/patricio0312rev/skillsetnpx agentmods add skills/patricio0312rev/skillset/data-seeding-fixtures-builderWrote 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/skills/patricio0312rev/skillset/data-seeding-fixtures-builder)<a href="https://agentmods.dev/skills/patricio0312rev/skillset/data-seeding-fixtures-builder"><img src="https://agentmods.dev/badge/skills/patricio0312rev/skillset/data-seeding-fixtures-builder/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/skills/patricio0312rev/skillset/data-seeding-fixtures-builder"><img src="https://agentmods.dev/badge/skills/patricio0312rev/skillset/data-seeding-fixtures-builder.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.00050 | $0.02185 |
| Opus 5 | $0.00025 | $0.01092 |
| Sonnet 5 | $0.00010 | $0.00437 |
| Haiku 4.5 | $0.00005 | $0.00218 |
Grade A, and why
data-seeding-fixtures-builder 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.
This is a copy
100% identical to data-seeding-fixtures-builder — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 376 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Data Seeding & Fixtures Builder
Generate realistic, deterministic seed data for development and testing.
Seed Data Strategy
// prisma/seed.ts
import { PrismaClient } from "@prisma/client";
import { faker } from "@faker-js/faker";
const prisma = new PrismaClient();
async function main() {
console.log("🌱 Seeding database...");
// Clear existing data
await prisma.order.deleteMany();
await prisma.user.deleteMany();
// Seed users
const users = await seedUsers(10);
console.log(`✅ Created ${users.length} users`);
// Seed orders
const orders = await seedOrders(users, 50);
console.log(`✅ Created ${orders.length} orders`);
console.log("✅ Seeding complete!");
}
main()
.catch((e) => {
console.error(e);
process.exit(1);
})
.finally(async () => {
await prisma.$disconnect();
});
Factory Functions
// factories/user.factory.ts
import { faker } from "@faker-js/faker";
import { PrismaClient, User } from "@prisma/client";
const prisma = new PrismaClient();
export interface UserFactoryOptions {
email?: string;
name?: string;
role?: "USER" | "ADMIN";
}
export class UserFactory {
static async create(options: UserFactoryOptions = {}): Promise<User> {
return prisma.user.create({
data: {
email: options.email || faker.internet.email(),
name: options.name || faker.person.fullName(),
role: options.role || "USER",
createdAt: faker.date.past(),
},
});
}
static async createMany(
count: number,
options: UserFactoryOptions = {}
): Promise<User[]> {
return Promise.all(
Array.from({ length: count }, () => this.create(options))
);
}
static async createAdmin(): Promise<User> {
return this.create({ role: "ADMIN" });
}
}
// Usage:
// const user = await UserFactory.create();
// const admin = await UserFactory.createAdmin();
// const users = await UserFactory.createMany(10);
Realistic Fixtures
// fixtures/products.ts
import { Product } from "@prisma/client";
export const PRODUCT_FIXTURES: Omit<
Product,
"id" | "createdAt" | "updatedAt"
>[] = [
{
name: 'MacBook Pro 16"',
description: "Powerful laptop for developers",
price: 2499.99,
stock: 50,
category: "Electronics",
},
{
name: "iPhone 15 Pro",
description: "Latest flagship smartphone",
price: 999.99,
stock: 100,
category: "Electronics",
},
{
name: "AirPods Pro",
description: "Wireless earbuds with noise cancellation",
price: 249.99,
stock: 200,
category: "Electronics",
},
];
// Seed products
async function seedProducts() {
return Promise.all(
PRODUCT_FIXTURES.map((product) => prisma.product.create({ data: product }))
);
}
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 · 376 lines · 50 tokens per session scan A 80ca8fec6ea3
data-seeding-fixtures-builder is a skill published in the GitHub repository patricio0312rev/skillset (6 stars, last pushed 8mo ago), licensed MIT. It adds 50 tokens to every session and 2,185 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to data-seeding-fixtures-builder, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
review-prs
Review a GitHub pull request in the googleapis/mcp-toolbox repo against the team's reviewer checklist: PR title/description conventions, linked issue, logic errors and unhandled edge cases, breaking changes, test coverage, docs updates, security (input handling), and new dependencies. Use whenever a maintainer asks…
reproduce-bug
Reproduce a reported bug in googleapis/mcp-toolbox and decide whether it is real, delivering an evidence-backed verdict: confirmed, already fixed, misconfiguration, client-side, works as intended, not reproducible, or blocked. Use whenever a maintainer asks you to reproduce, verify, confirm, or investigate a bug…
fix-failing-tests
Diagnose a failing test in the googleapis/mcp-toolbox repo and land a fix by reasoning from the actual error: read the failure, reproduce it, shrink it until the cause is forced into the open, then fix the cause. Use this whenever a test or CI job is red, a build breaks after a change, many packages fail at once, or a…
azure-cosmos-db-py
Build Azure Cosmos DB NoSQL services with Python/FastAPI following production-grade patterns. Use when implementing database client setup with dual auth (DefaultAzureCredential + emulator), service layer classes with CRUD operations, partition key strategies, parameterized queries, or TDD patterns for Cosmos. Triggers…
adding-dbt-unit-test
Creates unit test YAML definitions that mock upstream model inputs and validate expected outputs. Use when adding unit tests for a dbt model or practicing test-driven development (TDD) in dbt.
gh-issue
Size-audit, write, and split BanyanDB issues that somebody else or an automated TDD workflow can implement. Use whenever the user asks to file or revise an issue, decide whether an issue is too large, make an issue TDD-ready, turn a design into tickets, or split an umbrella into executable leaves. Do not draft or file…