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/jmetal/jmetalpy/agents-mdgit clone --depth 1 https://github.com/jMetal/jMetalPyWrote 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/jmetal/jmetalpy/agents-md)<a href="https://agentmods.dev/instructions/jmetal/jmetalpy/agents-md"><img src="https://agentmods.dev/badge/instructions/jmetal/jmetalpy/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 | $0.01082 | $0.01082 |
| Opus 5 | $0.00541 | $0.00541 |
| Sonnet 5 | $0.00216 | $0.00216 |
| Haiku 4.5 | $0.00108 | $0.00108 |
Grade A, and why
jMetalPy 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 4d 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Guidance for AI assistants and human contributors working on jMetalPy.
Project
jMetalPy is the Python implementation of the jMetal framework
for multi-objective optimization with metaheuristics. Source layout: src/jmetal/ (algorithm/,
core/, operator/, problem/, util/, lab/), tests mirror that structure under tests/,
runnable examples live in examples/, Sphinx docs in docs/. Target: Python 3.11+.
Scope
- Use agents for refactors, tests, docs, examples, and small-to-medium utilities.
- Avoid delegating API changes, licensing, or research conclusions without maintainer sign-off.
- Keep changes scoped; prefer incremental PRs over broad rewrites. Large mechanical changes (e.g. repo-wide reformatting) are fine when explicitly requested, but call out the blast radius before running them.
Coding Standards
ALWAYS follow the rules in CODING_GUIDELINES.md. Short version:
- English-only identifiers, comments, and docstrings (Google style: Args/Returns/Raises)
- Type new/modified code as a style convention — there's no static type checker in CI (tried
mypy, dropped it: findings were mostly it failing to follow deliberate duck-typing/generics
in 6+ year old internal code, not real bugs; see
CODING_GUIDELINES.md§5) @dataclass(slots=True, frozen=True)only for stateless data (config, DTOs) — never forSolutionand other containers algorithms mutate in place- One
returnper function except guard clauses; keep functions small; avoid nested conditionals - Exceptions are the default error-handling mechanism; the
Ok[T] | Errpattern is reserved for I/O-boundary code only - Tests: pytest, AAA structure,
test_should_<behavior>naming (not given-when-then — that's a Java/BDD convention, not idiomatic here), group related cases inclass Test<Subject>:, prefer@pytest.mark.parametrizeover near-duplicate tests
Git Conventions
ALWAYS follow the rules in GIT_GUIDELINES.md. Short version:
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.
- 4d ago First seen · 86 lines · 1,082 tokens per session scan A cbcae692144b
jMetalPy AGENTS.md is an instructions file published in the GitHub repository jMetal/jMetalPy (612 stars, last pushed 1mo ago), licensed MIT. It adds 1,082 tokens to every session, about $0.0054 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
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.