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/aspose-pdf-cloud/aspose-pdf-cloud-mcp/agents-mdgit clone --depth 1 https://github.com/aspose-pdf-cloud/aspose-pdf-cloud-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-pdf-cloud/aspose-pdf-cloud-mcp/agents-md)<a href="https://agentmods.dev/instructions/aspose-pdf-cloud/aspose-pdf-cloud-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/aspose-pdf-cloud/aspose-pdf-cloud-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 | $0.00940 | $0.00940 |
| Opus 5 | $0.00470 | $0.00470 |
| Sonnet 5 | $0.00188 | $0.00188 |
| Haiku 4.5 | $0.00094 | $0.00094 |
Grade A, and why
aspose-pdf-cloud-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 4d 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
This repository is a Python CLI and MCP server for Aspose.PDF.
src/aspose_pdf_cloud_mcp/: application package.config.py: environment and.envconfiguration loading.client.py: Aspose SDK client factory.storage_operations.py,document_operations.py,extraction_operations.py, andoutput_operations.py: focused business-operation domains.operations.py: stable facade shared by CLI and MCP transports.page_selectors.py: shared page/range parsing.result_types.py: typed operation and protocol contracts.mcp_adapter.py: common MCP success/error adaptation.cli.py: Typer command-line interface.mcp_server.py: FastMCP tool server.skill_installer.py: installs the bundledaspose-pdf-cloud-mcpagent skill.resources/skills/aspose-pdf-cloud-mcp/: packaged Codex/Claude Code skill.test/: pytest unit and live smoke tests.docs/: install, MCP, Codex prompt, live test, and security notes.examples/: copy-pasteable local configuration examples.README.md: user-facing setup and command examples.
Keep new behavior in the appropriate domain operation module first, export it through operations.py, then expose it through CLI and MCP wrappers. Never duplicate Aspose SDK calls in transport code.
Build, Test, and Development Commands
Install locally in editable mode:
python -m pip install -e ".[dev]"
Run the full default test suite:
python -m pytest -q
Run only live Aspose Cloud smoke tests:
$env:ASPOSE_RUN_LIVE_TESTS = "1"
python -m pytest -q -m live
Check CLI help:
python -m aspose_pdf_cloud_mcp.cli --help
Install the bundled Aspose.PDF skill locally:
python -m aspose_pdf_cloud_mcp.cli skill install codex --force
python -m aspose_pdf_cloud_mcp.cli skill install claude-code --project --force
Build and validate PyPI distributions:
python -m build
python -m twine check dist/*
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.
- 4d ago First seen · 92 lines · 940 tokens per session scan A ae0c85339107
aspose-pdf-cloud-mcp AGENTS.md is an instructions file published in the GitHub repository aspose-pdf-cloud/aspose-pdf-cloud-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 940 tokens to every session, about $0.0047 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
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.
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.
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).