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 codebygarv/Ai-skills --skill mock-and-fixture-generatorgit clone --depth 1 https://github.com/codebygarv/Ai-skillsWrote 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/codebygarv/ai-skills/mock-and-fixture-generator)<a href="https://agentmods.dev/skills/codebygarv/ai-skills/mock-and-fixture-generator"><img src="https://agentmods.dev/badge/skills/codebygarv/ai-skills/mock-and-fixture-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/skills/codebygarv/ai-skills/mock-and-fixture-generator"><img src="https://agentmods.dev/badge/skills/codebygarv/ai-skills/mock-and-fixture-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.00026 | $0.00310 |
| Opus 5 | $0.00013 | $0.00155 |
| Sonnet 5 | $0.00005 | $0.00062 |
| Haiku 4.5 | $0.00003 | $0.00031 |
Grade A, and why
mock-and-fixture-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 7d 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.
What it actually says
Purpose
Synthesize privacy-safe, edge-case-heavy test fixtures, mock API responses, and database seed data covering diverse data shapes, boundary values, and unicode variations.
When to Use
- Seeding unit and end-to-end test suites with realistic mock records.
- Creating local mock APIs for frontend development before the backend is built.
- Replacing dangerous production database dumps with anonymized synthetic datasets.
What to Analyze
- Data Model & Relationships: Foreign key links, nested arrays, and enum constraints.
- Realistic Variety: Realistic realistic names, addresses, emails, timestamps, and currency amounts.
- Boundary Edge Cases: Zero values, max safe integers, empty strings, nulls, long multi-byte Unicode/emojis, and SQL injection strings.
- PII Safety: Guaranteed zero real customer data (Faker/synthetic generated only).
Output Format
- JSON / TypeScript Fixture File: Clean, typed mock dataset.
- Factory Function: Parameterized factory helper (e.g.
createMockUser({ role: 'admin' })). - Edge Case Variants: Specific payloads containing boundary test cases.
Avoid
- Copying real production customer data into git repositories.
- Using trivial placeholders like
"test1","test2"that miss boundary bugs.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 7d ago First seen · 33 lines · 26 tokens per session scan A 2f9150213fad
mock-and-fixture-generator is a skill published in the GitHub repository codebygarv/Ai-skills (25 stars, last pushed 21d ago), licensed MIT. It adds 26 tokens to every session and 310 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
playwright-best-practices
Use when writing Playwright tests, fixing flaky tests, debugging failures, implementing Page Object Model, configuring CI/CD, optimizing performance, mocking APIs, handling authentication or OAuth, testing accessibility (axe-core), file uploads/downloads, date/time mocking, WebSockets, geolocation, permissions…
bun-cli
Bun CLI reference for package management, script running, testing, bundling, and compilation. Covers bun install/add/remove/update, bun run, bun test, bun build, bunx, bun patch, bun audit fix, bun dedupe, bun prune, bun why, bun pm, bun repl, bunfig.toml, bun.lock, workspace catalogs, isolated installs and the global…
ds-test
Universal test skill — generate, update, run, and fix tests for any stack. Use when writing, repairing, or running tests, or improving coverage.
Test Engineer
Creates or completes a medium-coverage test suite: unit, component, and critical e2e flows.
test-plan-writing
Write risk-based test plans with coverage matrices, test level decisions, pass/fail criteria, and environment requirements — deciding what to test, at which level, and why.
e2e-testing
Guide for running end-to-end tests of the Qwen Code CLI, including headless mode, MCP server testing, and API traffic inspection. Use this skill whenever you need to verify CLI behavior with real model calls, reproduce user-reported bugs end-to-end, test MCP tool integrations, or inspect raw API request/response…