Borrowing it
Nothing to install: this file belongs to aspose-words/Aspose.Words-MCP. 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/aspose-words/Aspose.Words-MCP/main/AGENTS.mdgit clone --depth 1 https://github.com/aspose-words/Aspose.Words-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/aspose-words/aspose.words-mcp/agents-md)<a href="https://agentmods.dev/instructions/aspose-words/aspose.words-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/aspose-words/aspose.words-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.00792 | $0.00792 |
| Opus 5 | $0.00396 | $0.00396 |
| Sonnet 5 | $0.00158 | $0.00158 |
| Haiku 4.5 | $0.00079 | $0.00079 |
Grade A, and why
Aspose.Words-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 7d 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Purpose
This repository is updated by coding agents during Aspose.Words release alignment work.
When making changes, preserve the existing repository structure, conventions, and architectural patterns.
Required implementation rules
1. Use explicit API only
Do not use getattr() or hasattr() for Aspose.Words API access.
All Aspose.Words API used by the MCP server must be referenced explicitly and directly.
If the server is being updated for a target Aspose.Words release, assume that the target API is the intended and supported API surface.
Do not add dynamic attribute checks to support old or uncertain API shapes.
Do not add compatibility shims based on getattr(), hasattr(), or similar reflective fallbacks.
2. Do not hide library usage errors
Do not use try/except to hide, suppress, or silently bypass incorrect Aspose.Words API usage.
If the MCP server uses the library incorrectly, that failure must remain visible during development and testing.
Do not catch exceptions only to continue execution with fallback behavior, partial behavior, or silent degradation.
Allowed exception handling is narrow and explicit only when it is required for:
- test assertions,
- user-input validation,
- external I/O boundaries,
- conversion of an error into a clearer MCP-facing error when the underlying failure remains explicit and testable.
Do not wrap Aspose.Words API calls in broad try/except blocks for defensive compatibility.
3. Tests must be updated with server changes
Any change to MCP server code must be accompanied by the necessary test updates.
If server behavior changes, tool coverage changes, tool parameters change, schemas change, manifests change, descriptions change, or new functionality is exposed, update existing tests and add new tests where required.
Do not leave server changes without corresponding test coverage adjustments.
4. Server versioning
The MCP server version must match the version of the Aspose.Words library it is aligned with.
When updating the server for a new Aspose.Words release, ensure that the version in pyproject.toml (and any other version-tracking files) is updated to match the target library version.
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.
- 7d ago First seen · 64 lines · 792 tokens per session scan A 8dfd06a2cb65
Aspose.Words-MCP AGENTS.md is an instructions file published in the GitHub repository aspose-words/Aspose.Words-MCP (4 stars, last pushed 1mo ago), licensed MIT. It adds 792 tokens to every session, about $0.0040 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-31.
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).
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).
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.