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.
git clone --depth 1 https://github.com/marianfoo/mcp-sap-docsWrote 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/rules/marianfoo/mcp-sap-docs/40-deploy)<a href="https://agentmods.dev/rules/marianfoo/mcp-sap-docs/40-deploy"><img src="https://agentmods.dev/badge/rules/marianfoo/mcp-sap-docs/40-deploy/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/rules/marianfoo/mcp-sap-docs/40-deploy"><img src="https://agentmods.dev/badge/rules/marianfoo/mcp-sap-docs/40-deploy.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.00713 | $0.00713 |
| Opus 5.5 | $0.00285 | $0.00285 |
| Sonnet 5.5 | $0.00143 | $0.00143 |
| Haiku 4.5 | $0.00071 | $0.00071 |
Grade A, and why
40-deploy 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- 40-deploy — 92% identical, 7 lines differ
How it starts
The opening of the file, as written. The whole thing — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deploy & Ops (Rule)
For PM2 processes, GitHub Actions, health checks, and production operations.
Deployment Pipeline
- GitHub Action: "Deploy MCP stack" workflow
- Trigger: Push to main branch or manual dispatch via workflow_dispatch
- Process: SSH → git pull → enhanced
setup.sh→ PM2 restart - Health Checks: Automated validation of all endpoints (proxy, http, streamable)
Enhanced Setup Script (setup.sh)
- Shallow Submodules: Single-branch, depth-1 clones with blob filtering
- Partial Clone: Uses
--filter=blob:nonefor minimal bandwidth - Branch Fallback: Tries specified branch, falls back to master
- Repository Compaction: Aggressive GC and reflog cleanup
- Skip Nested:
SKIP_NESTED_SUBMODULES=1for deployment optimization
PM2 Configuration (ecosystem.config.cjs)
- mcp-sap-proxy: MCP proxy server (127.0.0.1:18080)
- mcp-sap-http: HTTP status server (127.0.0.1:3001)
- mcp-sap-streamable: Streamable HTTP MCP (127.0.0.1:3122)
Environment Configuration (BM25-Only)
env: {
NODE_ENV: "production",
LOG_LEVEL: "INFO",
LOG_FORMAT: "json",
RETURN_K: "25" // Centralized result limit
}
Health Endpoints
- HTTP Server:
/status,/healthz,/readyz - Streamable Server:
/health - Proxy Server:
/status(via mcp-proxy)
Build Process
- TypeScript:
npm run build:tsc→dist/src/ - Index Build:
npm run build:index→dist/data/index.json - FTS Build:
npm run build:fts→dist/data/docs.sqlite - Full Build:
npm run build→ Complete pipeline
Monitoring & Logging
- Structured Logging: JSON format in production
- Performance Metrics: Search timing and result counts
- Error Tracking: Graceful fallbacks with error logging
- Resource Usage: PM2 process monitoring
Build Process
- Index Build:
npm run build:index→dist/data/index.json - FTS Build:
npm run build:fts→dist/data/docs.sqlite - TypeScript:
npm run build:tsc→dist/src/ - Full Build:
npm run build→ Complete pipeline
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 First seen · 70 lines · 713 tokens per session scan A 4e3912b5b004
40-deploy is a cursor rule published in the GitHub repository marianfoo/mcp-sap-docs (243 stars, last pushed today), licensed Apache-2.0. It adds 713 tokens to every session, about $0.0029 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-30.
Other cursor rules, from other repositories
no-mvn-compile
Do not run mvn compile; rely on IDE lint errors.
releasing-operator
when the user is releasing a new version of the Kubernetes operator.
agents-shipgate
Run Agents Shipgate as the deterministic merge gate for AI-generated agent capability changes.
ci-cd-workflows
This rule provides guidance on the CI/CD pipeline, GitHub Actions workflows (defined in .github/workflows/), custom actions (in .github/actions/), versioning strategies, and release processes. Use this rule if the query involves CI/CD, build/test issues, release procedures, versioning questions, or if it references…
dev-workflow
Monorepo developer workflow standards - mise tasks, git hooks, CI/CD, release automation.
sciclaw-papercuts
Papercuts from Sol/ImageMagick/release cycles — release, brew, CI, and workspace hygiene for sciClaw agents.