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.
npx skills add patricio0312rev/skillset --skill test-data-factory-buildergit clone --depth 1 https://github.com/patricio0312rev/skillsetWrote 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/test-data-factory-builder)<a href="https://agentmods.dev/skills/patricio0312rev/skillset/test-data-factory-builder"><img src="https://agentmods.dev/badge/skills/patricio0312rev/skillset/test-data-factory-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/test-data-factory-builder"><img src="https://agentmods.dev/badge/skills/patricio0312rev/skillset/test-data-factory-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.00046 | $0.02477 |
| Opus 5 | $0.00023 | $0.01239 |
| Sonnet 5 | $0.00009 | $0.00495 |
| Haiku 4.5 | $0.00005 | $0.00248 |
Grade A, and why
test-data-factory-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 9d 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 test-data-factory-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 — 450 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Data Factory Builder
Create composable factories for consistent test data.
Factory Pattern
// factories/UserFactory.ts
import { faker } from "@faker-js/faker";
export class UserFactory {
private data: Partial<User> = {};
static create(overrides?: Partial<User>): User {
return new UserFactory().with(overrides).build();
}
with(overrides: Partial<User>): this {
this.data = { ...this.data, ...overrides };
return this;
}
withEmail(email: string): this {
this.data.email = email;
return this;
}
withRole(role: UserRole): this {
this.data.role = role;
return this;
}
asAdmin(): this {
this.data.role = "ADMIN";
return this;
}
build(): User {
return {
id: this.data.id || faker.string.uuid(),
email: this.data.email || faker.internet.email(),
name: this.data.name || faker.person.fullName(),
role: this.data.role || "USER",
createdAt: this.data.createdAt || faker.date.past(),
...this.data,
};
}
}
// Usage
const user = UserFactory.create();
const admin = UserFactory.create().asAdmin().build();
const specific = UserFactory.create({ email: "[email protected]" });
Builder Pattern
// builders/OrderBuilder.ts
export class OrderBuilder {
private user?: User;
private items: OrderItem[] = [];
private status: OrderStatus = "PENDING";
forUser(user: User): this {
this.user = user;
return this;
}
withItem(product: Product, quantity: number = 1): this {
this.items.push({
id: faker.string.uuid(),
productId: product.id,
quantity,
price: product.price,
});
return this;
}
withStatus(status: OrderStatus): this {
this.status = status;
return this;
}
asPaid(): this {
this.status = "PAID";
return this;
}
async build(): Promise<Order> {
if (!this.user) {
throw new Error("User is required");
}
const total = this.items.reduce(
(sum, item) => sum + item.price * item.quantity,
0
);
return {
id: faker.string.uuid(),
userId: this.user.id,
items: this.items,
total,
status: this.status,
createdAt: new Date(),
};
}
}
// Usage
const order = await new OrderBuilder()
.forUser(user)
.withItem(laptop, 2)
.withItem(phone, 1)
.asPaid()
.build();
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.
- 9d ago First seen · 450 lines · 46 tokens per session scan A 8d78809ef96f
test-data-factory-builder is a skill published in the GitHub repository patricio0312rev/skillset (6 stars, last pushed 8mo ago), licensed MIT. It adds 46 tokens to every session and 2,477 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to test-data-factory-builder, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".
neuron-evaluation-engineer
Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.
skill-benchmark
Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.