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/lukasrepublic/agentic-foundry/agents-mdgit clone --depth 1 https://github.com/lukasrepublic/agentic-foundryWhat 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.00461 | $0.00461 |
| Opus 5 | $0.00230 | $0.00230 |
| Sonnet 5 | $0.00092 | $0.00092 |
| Haiku 4.5 | $0.00046 | $0.00046 |
Grade A, and why
agentic-foundry 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.
What it actually says
AGENTS.md — orientation for coding agents working in this repo
This repo is a Claude Code plugin (foundry): skills in skills/*/SKILL.md, personas
in agents/, hooks in hooks/ (wired by hooks/hooks.json), Python tooling in scripts/,
tests in tests/, templates in context/, stack profiles in packs/.
Ground rules
- Run the tests:
python3 -m pytest tests/ -q(full suite, ~1 min; the certify-fixture module boots local servers) andpython3 scripts/foundry-doctor.py(must printDOCTOR-GREEN). Both must be green before any PR. - Never weaken an assertion to make a test pass. Fix the code or flag the test.
- No claim beyond shipped enforcement: docs and skill prose must never describe guarantees the code doesn't provide. When you change behavior, change the prose in the same PR.
- Skill frontmatter is load-bearing: every
skills/*/SKILL.mdmust keep YAML-parseable frontmatter withnameanddescription; the doctor checks all of them. - Versions are pinned: GitHub Actions by 40-char SHA; dependency changes go through the standing-versions discipline — don't float anything.
- Git discipline: branch per change, PR-then-merge, no force-push to
main. The repo's own PreToolUse hook will refusegh pr merge --adminand any merge ahead of green checks — that's by design, not a bug to work around. - PR trailers: code-change PRs carry a
Spec:trailer naming the authorizing spec (thespec-linkCI gate checks it; docs-only diffs are exempt).
Where to learn more
README → docs/QUICKSTART.md → docs/architecture.md → docs/glossary.md. The changelog is the authoritative history.
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 · 31 lines · 461 tokens per session scan A f183fae2177a
agentic-foundry AGENTS.md is an instructions file published in the GitHub repository lukasrepublic/agentic-foundry (1 stars, last pushed 2d ago), licensed MIT. It adds 461 tokens to every session, about $0.0023 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
ii-agent AGENTS.md
Instructions for Intelligent-Internet/ii-agent, covering ii-agent contributor guide, quick start, repository map, mandatory rules and architecture.
intelligent-terminal rust.instructions.md
Concise Rust coding conventions for this repository.
Browser4 CLAUDE.md
Instructions for platonai/Browser4, covering browser4 — project context for claude, architecture, key dispatch chain (cli → browser), batch commands and e2e test structure.
nimbalyst AGENTS.md
AGENTS.md instructions for nimbalyst/nimbalyst: At the beginning of every AI session, read the root CLAUDE.md and any applicable package-level CLAUDE.md before taking actions.
sortie copilot-instructions.md
Instructions for sortie-ai/sortie, covering sortie coding & review standards, 1. layered imports (downward only; violation is critical), 2. concurrency safety, 3. workspace path safety (critical: security boundary) and 4. persistence (sqlite).
GENesis-AGI AGENTS.md
AGENTS.md instructions for WingedGuardian/GENesis-AGI, covering agent instructions, code review mandate (adversarial), gitnexus — code intelligence (advisory), genesis capability surface and skills.