Borrowing it
Nothing to install: this file belongs to Smartoire/paxaver-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/Smartoire/paxaver-mcp/main/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/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/smartoire/paxaver-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/smartoire/paxaver-mcp/agents-md.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.01174 | $0.01174 |
| Opus 5.5 | $0.00470 | $0.00470 |
| Sonnet 5.5 | $0.00235 | $0.00235 |
| Haiku 4.5 | $0.00117 | $0.00117 |
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 13d 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.
Working rules
- Follow system, developer, and user instructions first. Within repository guidance, more specific
AGENTS.mdfiles override parent guidance. - Run commands from this repository root. Use Node and pnpm versions from
package.json. - Check
git status --shortbefore editing. Preserve user changes. Inspect existing code, consumers, and tests before adding a tool or dependency. - Read CONTRIBUTING.md. Internal documentation (architecture, authentication, authorization, tool reference, deployment, security model, test scenarios) lives in the private Paxaver monorepo under
docs/paxaver-mcp/; it is intentionally not in this public repo. The sibling platform repository has its own instructions.
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.ts— Tool schema exportsserver/— MCP server implementationtools/— Tool handlerstransport/— Streamable HTTP transport
apps/mcp/tests/— Unit, protocol, and smoke tests
Internal documentation is kept out of this repository: it lives in the private
Paxaver monorepo under docs/paxaver-mcp/ (architecture.md,
authentication.md, authorization.md, tools.md, deployment.md,
security.md, compatibility.md, migration.md, TEST_SCENARIOS.md,
CONTEXT-MAP.md, privacy/compliance.md).
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.
- 13d ago Changed · +5 lines · +115 tokens per session 063b7c103b0c
- 22d ago Changed · +12 tokens per session 95bd83500d85
- 1mo ago Changed · -5 lines · +223 tokens per session d650da64640a
- 2mo 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 yesterday), licensed Apache-2.0. It adds 1,174 tokens to every session, about $0.0047 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.
Other instructions, from other repositories
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.