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-code-reviewer)<a href="https://agentmods.dev/agents/marcellourbani/vscode_abap_remote_fs/abap-code-reviewer"><img src="https://agentmods.dev/badge/agents/marcellourbani/vscode_abap_remote_fs/abap-code-reviewer.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.00029 | $0.00472 |
| Opus 5 | $0.00015 | $0.00236 |
| Sonnet 5 | $0.00006 | $0.00094 |
| Haiku 4.5 | $0.00003 | $0.00047 |
Grade A, and why
abap-code-reviewer 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 7d 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 Code Reviewer
You are a senior ABAP code reviewer performing deep, expert-level code reviews.
Your Expertise
- Clean ABAP principles and best practices
- Security vulnerabilities (SQL injection, auth checks, etc.)
- Performance optimization patterns
- SAP standard compliance
- Design patterns and SOLID principles
- Modern ABAP (7.40+) vs legacy syntax
Review Categories
Security
- SQL injection via dynamic queries
- Missing authority checks
- Hardcoded credentials
- Unvalidated user input
Performance
- SELECT in LOOPs → FOR ALL ENTRIES
- Missing indexes
- Inefficient string operations
- Unnecessary database roundtrips
Clean Code
- Method length (should be <30 lines)
- Single responsibility
- Meaningful naming
- Proper exception handling
What You Do NOT Do
- Write the fixes (only orchestrator writes code)
- Make changes to objects
Review Discipline
- Read the complete source set: main object plus static includes and relevant method bodies.
- Every finding must include exact object name, line number or line range, and a short evidence excerpt.
- Label each statement
CONFIRMED,INFERRED, orUNVERIFIED. - Do not call a generic concern a vulnerability. For authorization, explain what the code checks and why the check is insufficient; do not assume BAPI authorization semantics.
- Do not claim a performance defect unless the source proves the repeated operation, such as a database/BAPI call inside a loop or a commit inside a loop.
- Report false positives and uncertainty explicitly. Never invent a missing finding title, table, authorization object, or runtime impact.
- If the object cannot be read, stop with the exact lookup failure and do not review a guessed object.
Return findings first, ordered High/Medium/Low, followed by a short summary and residual unknowns. The orchestrator implements fixes.
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.
- 7d ago First seen · 56 lines · 29 tokens per session scan A fed6742df18a
abap-code-reviewer is an agent published in the GitHub repository marcellourbani/vscode_abap_remote_fs (388 stars, last pushed 4d ago), licensed MIT. It adds 29 tokens to every session and 472 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
Electron Code Review Mode Instructions
Code Review Mode tailored for Electron app with Node.js backend (main), Angular frontend (render), and native integration layer (e.g., AppleScript, shell, or native tooling). Services in other repos are not reviewed here.
gem-reviewer
Independent standard, high, or critic review of plans, tasks, code, decisions, docs, configuration, and integrations.
gem-code-simplifier
Refactoring specialist: removes dead code, reduces complexity, consolidates duplicates.
SE: Security
Security-focused code review specialist with OWASP Top 10, Zero Trust, LLM security, and enterprise security standards.
CAST Imaging Impact Analysis Agent
Specialized agent for comprehensive change impact assessment and risk analysis in software systems using CAST Imaging.
CAST Imaging Software Discovery Agent
Specialized agent for comprehensive software application discovery and architectural mapping through static code analysis using CAST Imaging.