Borrowing it
Nothing to install: this file belongs to mythographica/strategy. 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/mythographica/strategy/main/AGENTS.mdgit clone --depth 1 https://github.com/mythographica/strategyWrote 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/mythographica/strategy/agents-md)<a href="https://agentmods.dev/instructions/mythographica/strategy/agents-md"><img src="https://agentmods.dev/badge/instructions/mythographica/strategy/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/mythographica/strategy/agents-md"><img src="https://agentmods.dev/badge/instructions/mythographica/strategy/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.04053 | $0.04053 |
| Opus 5.5 | $0.01621 | $0.01621 |
| Sonnet 5.5 | $0.00811 | $0.00811 |
| Haiku 4.5 | $0.00405 | $0.00405 |
Grade A, and why
strategy 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 24d 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 — 324 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md - @mnemonica/strategy
Guidance for AI agents working on the Mnemonica Strategy MCP Server.
What this is
@mnemonica/strategy is the live bridge between a running Mnemonica
runtime and the tools around it — the center of the topology star: agents
drive it over MCP; applications self-host its channel; visualization
tooling (Mnemographica) connects as a monitoring client. It attaches to a
target Node.js process via the Chrome Debug Protocol (CDP) — zero
instrumentation of the target — then moves construction traffic onto a
WebSocket channel injected into that process. Apps that may instrument
themselves can skip CDP entirely: see The app-side client module
below. The long-term UX goal: errored trace → one click → debugger
reproduction on real data.
The development-mode side of the same channel (defining and swapping
constructors in a live app, no restart) is documented in
docs/live-craft.md.
The 3-tool surface (do not expand without discussion)
The server exposes exactly 3 MCP tools (src/server.ts):
- execute —
{ context, command, message }runs a command file. - list —
{ context? }lists commands, grouped by context and folder. - help —
{ context, command }returns metadata, schema, examples.
Arguments travel as a JSON string in message; every command parses
args.message first. This 3-tool design is deliberate and liked — do not
propose adding tools lightly.
Execution model — the truth table
| Where code runs | How |
|---|---|
| Strategy MCP process (local) | executeCommand in src/server.ts runs EVERY command file locally: module.exports.run files via require(), all others via new Function('ctx', body). There is no remote eval of command files. |
| Target runtime (remote) | Only code passed to Runtime.evaluate() over CDP runs in the target: (a) CDPConnection.evaluate() / getMnemonicaTypes(), (b) cdp-scripts/*.js payloads that RPC wrapper commands read from disk and send. |
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.
- 24d ago Changed · +3 lines · +15 tokens per session c9fbfebc2cd5
- 1mo ago Changed · -2 lines · -56 tokens per session ce11ec8a02d1
- 1mo ago Changed · -16 tokens per session 0ba7ca66d4a8
- 1mo ago Changed · +52 lines · +815 tokens per session 45ab696e3296
- 1mo ago First seen · 271 lines · 3,295 tokens per session scan A 46e278bf34b0
strategy AGENTS.md is an instructions file published in the GitHub repository mythographica/strategy (0 stars, last pushed 23d ago), licensed MIT. It adds 4,053 tokens to every session, about $0.0162 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-09-01.
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.
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.
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).