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/sbroenne/mcp-server-excel/documentation-structuregit clone --depth 1 https://github.com/sbroenne/mcp-server-excelWhat 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.01534 | $0.01534 |
| Opus 5 | $0.00767 | $0.00767 |
| Sonnet 5 | $0.00307 | $0.00307 |
| Haiku 4.5 | $0.00153 | $0.00153 |
Grade A, and why
mcp-server-excel documentation-structure.instructions.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 — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Structure & Standards
Clear hierarchy prevents temporary doc accumulation
📁 Documentation Hierarchy
Root Level - Essential User-Facing Only
- ✅
README.md- GitHub acquisition page and quick start - ✅
FEATURES.md- Feature navigation hub and tool-selection guide - ✅
CHANGELOG.md- Generated release history - ✅
SECURITY.md- Security policy (GitHub standard) - ✅
PRIVACY.md- Privacy policy - ✅
LICENSE- License file - ❌ NO temporary files (SUMMARY, FIX, BUG, TESTS, DOCS, etc.)
docs/ - Canonical Documentation
Purpose: Feature references, user guides, architecture, and development processes
Categories:
- Feature References:
features/*.md - User Guides:
INSTALLATION*.md,USE-CASES.md,CONTRIBUTING.md - Architecture:
ARCHITECTURE.md,ADR-*.md - Developer Guides:
DEVELOPMENT.md,PRE-COMMIT-SETUP.md - Process Docs:
RELEASE-STRATEGY.md,MCP_REGISTRY_PUBLISHING.md,NUGET-GUIDE.md - Infrastructure:
infrastructure/azure/README.md - Standards:
TEST-NAMING-STANDARD.md
Naming Convention:
- ✅
TOPIC-NAME.md(ALL CAPS for discoverability) - ✅
ADR-NNN-DECISION-NAME.md(Architecture Decision Records) - ❌ NO
SUMMARY.md,FIX.md,TESTS.md(temporary naming)
specs/ - Feature Specifications
Purpose: What should be built (requirements, design, before implementation)
Naming Convention:
- ✅
FEATURE-NAME-SPEC.md - ✅
COMPONENT-API-SPECIFICATION.md
src/[Component]/ - Component Documentation
Purpose: Component-specific overview and usage
Files:
- ✅
README.md- Component overview, quick start
Temporary Documentation Rules
❌ Forbidden at Root Level
FIX-*.md- Document fixes in PRs, not filesBUG-*.md- Track bugs in GitHub IssuesTESTS-*.md- Test info belongs in test filesDOCS-*.md- Update actual docs, don't create meta-docsSUMMARY-*.md- Summarize in PR descriptions
✅ Where to Put Content Instead
- Bug investigation → GitHub Issue comments
- Fix summary → PR description
- Architecture decisions →
docs/ADR-NNN-DECISION-NAME.md - Temporary notes → Branch commit messages (deleted after merge)
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 · 157 lines · 1,534 tokens per session scan A e5368bbad205
mcp-server-excel documentation-structure.instructions.md is an instructions file published in the GitHub repository sbroenne/mcp-server-excel (645 stars, last pushed 3d ago), licensed MIT. It adds 1,534 tokens to every session, about $0.0077 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
mcp-server-powerpoint copilot-instructions.md
Instructions for sbroenne/mcp-server-powerpoint, covering project instructions — powerpointmcp, critical files (read these first), sister projects, what is powerpointmcp? and session model (mcp server).
mcp-server-powerpoint architecture-patterns.instructions.md
Instructions for sbroenne/mcp-server-powerpoint, covering architecture patterns, .net class design (mandatory), layered architecture (critical), command pattern and structure (per domain).
mcp-server-powerpoint critical-rules.instructions.md
Instructions for sbroenne/mcp-server-powerpoint, covering critical rules - must follow, rule 1: success/errormessage invariant, rule 1b: no exception suppression in core, rule 30: real-com integration tests only, strict tdd and rule: 1-based indexing everywhere.
mcp-server-powerpoint mcp-server-guide.instructions.md
Instructions for sbroenne/mcp-server-powerpoint, covering mcp server development guide, llm-facing content rules, two kinds of tools: hand-written vs. generated, implementation pattern: single hand-written dispatch tool and error handling (mandatory).
mcp-server-powerpoint testing-strategy.instructions.md
Instructions for sbroenne/mcp-server-powerpoint, covering testing strategy, strict tdd (red → green), test project layout, serialization is mandatory and trait tagging (required for surgical filtering).
mcp-server-amazon CLAUDE.md
Instructions for rigwild/mcp-server-amazon, covering claude.md, development commands, install dependencies (use -d flag for puppeteer), build typescript to javascript and clean mock html files.