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/datenoio/iterabledata/agents-mdgit clone --depth 1 https://github.com/datenoio/iterabledataWhat 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 | $0.02397 | $0.02397 |
| Opus 5 | $0.01198 | $0.01198 |
| Sonnet 5 | $0.00479 | $0.00479 |
| Haiku 4.5 | $0.00240 | $0.00240 |
Grade A, and why
iterabledata 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 3d 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 — 226 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenSpec Instructions
These instructions are for AI assistants working in this project.
Always open @/openspec/AGENTS.md when the request:
- Mentions planning or proposals (words like proposal, spec, change, plan)
- Introduces new capabilities, breaking changes, architecture shifts, or big performance/security work
- Sounds ambiguous and you need the authoritative spec before coding
Use @/openspec/AGENTS.md to learn:
- How to create and apply change proposals
- Spec format and conventions
- Project structure and guidelines
Keep this managed block so 'openspec update' can refresh the instructions.
AGENTS.md
Instructions for AI coding agents working on the IterableData project.
Setup commands
- Install dependencies:
pip install -e ".[dev]" - Run tests:
pytest --verbose(includes coverage automatically) - Run tests with parallel execution:
pytest -n auto - Run linter:
ruff check iterable tests - Format code:
ruff format iterable tests - Type check:
mypy iterable - Run all checks:
ruff check iterable tests && ruff format --check iterable tests && pytest
Security and Quality Tools
- Security scan:
bandit -r iterable -ll - Dependency vulnerabilities:
pip-audit --requirement <(pip freeze) - Dead code detection:
vulture iterable --min-confidence 80 - Code complexity:
radon cc iterable --min B - Documentation style:
pydocstyle iterable - Coverage report:
pytest --cov=iterable --cov-report=html(openshtmlcov/index.html)
Code style
- Python 3.10+ with type hints where appropriate
- Maximum line length: 120 characters (configured in
pyproject.toml) - Use
rufffor linting and formatting (E, F, I, B, UP rules enabled) - Use double quotes for strings consistently
- Follow PEP 8 with project-specific exceptions
- Always use context managers (
withstatements) for file operations - Import organization: standard library, third-party, local imports
Project structure
iterable/- Main package directoryhelpers/- Utility functions (detect, schema, utils)datatypes/- Format-specific implementations (CSV, JSON, Parquet, etc.)codecs/- Compression codec implementationsengines/- Processing engines (DuckDB, internal)convert/- Format conversion utilitiespipeline/- Data pipeline processing
tests/- Test suite (one test file per format/feature)examples/- Usage examplestests/fixtures/- Committed test data files (tests/testdata/is a symlink to this directory)fixtures/- Test fixtures
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.
- 3d ago First seen · 226 lines · 2,397 tokens per session scan A cf77cb0c057c
iterabledata AGENTS.md is an instructions file published in the GitHub repository datenoio/iterabledata (37 stars, last pushed 13d ago), licensed MIT. It adds 2,397 tokens to every session, about $0.0120 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
wiremock AGENTS.md
AGENTS.md instructions for wiremock/wiremock, covering agent rules, running the build, messaging/websocket code and rules for these packages.
js-bson AGENTS.md
Instructions for mongodb/js-bson, covering agents.md, project overview, commands, benchmarks and structure.
markitdown-mcp AGENTS.md
Instructions for trsdn/markitdown-mcp, covering ai agents integration guide, 🤖 quick reference for ai agents, primary use cases, available tools and 🛠️ tool usage guide.
json-difference CLAUDE.md
Instructions for lukascivil/json-difference, covering claude.md, general guidelines for working with nx, scaffolding & generators, when to use nxdocs and repository overview.
axis-axis2-c-core AGENTS.md
Instructions for apache/axis-axis2-c-core, covering agents.md — apache axis2/c, security threat model, soap is the majority deployment, high-priority scan areas and 1. http/2 transport (primary production path).
tokenfold AGENTS.md
Instructions for snchimata/tokenfold, covering repository guidelines, working principles, repository map, implementation conventions and validation.