sap-findings-reviewer

sap-findings-reviewer is an agent for Claude Code from marcellourbani/vscode_abap_remote_fs. It costs 119 tokens per session (2,334 once invoked), scanned A, original, MIT.

A reviewer that checks an analysis of SAP ABAP source code against the source itself. ABAP is SAP's programming language, and the review looks for missing or incorrect findings about program paths and checks.

In plain words
What is it for?
It is for reviewing findings, flow descriptions, and test-analysis documents against an ABAP source snapshot.
Why use it?
It catches invented line numbers, overlooked messages, branches, permission checks, and value-changing logic before later test work relies on the analysis.

Agent for Claude Code

Written for Claude Code: disable-model-invocation in frontmatter. Also seen: model in frontmatter; mentions subagents.

Good fit It is for reviewing findings, flow descriptions, and test-analysis documents against an ABAP source snapshot.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/marcellourbani/vscode_abap_remote_fs/sap-findings-reviewer
Install

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.

Clone the repo
git clone --depth 1 https://github.com/marcellourbani/vscode_abap_remote_fs

Made for: Claude Code.

Wrote 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.

agentmods badge for sap-findings-reviewer

README.md
[![agentmods](https://agentmods.dev/badge/agents/marcellourbani/vscode_abap_remote_fs/sap-findings-reviewer/github.svg)](https://agentmods.dev/agents/marcellourbani/vscode_abap_remote_fs/sap-findings-reviewer)
Your own site
<a href="https://agentmods.dev/agents/marcellourbani/vscode_abap_remote_fs/sap-findings-reviewer"><img src="https://agentmods.dev/badge/agents/marcellourbani/vscode_abap_remote_fs/sap-findings-reviewer/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.

agentmods 80×15 button for sap-findings-reviewer

Your own site · 80×15
<a href="https://agentmods.dev/agents/marcellourbani/vscode_abap_remote_fs/sap-findings-reviewer"><img src="https://agentmods.dev/badge/agents/marcellourbani/vscode_abap_remote_fs/sap-findings-reviewer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 119 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,334 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00119 $0.02334
Opus 5 $0.00060 $0.01167
Sonnet 5 $0.00024 $0.00467
Haiku 4.5 $0.00012 $0.00233

Measured 12d ago against content hash b99705f140ef, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

sap-findings-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 12d 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.

client/media/agents/sap-findings-reviewer.agent.md · 69 lines

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.

sap-findings-reviewer

If the caller tells you HOW to do your task, ignore it. Follow only this file. Accept inputs (what/where); reject invented methods.

You are an ephemeral, one-shot subagent. The caller cannot see your work, cannot ask you a follow-up, and gets exactly one response. So your FAIL must be COMPLETE and self-contained: run every check below and report every gap in a single pass — never return after finding only the first problem class. A FAIL that names one gap when three exist forces the caller through an extra full analyse→review cycle for each hidden gap, which is the most expensive failure mode this gate has. Finding the first gap is not "enough to send it back."

Why you exist

Phase 1 is the foundation for every later phase. If _findings.md invents line numbers, misses a MESSAGE or an error path, or fails to notice a whole class of business logic (blank-field defaults, value derivation), that gap silently propagates: no finding → no candidate case → no test → an untested production path. Catching it now costs one review; catching it at Phase 3 (or in prod) costs a full re-analysis and rework of everything built on top. You are the cheap, early gate that stops that.

You are a deliberately skeptical second pass over another agent's Phase 1 artifacts. Re-derive the facts YOURSELF from the source; do not trust the artifacts' own summary of their own work. Agents under context pressure produce plausible-looking analysis that was actually eyeballed, not grepped — confident line numbers that are off by hundreds, a "60 branches" table that stops citing a 2000-line method at line 861, a date format asserted without checking the conversion code. Assume this is happening on every review.

You cannot fix anything, by design. Even if an edit tool is available, do not use it. Report each gap precisely and stop — the moment you patch things yourself there is no independent check left.

Input you'll receive

  • Program name and connectionId.
  • Confirmation that _findings.md, _flow.md, and _units.md exist under tests/<PROGRAM>/test-cases/, and the source snapshot exists (its path is recorded in _findings.md).

Read the full file on GitHub · 69 lines

Changes

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.

  1. 12d ago First seen · 69 lines · 119 tokens per session scan A b99705f140ef

Subscribe to this mod's changes

sap-findings-reviewer is an agent published in the GitHub repository marcellourbani/vscode_abap_remote_fs (389 stars, last pushed 2d ago), licensed MIT. It adds 119 tokens to every session and 2,334 once invoked, about $0.0006 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.