Borrowing it
Nothing to install: this file belongs to coding-with-abbi/sap-sales-order-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/coding-with-abbi/sap-sales-order-mcp/master/CLAUDE.mdgit clone --depth 1 https://github.com/coding-with-abbi/sap-sales-order-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/coding-with-abbi/sap-sales-order-mcp/claude-md)<a href="https://agentmods.dev/instructions/coding-with-abbi/sap-sales-order-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/coding-with-abbi/sap-sales-order-mcp/claude-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/coding-with-abbi/sap-sales-order-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/coding-with-abbi/sap-sales-order-mcp/claude-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.00457 | $0.00457 |
| Opus 5 | $0.00229 | $0.00229 |
| Sonnet 5 | $0.00091 | $0.00091 |
| Haiku 4.5 | $0.00046 | $0.00046 |
Grade A, and why
sap-sales-order-mcp CLAUDE.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 9d 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
sap-sales-order-mcp — Root CLAUDE.md
Cross-cutting standards only. Topic-specific rules live in
.claude/rules/(path-scoped) so they load only when relevant. Keeps this file lean — avoids attention dilution.
Project
Production-ready MCP server for SAP S/4HANA Sales Order Management.
Sandbox-first (public SAP API Business Hub), offline-testable (no API key
needed for unit tests). Python 3.10+ under src/sap_sales_mcp/.
Cross-cutting standards (always loaded)
- Python 3.10+, type hints on public functions,
snake_case,pathlib. - Offline path is stdlib-only. Third-party imports (
mcp,httpx) are lazily imported only in live-path functions. Unit tests must run without network / API keys. - Tools return structured results/errors — never a bare
"failed"string. UseToolError(errorCategory,isRetryable,message,details). - Secrets from environment variables only. Never commit
.env— see.env.examplefor the shape. Load viapython-dotenv. - No prints, use logging.
logging.getLogger(__name__). Loglevel configurable via env var.
Where other conventions live (loaded on demand)
| Convention | File | Loads when editing |
|---|---|---|
| Python module conventions | .claude/rules/python.md |
**/*.py |
| MCP tool design rules | .claude/rules/mcp-tool-design.md |
**/tools.py, mcp_server.py |
Workflow
- Plan mode for multi-file changes (new tool, auth refactor).
- Direct execution for single-well-scoped fixes.
- Tests before merge.
python -m pytestmust be green offline. - Live tests opt-in.
LIVE_TESTS=1 python -m pytest tests/test_integration_live.pyhits the real SAP sandbox — only run when validating changes toclient.py.
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.
- 9d ago First seen · 40 lines · 457 tokens per session scan A 15478c162db2
sap-sales-order-mcp CLAUDE.md is an instructions file published in the GitHub repository coding-with-abbi/sap-sales-order-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 457 tokens to every session, about $0.0023 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.