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 rules/marianfoo/abap-mcp-server/40-deploygit clone --depth 1 https://github.com/marianfoo/abap-mcp-serverWhat 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.00687 | $0.00687 |
| Opus 5 | $0.00344 | $0.00344 |
| Sonnet 5 | $0.00137 | $0.00137 |
| Haiku 4.5 | $0.00069 | $0.00069 |
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 2d 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.
This is a copy
92% identical to 40-deploy — 7 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 69 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)
- abap-mcp-http: HTTP status server (127.0.0.1:3001)
- abap-mcp-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.
- 2d ago First seen · 69 lines · 687 tokens per session scan A 2797dc585cc5
40-deploy is a cursor rule published in the GitHub repository marianfoo/abap-mcp-server (88 stars, last pushed 14d ago), licensed Apache-2.0. It adds 687 tokens to every session, about $0.0034 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to 40-deploy, differing in 7 lines, and is treated as a copy.
Other cursor rules, from other repositories
180-terraform
Secure, efficient, modular Terraform with strong validation, docs, and CI hygiene.
devops-engineer
Infrastructure, Deployment, and CI/CD specialist. Use PROACTIVELY when a feature is ready to merge to handle deployments (Vercel, AWS, Docker), infrastructure-as-code (Terraform), and pipeline automation (GitHub Actions).
deployment-engineer
Designs and implements robust CI/CD pipelines, container orchestration, and cloud infrastructure automation. Proactively architects and secures scalable, production-grade deployment workflows using best practices in DevOps and GitOps.
viberaven-deploy
Apply before changing Vercel config or deploy CI workflows.
deployment
Live PS3D local, GitHub CI, Vercel, Supabase, and remote MCP deployment context.
netlify-deploy
Create and manage Netlify deploys — Git continuous deployment, CLI manual/anonymous deploys, Deploy to Netlify buttons, drag-and-drop, and per-context netlify.toml build settings. Use when linking a repo, deploying from the CLI, setting up Deploy Previews or branch deploys, configuring deploy contexts, adding skew…