Borrowing it
Nothing to install: this file belongs to ogprotege/amex-anaylsis-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/ogprotege/amex-anaylsis-mcp/main/AGENTS.mdgit clone --depth 1 https://github.com/ogprotege/amex-anaylsis-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/ogprotege/amex-anaylsis-mcp/agents-md)<a href="https://agentmods.dev/instructions/ogprotege/amex-anaylsis-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/ogprotege/amex-anaylsis-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/ogprotege/amex-anaylsis-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/ogprotege/amex-anaylsis-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.00405 | $0.00405 |
| Opus 5 | $0.00202 | $0.00202 |
| Sonnet 5 | $0.00081 | $0.00081 |
| Haiku 4.5 | $0.00040 | $0.00040 |
Grade A, and why
amex-anaylsis-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 10d 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.
What it actually says
AGENTS.md
Cursor Cloud specific instructions
This repo is a TypeScript / Node.js MCP server for Amex spending analysis with vendor unmasking. There is no HTTP server and no database — it speaks the Model Context Protocol over stdio and reads CSV files.
Dependencies (npm install) are installed automatically by the startup update
script, so you normally don't need to install anything to start working.
Running / testing (commands live in package.json scripts)
- Tests (no personal data needed):
npm test. Unmasking only:npm run test-unmasking. - Demo that writes
data/test-amex.csvandoutput/test-analysis.xlsx:npm run demo. - Type-check / compile:
npm run build(usesamex-mcp-tsconfig.json, emitsdist/). - Dev server:
npm run dev(standard toolset viatsx).npm run dev:enhancedfor the full catalog.npm run dev:basicfor the original six tools plusload_statement. - CLI:
npx tsx src/cli.ts --help.
Non-obvious notes
- The server communicates over stdio, so "running" it just blocks waiting for
JSON-RPC on stdin. To smoke-test it without an MCP client, pipe a newline-delimited
initialize+notifications/initialized+tools/listJSON-RPC sequence intonpx tsx amex-mcp-server.tsand read the responses from stdout. - Analysis code lives in
src/. Rootamex-mcp-server.ts/amex-mcp-server-enhanced.tsare entry wrappers. - Generated
data/*.csvandoutput/exports are gitignored; tests use in-memory fixtures. npm auditreports some advisories from transitive deps; they do not affect dev/test.
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.
- 10d ago First seen · 27 lines · 405 tokens per session scan A 3f02390f66c0
amex-anaylsis-mcp AGENTS.md is an instructions file published in the GitHub repository ogprotege/amex-anaylsis-mcp (3 stars, last pushed 20d ago), licensed MIT. It adds 405 tokens to every session, about $0.0020 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.
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).
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.