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/fr0ster/mcp-abap-adtWrote 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/fr0ster/mcp-abap-adt/main)<a href="https://agentmods.dev/rules/fr0ster/mcp-abap-adt/main"><img src="https://agentmods.dev/badge/rules/fr0ster/mcp-abap-adt/main/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/fr0ster/mcp-abap-adt/main"><img src="https://agentmods.dev/badge/rules/fr0ster/mcp-abap-adt/main.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.00355 | $0.00355 |
| Opus 5.5 | $0.00142 | $0.00142 |
| Sonnet 5.5 | $0.00071 | $0.00071 |
| Haiku 4.5 | $0.00036 | $0.00036 |
Grade A, and why
main 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:
- main — 100% identical, 0 lines differ
What it actually says
mcp-abap-adt Rules
Language Requirements
All repository artifacts authored by the assistant (source code, documentation, comments, commit messages, etc.) must be written in English.
Direct communication with the user must follow the language used by the user in the current conversation.
Project Context
- Name: mcp-abap-adt – MCP server for SAP ABAP ADT (ABAP Development Tools).
- Purpose: Provides a Model Context Protocol (MCP) server for interacting with SAP ABAP systems.
- Key Modules:
src/handlers/,src/lib/connection/,src/lib/,tests/
Code Standards
- Source code: English only
- Comments: English only, explain "why" not "what"
- Variable/function/class names: English only
- Error messages: English only
- Log messages: English only
Fundamental Cline Rules
- No assumptions about object existence unless explicitly present in retrieved code or listed by GetIncludesList
- No reliance on unspecified standards (SAP, ABAP, documentation standards) unless explicitly specified
- Context over abstract standards - never ignore user's context in favor of abstract standards
- Clarification requirement - always ask for clarification if language, format, structure are not specified
- Default language: English (unless otherwise specified)
Architecture Notes
- Connection types: CloudAbapConnection, OnPremAbapConnection, BaseAbapConnection
- Handlers use centralized caching via
objectsListCache - Handlers return structured results (no file writes from handler logic)
- Testing: YAML-based configuration in
tests/test-config.yaml
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 · 37 lines · 355 tokens per session scan A 56a50c540a41
main is a cursor rule published in the GitHub repository fr0ster/mcp-abap-adt (101 stars, last pushed today), licensed Apache-2.0. It adds 355 tokens to every session, about $0.0014 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
abap-dev
Rules for ABAP development using SAP ADT MCP tools.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.