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/linxule/interpretive-orchestration/agents-mdgit clone --depth 1 https://github.com/linxule/interpretive-orchestrationWrote 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/linxule/interpretive-orchestration/agents-md)<a href="https://agentmods.dev/instructions/linxule/interpretive-orchestration/agents-md"><img src="https://agentmods.dev/badge/instructions/linxule/interpretive-orchestration/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.01396 | $0.01396 |
| Opus 5 | $0.00698 | $0.00698 |
| Sonnet 5 | $0.00279 | $0.00279 |
| Haiku 4.5 | $0.00140 | $0.00140 |
Grade A, and why
interpretive-orchestration 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 169 lines · 1,396 tokens per session scan A 1001f19bb27a
interpretive-orchestration AGENTS.md is an instructions file published in the GitHub repository linxule/interpretive-orchestration (17 stars, last pushed 1mo ago), with no licence file. It adds 1,396 tokens to every session, about $0.0070 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
academic-commercialization-agent AGENTS.md
Instructions for shuxiachai/academic-commercialization-agent, covering agents.md — working on this project, what it is, commands, hard conventions and where the reasoning lives.
AI-Powered-Literature-Review-Skills AGENTS.md
Instructions for stephenlzc/AI-Powered-Literature-Review-Skills, covering agents.md - literature reviewer skill, 项目概述, 核心特性, 技术栈 and 项目结构.
BITE AGENTS.md
Instructions for RipeMangoBox/BITE, covering agent guide, working surface, local pipeline, branch sync policy and rules.
zissa-wiki CLAUDE.md
Instructions for MetamusicX/zissa-wiki, covering claude.md — research wiki schema, identity, architecture, folder conventions and raw/.
archilles CLAUDE.md
Instructions for kasssandr/archilles, covering claude.md, project overview, commands, installation and indexing.
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).