What is aspose-pdf-cloud-mcp AGENTS.md?

Repository instructions for developing the Aspose.PDF Cloud command-line and MCP server project. They describe its Python code layout, build and test commands, style rules, and testing guidance.

Finding the right modules for PDF and storage changes, following project conventions, running tests, and using the documented development workflow.

They give contributors a shared set of rules for changing the project without overlooking its structure or verification steps.

How aspose-pdf-cloud/aspose-pdf-cloud-mcp configures Codex and OpenCod

Reuse

Borrowing it

Nothing to install: this file belongs to aspose-pdf-cloud/aspose-pdf-cloud-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.

Copy the file

curl -O https://raw.githubusercontent.com/aspose-pdf-cloud/aspose-pdf-cloud-mcp/main/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/aspose-pdf-cloud/aspose-pdf-cloud-mcp

Made for: Codex, OpenCode.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/aspose-pdf-cloud/aspose-pdf-cloud-mcp/agents-md/github.svg)](https://agentmods.dev/instructions/aspose-pdf-cloud/aspose-pdf-cloud-mcp/agents-md)

Your own site

<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/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.

Your own site · 80×15

<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="Reviewed on agentmods" width="80" height="20"></a>

Per session 1,212 This file is loaded in full into every session.

When invoked 1,212 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.01212	$0.01212
Opus 5.5	$0.00485	$0.00485
Sonnet 5.5	$0.00242	$0.00242
Haiku 4.5	$0.00121	$0.00121

Measured 1mo ago against content hash ea094fd3f478, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 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.

AGENTS.md · 109 lines

How it starts

The opening of the file, as written. The whole thing — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Repository guidance

Project

Aspose.PDF Cloud CLI and MCP server, implemented in Python 3.11+ with a src/ layout. pyproject.toml declares Aspose SDK 26.x, MCP SDK 2.x, Typer, Rich, and typing-extensions. Both aspose-pdf-cloud-cli and apdf invoke aspose_pdf_cloud_mcp.cli:main; apdf mcp serve starts the MCP server.

Code organization

src/aspose_pdf_cloud_mcp/: application code.
storage_operations.py, document_operations.py, extraction_operations.py, and output_operations.py: domain operations.
operations.py: stable compatibility facade used by both transports.
cli.py: Typer commands and human/JSON output.
mcp_server.py: MCP tool declarations; mcp_adapter.py: response envelopes.
config.py and client.py: credentials/configuration and SDK client creation.
page_selectors.py, result_types.py, errors.py, and io_utils.py: shared parsing, typed contracts, error sanitization, and atomic writes.
test/: pytest unit, contract, and opt-in live tests.
docs/ and examples/: usage, architecture, security, and client configuration.
src/aspose_pdf_cloud_mcp/resources/skills/aspose-pdf-cloud-mcp/: bundled agent skill and references, installed by skill_installer.py.

Read docs/architecture.md before changing operations or transport contracts. Add behavior to the appropriate domain module and export it through operations.py. Keep SDK calls out of CLI and MCP wrappers. Preserve equivalent arguments and behavior across both surfaces; cover shared changes in test/test_contracts.py.

Use the MCP v2 MCPServer API from mcp.server.mcpserver, matching existing code. Follow existing four-space indentation, type annotations, and narrow module responsibilities. Do not hand-edit generated _version.py or replace the dynamic version with a static version.

Version and release maintenance

Version 1.0.0 is the existing release; current development targets 1.1.0. Preserve the v1.0.0 tag and the historical 1.0.0 changelog entry. Keep ongoing changes under Unreleased until preparing the 1.1.0 release, then rename that section to 1.1.0 with the actual release date.

Read the full file on GitHub · 109 lines

Changes

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 Changed · +17 lines · +272 tokens per session ea094fd3f478
2mo ago First seen · 92 lines · 940 tokens per session scan A ae0c85339107

Subscribe to this mod's changes

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 28d ago), licensed MIT. It adds 1,212 tokens to every session, about $0.0048 per session on Opus 5.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.

aspose-pdf-cloud-mcp AGENTS.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
aspose-pdf-cloud-mcp AGENTS.mdaspose-pdf-cloud/aspose-pdf-cloud-mcp	Instructions file	0	28d ago	MIT	A	1,212	Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	today	MIT	A	7,461	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	5,685	GitHub Copilot
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	3,093	GitHub Copilot
vscode model-prompts.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	2,022	GitHub Copilot

aspose-pdf-cloud-mcp: Instructions file for Codex