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/trsdn/mcp-server-ppt/documentation-structuregit clone --depth 1 https://github.com/trsdn/mcp-server-pptWhat 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.00898 | $0.00898 |
| Opus 5 | $0.00449 | $0.00449 |
| Sonnet 5 | $0.00180 | $0.00180 |
| Haiku 4.5 | $0.00090 | $0.00090 |
Grade A, and why
mcp-server-ppt 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 2d 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 — 117 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- Main project overview - ✅
SECURITY.md- Security policy (GitHub standard) - ✅
LICENSE- License file - ❌ NO temporary files (SUMMARY, FIX, BUG, TESTS, DOCS, etc.)
docs/ - Implementation Documentation
Purpose: How things work, how to use them, architectural decisions
Categories:
- User Guides:
CONTRIBUTING.md - Developer Guides:
DEVELOPMENT.md,PRE-COMMIT-SETUP.md - Process Docs:
RELEASE-STRATEGY.md,MCP_REGISTRY_PUBLISHING.md,NUGET-GUIDE.md - Architecture:
ADR-*.md(Architecture Decision Records) - Infrastructure:
AZURE_SELFHOSTED_RUNNER_SETUP.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)
Document Lifecycle
Before Creating a Doc
- Is this permanent? → YES: Use proper location above
- Is this temporary? → Put in PR/Issue/commit message instead
- Does equivalent doc exist? → Update existing, don't duplicate
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.
- 2d ago First seen · 117 lines · 898 tokens per session scan A 7da2aa7dcf9b
mcp-server-ppt documentation-structure.instructions.md is an instructions file published in the GitHub repository trsdn/mcp-server-ppt (36 stars, last pushed 7d ago), licensed MIT. It adds 898 tokens to every session, about $0.0045 per session on Opus 5. A static security scan graded it A with 0 findings. It comes from a forked repository.
Other instructions, from other repositories
langgraph AGENTS.md
AGENTS.md instructions for langchain-ai/langgraph, covering agents instructions, corridor security analysis, libraries and dependency map.
maui performance-hotpaths.instructions.md
Instructions for dotnet/maui, covering performance-critical path rules, hot paths in maui, allocation avoidance, caching and invalidation and collection iteration.
gptme AGENTS.md
AGENTS.md instructions for gptme/gptme, covering agent instructions for gptme, git workflow, code style, testing and project structure.
AstrBot copilot-instructions.md
Copilot instructions for AstrBotDevs/AstrBot, covering astrbot development instructions, working effectively, bootstrap and install dependencies, running the application and dashboard build (vue.js/node.js).
mcp-dotnet-samples AGENTS.md
Instructions for microsoft/mcp-dotnet-samples, covering agents.md - mcp .net samples, project overview, project structure and architecture, repository organization and sample components.
chatgpt-cli CLAUDE.md
Instructions for kardolus/chatgpt-cli, covering chatgpt-cli — release runbook, prerequisites, 1. cut the release, 2. publish the github release + binaries and 3. update the homebrew tap.