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/feanorscodesl/imladris/agents-mdgit clone --depth 1 https://github.com/FeanorsCodeSL/imladrisWrote 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/feanorscodesl/imladris/agents-md)<a href="https://agentmods.dev/instructions/feanorscodesl/imladris/agents-md"><img src="https://agentmods.dev/badge/instructions/feanorscodesl/imladris/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.01194 | $0.01194 |
| Opus 5 | $0.00597 | $0.00597 |
| Sonnet 5 | $0.00239 | $0.00239 |
| Haiku 4.5 | $0.00119 | $0.00119 |
Grade A, and why
imladris 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Imladris is a Python + FastMCP project: a cross-harness multi-model deliberation
(Fusion) MCP server, run as an MCP stdio subprocess. The deliberation engine
fans a prompt out to a configurable panel of OpenAI-compatible LLM providers
(1–8), runs one API-side analysis judge, and lets the harness's own native model
author the final answer from the judge's analysis plus all raw panel answers. (The
curator and anonymization passes were removed.) The design and current contracts
live in docs/architecture/. No FastAPI/REST, no HTTP server, no Docker —
those were removed.
Project Structure & Module Organization
orchestrator/— the service package:mcp_server.py(FastMCPimladris+imladris_status+imladris_clear_sessionstools, the/counciland/council-sessionprompts,main()),panel.py(fan-out + degradation + session orchestration),judge.py(the analysis judge),sessions.py(local session store- per-member
messages[]+ window-aware compaction),model_catalog.py(models.dev fetch/cache/seed + context-window resolver),budget.py(advisory context-budget estimator),providers/(the single OpenAI-compatible kind + factory),settings.py(JSON/YAML + env config; roles panel/judge),models.py,interfaces.py,costing.py,json_utils.py,fakes.py,data/(bundled model-catalog seed),cli/(theimladrisconfigurator TUI),tests/.
- per-member
config/—imladris.example.yaml(illustrative provider list, presets, pricing).scripts/—install.sh,install.ps1, and stdio smoke helpers (Bash + PowerShell).docs/architecture/— live architecture, pipeline, configuration, security, deployment, and dependency references.
The project slug is imladris: the MCP tool id and server id
(FastMCP("imladris")), the console scripts (imladris, imladris-mcp), and the
local skill name. The user-facing prompts are /council (one-shot) and
/council-session (stateful). Keep imladris stable.
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 · 80 lines · 1,194 tokens per session scan A 80a3bd5e45b0
imladris AGENTS.md is an instructions file published in the GitHub repository FeanorsCodeSL/imladris (4 stars, last pushed 2mo ago), licensed MIT. It adds 1,194 tokens to every session, about $0.0060 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
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.