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/yaooqinn/spark-history-cli/agents-mdgit clone --depth 1 https://github.com/yaooqinn/spark-history-cliWrote 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/yaooqinn/spark-history-cli/agents-md)<a href="https://agentmods.dev/instructions/yaooqinn/spark-history-cli/agents-md"><img src="https://agentmods.dev/badge/instructions/yaooqinn/spark-history-cli/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.00707 | $0.00707 |
| Opus 5 | $0.00353 | $0.00353 |
| Sonnet 5 | $0.00141 | $0.00141 |
| Haiku 4.5 | $0.00071 | $0.00071 |
Grade A, and why
spark-history-cli 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 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Project Overview
spark-history-cli is a Python CLI for querying the Apache Spark History Server REST API. It also ships two agent skills (spark-history-cli and spark-advisor) that teach AI coding assistants how to debug and optimize Spark applications.
Repository Structure
spark-history-cli/
├── spark_history_cli/ # Python package
│ ├── cli.py # Click-based CLI entry point (REPL + one-shot)
│ ├── core/ # API client, formatters, data models
│ ├── utils/ # Skill installer, helpers
│ ├── tests/ # pytest test suite
│ └── skills/ # Bundled SKILL.md (installed via `install-skill` command)
├── skills/ # Root-level skills (discovered by `npx skills add`)
│ ├── spark-history-cli/ # CLI usage skill
│ │ ├── SKILL.md
│ │ └── sample_codes/
│ └── spark-advisor/ # Performance diagnosis skill
│ ├── SKILL.md
│ ├── references/ # diagnostics.md, comparison.md
│ └── sample_codes/
├── setup.py # Package metadata, version, entry points
├── CHANGELOG.md # Release history
└── .github/workflows/
├── ci.yml # Tests on push/PR
└── publish.yml # PyPI publish on GitHub Release
Key Development Guidelines
- Python 3.10+ required
- Install locally:
pip install -e . - Run tests:
pytest spark_history_cli/tests/ - Lint: standard Python conventions, no custom linter configured
- Entry point:
spark_history_cli.cli:main
Making Changes
CLI commands
All commands are in cli.py using Click. Each command calls methods on the API client in core/. Add new commands by following the existing pattern (Click command → API call → format output).
Skills
Skills are pure Markdown (SKILL.md) with optional references/ and sample_codes/. The skills in skills/ (root) are the canonical source — spark_history_cli/skills/ is a bundled copy for the install-skill command.
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 · 70 lines · 707 tokens per session scan A 71c985fc3e21
spark-history-cli AGENTS.md is an instructions file published in the GitHub repository yaooqinn/spark-history-cli (29 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 707 tokens to every session, about $0.0035 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 instructions, from other repositories
hotpath-rs AGENTS.md
AGENTS.md instructions for pawurb/hotpath-rs, covering agents.md, project overview, reference docs, development commands and profiling modes are combined via features, e.g.
codspeed AGENTS.md
AGENTS.md instructions for CodSpeedHQ/codspeed, covering agents.md, common development commands, building and testing, build the project and build in release mode.
hotpath-rs CLAUDE.md
Claude Code instructions for pawurb/hotpath-rs, a project described as: Rust profiler for CPU, memory, SQL, HTTP, and async performance, with Prometheus and Grafana support.
codspeed CLAUDE.md
Claude Code instructions for CodSpeedHQ/codspeed, a project described as: CodSpeed is the all-in-one performance testing toolkit. Optimize code performance and catch regressions early.
benchmark AGENTS.md
AGENTS.md instructions for google/benchmark, a project described as: A microbenchmark support library.
mobilegym AGENTS.md
Instructions for Purewhiter/mobilegym, covering agents.md, project overview, type-checking strategy, eslint and with data graph generation.