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 ilia-inovaflow/s4hana-create-record-skills --skill s4hana-create-service-entry-sheetgit clone --depth 1 https://github.com/ilia-inovaflow/s4hana-create-record-skillsWrote 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/ilia-inovaflow/s4hana-create-record-skills/s4hana-create-service-entry-sheet)<a href="https://agentmods.dev/skills/ilia-inovaflow/s4hana-create-record-skills/s4hana-create-service-entry-sheet"><img src="https://agentmods.dev/badge/skills/ilia-inovaflow/s4hana-create-record-skills/s4hana-create-service-entry-sheet/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/ilia-inovaflow/s4hana-create-record-skills/s4hana-create-service-entry-sheet"><img src="https://agentmods.dev/badge/skills/ilia-inovaflow/s4hana-create-record-skills/s4hana-create-service-entry-sheet.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.00253 | $0.01982 |
| Opus 5 | $0.00127 | $0.00991 |
| Sonnet 5 | $0.00051 | $0.00396 |
| Haiku 4.5 | $0.00025 | $0.00198 |
Grade A, and why
s4hana-create-service-entry-sheet scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
3. **If neither**: auto-create `./.env` from the bundled template (curl from `https://raw.githubusercontent.com/ilia-inovaflow/s4hana-create-record-skills/main/.env.example`), append `.env` to `.gitignore` if not already How it starts
The opening of the file, as written. The whole thing — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
s4hana-create-service-entry-sheet
Create Service Entry Sheets on SAP S/4HANA Cloud Public (Lean Services). Verified end-to-end against SAP S/4HANA Cloud Public Edition 2026-05-12 — SES 1, 2, 3 posted via API.
Phase 0 — Setup check (MANDATORY, no exceptions)
Before any API call, before any tool use, do this check. Even if you already know credentials from earlier in the conversation — IGNORE that knowledge and re-check from scratch each invocation.
- Announce: tell the user "Checking for SAP credentials in
<current cwd>..." - Check ONLY these two sources:
- A
.envfile at./.env(in the current working directory — NOT parent dirs, NOT~/.env, NOT any memory file) - Shell-exported env vars:
SAP_HOSTANDSAP_AUTH_MODEboth present
- A
- If neither: auto-create
./.envfrom the bundled template (curl fromhttps://raw.githubusercontent.com/ilia-inovaflow/s4hana-create-record-skills/main/.env.example), append.envto.gitignoreif not already there, tell the user clearly what to fill in (auth mode + host + creds), and wait for them to say "ready" before making any API call. Never overwrite an existing.env. - If credentials are present: report back to the user: "✓ Loaded credentials for
<host>in<auth-mode>mode. Proceeding with [task]."
Never use credentials from conversation memory, from another project's .env, or from any tenant the user previously worked with in a different session. Each project gets its own .env. See shared/setup-check.md for the full rationale and edge cases.
When to trigger
Verbs: create / post / add / generate / seed / enter / confirm Objects: SES, service entry sheet(s), service confirmation(s) Counts: 1 to ~50 records.
Hard rules (never violate)
- Always do a 1-record live POST as a probe before bulk (≥3 records).
- The referenced PO must be a SERVICE PO (cat
0+ SERV material + AAC=K). Uses4hana-create-powith the service-PO recipe first if none exist. - SES references the service line (cat 0), NOT the limit item (cat A) if the PO has one.
- Scripts go in
<cwd>/.s4hana-tmp/create-ses-<YYYYMMDD-HHMM>/. Never commit, never modify.env. - POSTs are sequential with 200ms delay; halt on 3 consecutive failures (but auto-retry once on
MM_PUR_SES/119: PO not releasedafter a 2-second wait — transient backend async).
What ships with it
2 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 · 121 lines · 253 tokens per session scan A 1280cb61fca4
s4hana-create-service-entry-sheet is a skill published in the GitHub repository ilia-inovaflow/s4hana-create-record-skills (2 stars, last pushed 2mo ago), licensed MIT. It adds 253 tokens to every session and 1,982 once invoked, about $0.0013 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
pricing-refresh
Refresh or verify the hermit cost rate table against Anthropic's live pricing. Use when the operator says "refresh pricing", "verify pricing", "is the rate table current", "new model pricing", or asks whether scripts/lib/pricing.ts matches current Codex rates. Maintainer-only; never autonomous, never a routine, never…
monitor
Autonomous monitoring loop. Checks open trades against SL/TP levels, closes trades that hit targets, evaluates expired predictions, and generates periodic summaries. Run via cron for full autonomy. Usage: /monitor.
validate-predictions
Review and validate pending predictions against current market data. Usage: /validate-predictions.
0xarchive
Query historical and real-time crypto market data from 0xArchive across two top-level venue APIs: Hyperliquid and Lighter.xyz. HIP-3 builder perps live under the Hyperliquid namespace at /v1/hyperliquid/hip3. HIP-4 outcome markets (binary prediction markets like 'Will BTC be >= X by date Y?') live at…
analyze
Run a comprehensive multi-agent crypto analysis with phased execution. Usage: /analyze BTC or /analyze ETH SOL.
close-trade
Close an open trade and run post-mortem analysis. Usage: /close-trade trade001 or /close-trade trade001 at 98500.