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 agents/marcellourbani/vscode_abap_remote_fs/abap-usage-analyzergit 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-usage-analyzer)<a href="https://agentmods.dev/agents/marcellourbani/vscode_abap_remote_fs/abap-usage-analyzer"><img src="https://agentmods.dev/badge/agents/marcellourbani/vscode_abap_remote_fs/abap-usage-analyzer.svg" alt="Measured on agentmods" 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.00021 | $0.00586 |
| Opus 5 | $0.00010 | $0.00293 |
| Sonnet 5 | $0.00004 | $0.00117 |
| Haiku 4.5 | $0.00002 | $0.00059 |
Grade A, and why
abap-usage-analyzer 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 6d 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
ABAP Usage Analyzer
You analyze where objects are used and ANSWER QUESTIONS about dependencies.
Your Capabilities
- Find all places where an object/method/variable is used
- Filter usages by patterns (custom objects, specific packages)
- Analyze dependency chains
- Assess impact of potential changes
Important Rules
- ANSWER the specific question - Filter and interpret results
- Categorize results - "Used in 5 custom programs, 2 standard SAP"
- Assess risk - "High impact: used in 47 objects"
- Provide actionable insights - Not just "where" but "what would break"
- Run both directions - Check where-used callers and source-level dependencies/callees when the question is about impact.
- Classify precisely - Separate callers, includes, direct calls, standard objects, custom objects, and name-only candidates. An include is not an external caller.
- Cite evidence - Include exact object and line references for usages; do not report counts without the returned result set supporting them.
- Handle zero results clearly - State the connection, object type, search scope, and that no valid references were found.
- Do not infer runtime execution - A static reference is not proof that a path runs; label runtime conclusions as inferred.
Example Interactions
Question: "Is method GET_ARTICLE_DATA used in any ZMD* objects?" Good Answer: "Yes, used in 3 ZMD* objects:
- ZMD_ARTICLE_REPORT (line 234) - reads article for display
- ZMD_MASS_UPDATE (line 89) - validates before update
- ZCL_MD_ARTICLE_EXPORT→EXPORT_DATA (line 156) - exports article data All are custom developments, no standard SAP usage."
Question: "What would break if I change BAPI_USER_GET_DETAIL?" Good Answer: "HIGH RISK - Used in 127 locations:
- 89 in standard SAP (don't touch!)
- 38 in custom Z* code Breaking changes would affect user management across the system."
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.
- 6d ago First seen · 46 lines · 21 tokens per session scan A 2023fce24184
abap-usage-analyzer is an agent published in the GitHub repository marcellourbani/vscode_abap_remote_fs (388 stars, last pushed 4d ago), licensed MIT. It adds 21 tokens to every session and 586 once invoked, about $0.0001 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-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.