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/smartoire/paxaver-mcp/agents-mdgit clone --depth 1 https://github.com/Smartoire/paxaver-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/smartoire/paxaver-mcp/agents-md)<a href="https://agentmods.dev/instructions/smartoire/paxaver-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/smartoire/paxaver-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.00824 | $0.00824 |
| Opus 5 | $0.00412 | $0.00412 |
| Sonnet 5 | $0.00165 | $0.00165 |
| Haiku 4.5 | $0.00082 | $0.00082 |
Grade A, and why
paxaver-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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Purpose
This file defines the rules for AI agents that work in the Paxaver MCP repository.
Project Overview
The Paxaver MCP server is an AI-facing adapter over the Paxaver school community platform. It implements the Model Context Protocol (MCP) on Cloudflare Workers with RS256 JWT validation, capability-first authorization, and Streamable HTTP transport.
The server is a thin adapter. It contains no business logic and never touches the database, Stripe, or email directly. Every action is delegated to the private Paxaver backend API over a Cloudflare service binding.
Repository Structure
apps/mcp/src/— MCP server source codeapi/— Paxaver backend API clientauth/— JWT validation and authorizationdiscovery/— Well-known endpoints (RFC 9728, RFC 8414)lib/— Shared utilities (contracts, crypto, policy)schemas/— Tool input schemasserver/— MCP server implementationtools/— Tool handlerstransport/— Streamable HTTP transport
apps/mcp/tests/— Unit, protocol, and smoke testsdocs/— Documentation
Tech Stack
- TypeScript 6
- Cloudflare Workers
- Native
fetchhandler - jose (JWT validation)
- Vitest (testing)
- Wrangler 4
Build and Verification Commands
# Install dependencies
pnpm install
# Typecheck
pnpm typecheck
# Run tests
pnpm test
# Lint
pnpm lint
# Format check
pnpm format:check
# Build (dry-run)
pnpm build
# Security audit
pnpm security:audit
Architecture Rules
- The MCP server is a thin adapter. Do not add business logic.
- Delegate all actions to the Paxaver backend API via service bindings.
- Validate all trust-boundary inputs.
- Handle failures explicitly with sanitized, user-safe error messages.
- Do not expose secrets or private data in errors.
Authorization Model
- RS256 JWT validation via JWKS from the centralized Paxaver auth worker.
- Per-tool capability policy and role gating.
- OAuth 2.1 Authorization Code + PKCE (S256) flow.
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 · 129 lines · 824 tokens per session scan A 6ba2e4b4cbf5
paxaver-mcp AGENTS.md is an instructions file published in the GitHub repository Smartoire/paxaver-mcp (0 stars, last pushed today), licensed Apache-2.0. It adds 824 tokens to every session, about $0.0041 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).