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 skills add Ciltress/sap-abap-mcp --skill sap-fiori-url-generatorgit clone --depth 1 https://github.com/Ciltress/sap-abap-mcpWrote 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/skills/ciltress/sap-abap-mcp/sap-fiori-url-generator)<a href="https://agentmods.dev/skills/ciltress/sap-abap-mcp/sap-fiori-url-generator"><img src="https://agentmods.dev/badge/skills/ciltress/sap-abap-mcp/sap-fiori-url-generator/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/skills/ciltress/sap-abap-mcp/sap-fiori-url-generator"><img src="https://agentmods.dev/badge/skills/ciltress/sap-abap-mcp/sap-fiori-url-generator.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.00043 | $0.03050 |
| Opus 5 | $0.00022 | $0.01525 |
| Sonnet 5 | $0.00009 | $0.00610 |
| Haiku 4.5 | $0.00004 | $0.00305 |
Grade A, and why
sap-fiori-url-generator 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.
This is a copy
100% identical to sap-fiori-url-generator — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 444 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SAP Fiori URL Generator Skill
This skill enables you to generate SAP Fiori Launchpad (FLP) URLs based on app names from the AppList.json file.
References
When you need to look up SAP Fiori app information:
App List Database: Read references/AppList.json - contains all SAP Fiori apps with their Semantic Object-Action mappings, App IDs, descriptions, and technical details.
Use this reference to:
- Search for apps by name (partial match, case-insensitive)
- Extract the "Semantic Object - Action" field for URL generation
- Provide app details (ID, description, component) to users
- Suggest similar apps when exact match is not found
Updating AppList.json
The AppList.json data can be obtained from SAP's Fiori Apps Library:
- Go to https://pr.alm.me.sap.com/launchpad#FALApp-display
- Export the app list to Excel
- Convert the Excel file to JSON format
This ensures the app list stays current with the latest SAP Fiori applications.
Overview
When a user provides:
- A base SAP Fiori URL (e.g.,
https://myserver.com:44300) - An app name (e.g., "Create Maintenance Request")
You will:
- Search the AppList.json file for the app
- Extract the "Semantic Object - Action" field
- Construct the complete FLP URL with proper parameters
URL Structure
The complete SAP Fiori Launchpad URL follows this pattern:
{BASE_URL}/sap/bc/ui2/flp?sap-client={CLIENT}&sap-language={LANGUAGE}#{SEMANTIC_OBJECT}-{ACTION}
Required Parameters (MUST be provided by user)
- BASE_URL: The SAP system base URL (e.g.,
https://myserver.com:44300)- MUST be provided by user
- No default value
- sap-client: The SAP client number (e.g.,
100)- MUST be provided by user
- No default value
- Required for all SAP Fiori Launchpad URLs
Optional Parameters
- sap-language: Language code (e.g.,
EN,DE,FR)- Default:
ENif not specified by user - Can be customized per request
- Default:
Auto-Generated Parameters
- SEMANTIC_OBJECT-ACTION: Automatically extracted from the "Semantic Object - Action" field in AppList.json
- No user input required
- Looked up based on app name
What ships with it
8 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 12d ago First seen · 444 lines · 43 tokens per session scan A 8e09de3d15d3
sap-fiori-url-generator is a skill published in the GitHub repository Ciltress/sap-abap-mcp (3 stars, last pushed 20d ago), licensed MIT. It adds 43 tokens to every session and 3,050 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to sap-fiori-url-generator, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…