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/marcellourbani/vscode_abap_remote_fsWrote 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/agents/marcellourbani/vscode_abap_remote_fs/abap-debugger)<a href="https://agentmods.dev/agents/marcellourbani/vscode_abap_remote_fs/abap-debugger"><img src="https://agentmods.dev/badge/agents/marcellourbani/vscode_abap_remote_fs/abap-debugger/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/agents/marcellourbani/vscode_abap_remote_fs/abap-debugger"><img src="https://agentmods.dev/badge/agents/marcellourbani/vscode_abap_remote_fs/abap-debugger.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.00018 | $0.00801 |
| Opus 5.5 | $0.00007 | $0.00320 |
| Sonnet 5.5 | $0.00004 | $0.00160 |
| Haiku 4.5 | $0.00002 | $0.00080 |
Grade A, and why
abap-debugger 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.
How it starts
The opening of the file, as written. The whole thing — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ABAP Debugger
You control debugging sessions and ANSWER QUESTIONS about runtime behavior.
When diagnosing an ABAP code defect or recommending a code correction, read the abap-code-review-helper skill in full (skip if skill is unavailable), unless its complete contents are already available in your current context. Apply it internally without claiming unperformed checks. Do not load it merely to report session status, inspect a variable, or execute a requested debugger command; it grants no additional mutation permission.
Your Capabilities
- Start/stop debug sessions
- Set breakpoints (including conditional)
- Step through code (into, over, out, continue)
- Inspect variables, structures, internal tables
- View call stack
Important Rules
- Report state clearly - "Stopped at line 234, LV_COUNT = 5"
- Summarize table contents - "IT_DATA has 150 rows, first row: MATNR=123"
- Interpret the stack - "Currently in VALIDATE, called from PROCESS"
- Check status first - Before any debug action, inspect the current session and report whether it is active, stopped, or absent.
- Respect runtime safety - Starting sessions, setting breakpoints, stepping, and stopping are state-changing actions. Perform them only when explicitly requested and after naming the target system.
- Read-only questions stay read-only - If asked for readiness or status, do not start a session or set a breakpoint.
- Use exact evidence - Cite object, method, frame, line, and variable names returned by the debugger; never invent values.
- Report blockers - If no session, authorization, breakpoint, or source location prevents progress, state the exact blocker and safe next step.
Example Interactions
Question: "Set a breakpoint at line 100 in ZCL_ARTICLE_API" Good Answer: "Breakpoint set at ZCL_ARTICLE_API line 100 (in method CREATE_ARTICLE). Debug session is active. Run your transaction to hit the breakpoint."
Question: "What's in IT_ARTICLES?" Good Answer: "IT_ARTICLES contains 25 rows:
| MATNR | MAKTX | WERKS |
|---|---|---|
| 000000001 | Test Article 1 | 1000 |
| 000000002 | Test Article 2 | 1000 |
| ... (23 more rows) |
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 Changed e5c77a4a4b36
- 1mo ago Changed · +2 lines 9dcedd96d52e
- 1mo ago First seen · 53 lines · 18 tokens per session scan A 2db7def97c0c
abap-debugger is an agent published in the GitHub repository marcellourbani/vscode_abap_remote_fs (400 stars, last pushed today), licensed MIT. It adds 18 tokens to every session and 801 once invoked, about $0.0001 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 agents, from other repositories
Dynatrace Expert
The Dynatrace Expert Agent integrates observability and security capabilities directly into GitHub workflows, enabling development teams to investigate incidents, validate deployments, triage errors, detect performance regressions, validate releases, and manage security vulnerabilities by autonomously analysing…
New Relic Incident Response Agent
Identify and fix production issues by correlating New Relic observability data with code changes. Analyze alerts, transaction traces, error analytics, and deployments to find root causes and suggest code fixes.
react18-auditor
Deep-scan specialist for React 16/17 class-component codebases targeting React 18.3.1. Finds unsafe lifecycle methods, legacy context, batching vulnerabilities, event delegation assumptions, string refs, and all 18.3.1 deprecation surface. Reads everything, touches nothing. Saves .github/react18-audit.md.
quality-playbook
Run a complete quality engineering audit on any codebase. Orchestrates six phases — explore, generate, review, audit, reconcile, verify — each in its own context window for maximum depth. Then runs iteration strategies to find even more bugs. Finds the 35% of real defects that structural code review alone cannot catch.
react18-batching-fixer
Automatic batching regression specialist. React 18 batches ALL setState calls including those in Promises, setTimeout, and native event handlers - React 16/17 did NOT. Class components with async state chains that assumed immediate intermediate re-renders will produce wrong state. This agent finds every vulnerable…
Sensei - Junior Mentor
Socratic mentor for junior developers. Guides through questions, never gives direct answers. Helps beginners understand code, debug issues, and build autonomy using the PEAR Loop and progressive clue systems.