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/eea/eea.agent.skills/agents-mdgit clone --depth 1 https://github.com/eea/eea.agent.skillsWhat 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.01342 | $0.01342 |
| Opus 5 | $0.00671 | $0.00671 |
| Sonnet 5 | $0.00268 | $0.00268 |
| Haiku 4.5 | $0.00134 | $0.00134 |
Grade A, and why
eea.agent.skills 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 2d 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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
EEA Agent Skills Repository
This file governs how AI agents work when editing the eea.agent.skills repository itself.
Note: This is the REPO-LOCAL instruction file. For the organization-wide harness that applies to all EEA projects, see
harness/EEA-HARNESS.md.
Prohibited Actions
- Do not edit
harness/EEA-HARNESS.mdwithout explicit user request — that's org-wide policy; changes affect every EEA project - Do not commit unmerged upstream changes to
src/skills/*/SKILL.md— always run./scripts/build.shfirst - Do not delete
EEA-OVERRIDES.mdfiles — these contain EEA-specific customizations - Do not add new top-level directories without updating this README and the harness routing rules
- Do not commit secrets in any file, including test fixtures and example configs
Build System
skills/ is auto-generated. Never edit it directly.
# Build a single skill (merges SKILL.md + EEA-OVERRIDES.md → skills/)
./scripts/build.sh docker-expert
# Build all skills (run with no arguments)
./scripts/build.sh
After any change to src/skills/*/SKILL.md or EEA-OVERRIDES.md, run ./scripts/build.sh and commit the skills/ changes.
CI fails if skills/ is out of sync (git status --porcelain skills/ must be clean).
The build script also copies references/, DESIGN.md, and assets/ if present.
Validation
# Full health check: repo consistency, catalog sync, agentskills spec compliance
./scripts/verify.sh
# Validate all source and merged skills against the Agent Skills specification
./scripts/validate-skills.sh
validate-skills.shauto-installsskills-ref(PyPI) into a temp venv ifagentskillsis missing.- CI runs both on every PR.
Skill Development Workflow
Adding a New Skill
- Create skill directory under
src/skills/{skill-name}/ - Add upstream
SKILL.md(if based on upstream source) - Create
EEA-OVERRIDES.mdwith EEA-specific customizations - Add
metadata.jsonwith skill metadata - Update
catalog.yamlwith new skill entry - Build merged skill:
./scripts/build.sh {skill-name} - Verify: check that
skills/{skill-name}/SKILL.mdwas generated correctly andgit statusshows the expected changes - Commit:
skill: add {skill-name}
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.
- 2d ago First seen · 140 lines · 1,342 tokens per session scan A 77d08de59665
eea.agent.skills AGENTS.md is an instructions file published in the GitHub repository eea/eea.agent.skills (2 stars, last pushed 25d ago), licensed MIT. It adds 1,342 tokens to every session, about $0.0067 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
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.
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).
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.