Borrowing it
Nothing to install: this file belongs to Undertone0809/rudder. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Undertone0809/rudder/main/.agents/skills/maintainer/mock-data-maintainer/SKILL.mdgit clone --depth 1 https://github.com/Undertone0809/rudderWrote 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/undertone0809/rudder/mock-data-maintainer)<a href="https://agentmods.dev/skills/undertone0809/rudder/mock-data-maintainer"><img src="https://agentmods.dev/badge/skills/undertone0809/rudder/mock-data-maintainer.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.00050 | $0.02834 |
| Opus 5 | $0.00025 | $0.01417 |
| Sonnet 5 | $0.00010 | $0.00567 |
| Haiku 4.5 | $0.00005 | $0.00283 |
Grade A, and why
mock-data-maintainer 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 — 316 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mock Data Maintainer
Use this skill to create mock data that is useful, coherent, and easy to reuse. The goal is not random fake records. The goal is scenario data that supports testing, screenshots, demos, and clear user understanding.
First Decision
Classify the request into one primary intent before generating data:
- testing data: local dev, E2E, bug reproduction, contract checks, edge states
- screenshot/demo data: local screenshots, landing proof shots, README, decks
- user-scenario data: explain a workflow, persona, problem, or product value
- static artifact data: CSV, JSON, SQL, Markdown table, or TypeScript fixture
If the prompt implies multiple intents, produce one shared scenario spine and then adapt outputs for each intent. For example, one Rudder launch-week org can serve local screenshots, workflow explanation, and E2E fixture design.
Reference Selection
Read only the references needed for the request:
references/scenario-index.md: scenario catalog and selection rulesreferences/quality-bar.md: realism, determinism, privacy, and output rulesreferences/rudder-studio-scenario.md: canonical month-long "Rudder uses Rudder to build and grow Rudder" org, with reusable JSON fixtures and seed scriptreferences/rudder-landing-demo-org.md: canonical screenshot-ready Rudder orgreferences/rudder-test-fixtures.md: Rudder testing and edge-state fixturesreferences/rudder-user-scenarios.md: Rudder user stories and scenario spinesreferences/generic-saas-dashboard.md: SaaS metrics, billing, and ops datareferences/generic-crm-sales.md: CRM, pipeline, account, and support datareferences/edge-states.md: empty, error, boundary, permission, and conflict states
Bundled Scripts
Use bundled scripts when the user needs live Rudder data instead of static records:
scripts/capture-landing-proof-shots.ts: boots an isolated Rudder instance, seeds the canonical landing demo org, and optionally captures proof-shot screenshots. UseLANDING_SHOTS_SKIP_CAPTURE=1 LANDING_SHOTS_HOLD_OPEN=1for seed-only local screenshot prep.scripts/seed-rudder-studio.ts: seeds the reusable Rudder Studio org into a running local dev instance. Use it when the user wants a realistic month-long Rudder org, "using Rudder to build Rudder", natural Calendar work history, or durable user-scenario data.
What ships with it
18 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.
- data/rudder-studio/agents.json 2.9 KB
- data/rudder-studio/approvals.json 2.7 KB
- data/rudder-studio/calendar.json 2.5 KB
- data/rudder-studio/chats.json 2.7 KB
- data/rudder-studio/issues.json 21 KB
- data/rudder-studio/scenario.json 5.0 KB
- references/edge-states.md 1.1 KB
- references/generic-crm-sales.md 1.1 KB
- references/generic-saas-dashboard.md 1.2 KB
- references/quality-bar.md 4.0 KB
- references/rudder-landing-demo-org.md 5.5 KB
- references/rudder-studio-scenario.md 6.2 KB
- references/rudder-test-fixtures.md 2.2 KB
- references/rudder-user-scenarios.md 3.6 KB
- references/runbook.md 13 KB
- references/scenario-index.md 2.2 KB
- scripts/capture-landing-proof-shots.ts 69 KB runs code
- scripts/seed-rudder-studio.ts 34 KB runs code
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 · 316 lines · 50 tokens per session scan A 7bc158276b12
mock-data-maintainer is a skill published in the GitHub repository Undertone0809/rudder (288 stars, last pushed today), licensed Apache-2.0. It adds 50 tokens to every session and 2,834 once invoked, about $0.0003 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…