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 agentmods add instructions/newfront/pyspark-datagen/agents-mdgit clone --depth 1 https://github.com/newfront/pyspark-datagenWrote 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/instructions/newfront/pyspark-datagen/agents-md)<a href="https://agentmods.dev/instructions/newfront/pyspark-datagen/agents-md"><img src="https://agentmods.dev/badge/instructions/newfront/pyspark-datagen/agents-md.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.02829 | $0.02829 |
| Opus 5 | $0.01414 | $0.01414 |
| Sonnet 5 | $0.00566 | $0.00566 |
| Haiku 4.5 | $0.00283 | $0.00283 |
Grade A, and why
pyspark-datagen AGENTS.md 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 5d 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 — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent guide: learning-spark-datagen
Quick reference for AI agents (and humans) so you don’t have to scan the README or multiple files to run data generation and Delta workflows.
Agent rules and skills (load these automatically)
Project-specific rules and skills live under .agents/ (not .cursor/). This AGENTS.md is loaded automatically, so at the start of any task in this repo, also load and follow the following:
- Rules — read every file in
.agents/rules/and apply them as always-on guidance:.agents/rules/agents-and-tests.mdc— when you find a better approach, updateAGENTS.md, add/extend unit tests, and fix one problem at a time..agents/rules/git-branching.mdc— never commit directly tomain; before starting work, check the current branch and (if onmain) create a feature branch first. UseAskQuestionto offer a suggestedfeat/<short-description>name or let the user provide their own. Prefixes:feat/,fix/,chore/,refactor/,test/. One logical unit of work per branch.
- Skills — when a task matches a skill's description, read its
SKILL.mdfirst and follow it:.agents/skills/add-datagen-generator/SKILL.md— add a new Protobuf-backed data generator (new proto,GenXclass, CLI, tests) following the User/Order pattern.
If you add new rules or skills, drop them under
.agents/rules/or.agents/skills/<name>/SKILL.mdand add a bullet here so they continue to load automatically.
Where to run
All commands below assume you’re in learning-spark-datagen/ (the package with main.py and pyproject.toml). Use uv run to execute the CLI.
cd learning-spark-datagen
CLI: main.py
Entry point: uv run main.py (or uv run main.py --generate ...).
| Flag | Purpose |
|---|---|
--generate |
Enable generate mode (required for data gen). |
--type users | orders | products | sessions | rain_sensors |
Entity to generate (default: users). |
--count N |
Number of records — or sessions for --type sessions — (default: 100). |
--output PATH |
File path for JSON/NDJSON; required for --format delta (Delta table directory). |
--format json | delta |
json = NDJSON to file (or stdout if --output omitted); delta = Delta table. Auto-defaults to delta when --users-table or --products-table is set; otherwise json. |
--users-file PATH |
For --type orders and --type sessions. NDJSON file of users; user_id will be one of these UUIDs. |
--users-table DELTA_DIR |
Alternative to --users-file; reads users from a Delta table via Spark. Mutually exclusive with --users-file. |
--products-file PATH |
For --type sessions only. NDJSON file of products; every event's items[].item_id will reference these products. |
--products-table DELTA_DIR |
Alternative to --products-file; reads the product catalog from a Delta table via Spark. Mutually exclusive with --products-file. |
--start-date YYYY-MM-DD |
For --type sessions only. Earliest session date (default 2026-01-01). |
--end-date YYYY-MM-DD |
For --type sessions only. Latest session date (default 2026-05-28). |
--sessions-per-user-alpha FLOAT |
For --type sessions only. Zipf exponent for user picking (default 1.5; higher = more skew toward loyal customers). |
--funnel-profile realistic | aggressive | conservative |
For --type sessions only. Built-in funnel drop-off profile (default realistic). |
--seed N |
Random seed (default: 42). |
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.
- 5d ago First seen · 172 lines · 2,829 tokens per session scan A be72ce46d287
pyspark-datagen AGENTS.md is an instructions file published in the GitHub repository newfront/pyspark-datagen (5 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 2,829 tokens to every session, about $0.0141 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 instructions, from other repositories
python-sdk AGENTS.md
AGENTS.md instructions for modelcontextprotocol/python-sdk, covering development guidelines, note for ai agents, branching model, package management and code quality.
GPT-RAG config-python.instructions.md
Instructions for Azure/GPT-RAG, a project described as: Enterprise-grade accelerator for agentic RAG on Azure. Built on Microsoft Foundry with Foundry IQ as the default retrieval backend, Microsoft Agent Framework orchestration, Zero-Trust architecture and IaC.
weightslab AGENTS.md
AGENTS.md instructions for GrayboxTech/weightslab, covering weightslab — agent context for users & debugging, 0. how to load this guide into claude code, 1. what it is and how the pieces connect, 2. install & run (the happy path) and ... your training loop ...
metaxy CLAUDE.md
Claude Code instructions for anam-org/metaxy, covering claude.md, agent workflow, python code standards, project status and project overview.
sports-skills CLAUDE.md
Claude Code instructions for machina-sports/sports-skills, covering claude.md - sports-skills guidelines, tech stack, commands and code conventions.
OpenGradient-SDK CLAUDE.md
Instructions for OpenGradient/OpenGradient-SDK, covering claude.md, project overview, development commands, build & installation and install dependencies (syncs from pyproject.toml/uv.lock).