Borrowing it
Nothing to install: this file belongs to lukasrepublic/agentic-foundry. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/lukasrepublic/agentic-foundry/main/AGENTS.mdgit clone --depth 1 https://github.com/lukasrepublic/agentic-foundryWrote 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/lukasrepublic/agentic-foundry/agents-md)<a href="https://agentmods.dev/instructions/lukasrepublic/agentic-foundry/agents-md"><img src="https://agentmods.dev/badge/instructions/lukasrepublic/agentic-foundry/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/lukasrepublic/agentic-foundry/agents-md"><img src="https://agentmods.dev/badge/instructions/lukasrepublic/agentic-foundry/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.00952 | $0.00952 |
| Opus 5.5 | $0.00381 | $0.00381 |
| Sonnet 5.5 | $0.00190 | $0.00190 |
| Haiku 4.5 | $0.00095 | $0.00095 |
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 26d 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — the standing rules for coding agents working in this repo
Claude Code reads this file as the project's instructions when there is no CLAUDE.md
(since 2.1.278, 2026-09-18); other agent tools read it by convention. It holds only the
invariant rules of this repo, each verifiable against the tree. Orchestration and
session-specific prompts live elsewhere (skills/, the adopter's own workspace).
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, ~10 min measured 2026-09-21; the certify-fixture module boots a localhttp.server) with the pinned dev requirements (requirements-dev.txt; CI uses Python 3.12), andpython3 scripts/foundry-doctor.py(must printDOCTOR-GREEN— run from this repo as the session root; run from a hosting workspace it reports the control-plane RED by design). Both must be green locally before the first push of a branch. - The hook's executable content is digest-pinned in
tests/fixtures/release/cut-release-reconcile-sweep.yaml; a deliberate change tohooks/foundry-git-discipline.shadvances the pin with a numbered ledger entry there. - 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 (hooks/foundry-git-discipline.sh) refuses force-pushes to a protected branch,gh pr merge --admin, and any merge ahead of green checks — by design, not a bug to work around. Atoms PR intorelease/<version>;mainreceives one PR per release;hotfix/<id>→mainis the one exception. Seedocs/how-to/branching-and-cleanup.md. - Text that names a guarded command goes through Write/Edit, never a Bash heredoc. The
hook scans the whole command string, heredoc bodies included, so
cat > f <<EOFwith a body mentioning a force-push or--adminis refused (docs, tests, commit bodies, PR bodies). An inline-m "…"is fine. Seedocs/merge-floor.md. - The retired-framework token fails CI.
ci.ymlgreps the whole tree, case-insensitive, for the three-letter name of the retired environment tool (the one that starts withcand ends withx); any occurrence in any file — code, comment, doc, fixture — is red. - PR trailers: code-change PRs carry a
Spec:trailer naming the authorizing spec (thespec-link-basegate in.github/workflows/btb-gates-base.ymlchecks it; docs-only diffs are exempt). Security-relevant changes (this hook, CI gate workflows, authorization, provenance) get an independent reviewer — self-review has missed real bugs here.
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.
- 26d ago Changed · +22 lines · +491 tokens per session 8151598b3486
- 1mo 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 12d ago), licensed MIT. It adds 952 tokens to every session, about $0.0038 per session on Opus 5.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
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).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.