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/sylphxai/smart-reader-mcp/agents-mdgit clone --depth 1 https://github.com/SylphxAI/smart-reader-mcpWrote 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/sylphxai/smart-reader-mcp/agents-md)<a href="https://agentmods.dev/instructions/sylphxai/smart-reader-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/sylphxai/smart-reader-mcp/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.1 | $0.00405 | $0.00405 |
| Opus 5 | $0.00202 | $0.00202 |
| Sonnet 5 | $0.00081 | $0.00081 |
| Haiku 4.5 | $0.00040 | $0.00040 |
Grade A, and why
smart-reader-mcp 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 5d 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.
This is a copy
89% identical to coderag AGENTS.md — 7 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
smart-reader-mcp — local agent notes only
Static engineering and delivery standards load from the active Skills runtime (SylphxAI/skills is binding instruction SSOT). Doctrine and Mission Control are retired historical lineage and must not be loaded as current instruction authority.
Local truth: PROJECT.md, .doctrine/project.json when present.
Boundary hazards
- Never commit secrets, tokens,
.envfiles, or credentials.
Local commands
bun run typecheckbun run testbun run buildbun run checkbun run validatecargo test --workspace- Prefer the narrowest affected check before full workspace runs.
- Report layers honestly: local diff · trunk FF · deploy · prod proof (do not collapse).
Validation notes
- Prefer the narrowest affected check before full workspace runs.
- Report layers honestly: local diff · trunk FF · deploy · prod proof (do not collapse).
Backend false-authority fence
Work: wi_01KYFN6993PMG8WD00Q51AE231
If this repository has completed a Rust backend cutover:
- Production backend behavior authority is the Rust crate/binary/service path declared in
sylphx.toml/ deploy manifests / packagebinnative path / Docker ENTRYPOINT. - Residual TypeScript service trees or alternate TS engines are not product authority unless explicitly proven still on the live path.
- Do not "fix production" by editing residual TypeScript and assuming deploy/runtime will pick it up.
- Prefer deleting residual TS backend trees after Rust sole proof; keep history in Git.
- Intentional TypeScript frontends, npm packaging wrappers, and native-binding surfaces may remain.
Repo-specific note
Rust binary is runtime authority; TS/npm packaging is not an alternate backend implementation.
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.
- 5d ago First seen · 45 lines · 405 tokens per session scan A 378858be66fa
smart-reader-mcp AGENTS.md is an instructions file published in the GitHub repository SylphxAI/smart-reader-mcp (0 stars, last pushed 28d ago), licensed MIT. It adds 405 tokens to every session, about $0.0020 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to coderag AGENTS.md, differing in 7 lines, and is treated as a copy.
Other instructions, from other repositories
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.
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.
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.
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).