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/sapdev-ai/sap-devWrote 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/sapdev-ai/sap-dev/abap-developer)<a href="https://agentmods.dev/agents/sapdev-ai/sap-dev/abap-developer"><img src="https://agentmods.dev/badge/agents/sapdev-ai/sap-dev/abap-developer/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/sapdev-ai/sap-dev/abap-developer"><img src="https://agentmods.dev/badge/agents/sapdev-ai/sap-dev/abap-developer.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.00258 | $0.16246 |
| Opus 5.5 | $0.00103 | $0.06498 |
| Sonnet 5.5 | $0.00052 | $0.03249 |
| Haiku 4.5 | $0.00026 | $0.01625 |
Grade A, and why
abap-developer 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.
The source is not reproduced here
Licensed GPL-3.0
The repository is licensed GPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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 · 1,053 lines · 258 tokens per session scan A a1fd5949e645
abap-developer is an agent published in the GitHub repository sapdev-ai/sap-dev (8 stars, last pushed 1mo ago), licensed GPL-3.0. It adds 258 tokens to every session and 16,246 once invoked, about $0.0010 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-31.
Other agents, from other repositories
canvas-create-screens
Groups approved functional intent into task-oriented screens, in-screen states and navigation without choosing Canvas controls.
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
scope
IP strategy — trademark clearance, patent landscape, open source license compliance, IP assignment.
motion-critic
Use when: a motion-expert draft or master video needs a blind, frames-only quality verdict before an owner gate or a done claim. Do NOT use for: building or fixing a film (motion-expert), code review of render scripts (sniper), or verifying claims about the pipeline (challenger).
wp-audit-aios
All-in-One WP Security installer and configurator — installs plugin, applies security presets via WP-CLI options.
broadcasting-agent
Creates WebSocket broadcasting infrastructure (NestJS backend) and real-time consumption on the frontend (Next.js or React). Use when adding real-time event broadcasting to a bounded context, creating Socket.IO gateways, or implementing frontend event listeners. Dispatched after infrastructure layer is complete.