Borrowing it
Nothing to install: this file belongs to trsdn/mcp-server-ppt. 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/trsdn/mcp-server-ppt/main/.github/instructions/documentation-structure.instructions.mdgit clone --depth 1 https://github.com/trsdn/mcp-server-pptWrote 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/trsdn/mcp-server-ppt/documentation-structure)<a href="https://agentmods.dev/instructions/trsdn/mcp-server-ppt/documentation-structure"><img src="https://agentmods.dev/badge/instructions/trsdn/mcp-server-ppt/documentation-structure/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/trsdn/mcp-server-ppt/documentation-structure"><img src="https://agentmods.dev/badge/instructions/trsdn/mcp-server-ppt/documentation-structure.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.00898 | $0.00898 |
| Opus 5.5 | $0.00359 | $0.00359 |
| Sonnet 5.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 1mo 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.
- 1mo 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 (41 stars, last pushed yesterday), licensed MIT. It adds 898 tokens to every session, about $0.0036 per session on Opus 5.5. A static security scan graded it A with 0 findings. It comes from a forked repository.
Other instructions, from other repositories
plan-forge dapr.instructions.md
Dapr patterns for .NET — building blocks, component config, sidecar architecture, multi-tenant isolation, workflows, state management, secrets.
plan-forge database.instructions.md
Database patterns for .NET — Dapper/EF Core 10, parameterized queries, migration strategy.
plan-forge naming.instructions.md
Azure naming conventions — Microsoft CAF abbreviations, constraints, uniqueness, tagging.
plan-forge caching.instructions.md
Caching patterns for .NET — IDistributedCache, Redis, in-memory, cache-aside, TTL strategies.
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.