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-po-confirmationgit 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-po-confirmation)<a href="https://agentmods.dev/skills/ilia-inovaflow/s4hana-create-record-skills/s4hana-create-po-confirmation"><img src="https://agentmods.dev/badge/skills/ilia-inovaflow/s4hana-create-record-skills/s4hana-create-po-confirmation/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-po-confirmation"><img src="https://agentmods.dev/badge/skills/ilia-inovaflow/s4hana-create-record-skills/s4hana-create-po-confirmation.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.00193 | $0.02524 |
| Opus 5.5 | $0.00077 | $0.01010 |
| Sonnet 5.5 | $0.00039 | $0.00505 |
| Haiku 4.5 | $0.00019 | $0.00252 |
Grade A, and why
s4hana-create-po-confirmation 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 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.
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 — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
s4hana-create-po-confirmation
Create supplier order confirmations on SAP S/4HANA Cloud Public via the SOAP A2X service. Verified end-to-end against SAP S/4HANA Cloud Public Edition 2026-05-12 — confirmation visible in Fiori "Supplier Confirmation" tab on PO 4500000020/10 (Sequential 1, Category AB, qty 50 PC, delivery 05/25/2026).
When to trigger
Verbs: create / post / add / generate / seed / confirm / acknowledge / simulate Objects: PO confirmation(s), supplier confirmation(s), order acknowledgement(s), vendor 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), and verify in Fiori that the confirmation actually appeared (the service is one-way async; HTTP 202 means accepted, not committed).
- PO line must have
SupplierConfirmationControlKeyset before posting confirmations. If empty (default on this tenant), PATCH it via OData first. - WS-Addressing headers are required — without
wsa:Action,wsa:To,wsa:MessageID,wsa:ReplyTo, the service returns 500 "Web service processing error" with no diagnostic detail. - Scripts go in
mcp-server/src/sap/.tmp/<user>-<YYYYMMDD-HHMM>/create-po-confirmations/. Never commit, never modify.env. - POSTs are sequential with 200ms delay; halt on 3 consecutive non-202 responses.
Endpoint
- Service path:
/sap/bc/srt/scs_ext/sap/supplierconfirmationrequest_i1 - SOAP action:
http://sap.com/xi/Procurement/SupplierConfirmationRequest_In/SupplierConfirmationRequest_InRequest - Communication scenario:
SAP_COM_0827— "Supplier Confirmation Process Integration" - Style: SOAP 1.1, document/literal, WS-Addressing required, response: HTTP 202 (one-way async)
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.
What ships with it
3 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.
- 1mo ago First seen · 168 lines · 193 tokens per session scan A c4ebb9c9d67b
s4hana-create-po-confirmation is a skill published in the GitHub repository ilia-inovaflow/s4hana-create-record-skills (2 stars, last pushed 4mo ago), licensed MIT. It adds 193 tokens to every session and 2,524 once invoked, about $0.0008 per session on Opus 5.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
yolo-brief
Use to record a new feature in a YOLO repo, or to cancel one. Writes workspace/features/ /brief.md with a goal and checkable success criteria, taken from an approved design spec when one exists. Triggers on "track this as a feature", "write a brief for X", "track it from that spec", "yolo brief", "cancel the X…
yolo-next
Use when the user asks what to work on next, what to pick up, or what to prioritize in a YOLO repo. Ranks the backlog from derived status, dependencies, stalled work, open issues and code TODOs, and recommends the top 3 with reasons. Read-only. Triggers on "what next", "what should I work on", "what should I pick up"…
yolo-status
Use when the user asks where things stand, what's in progress, what's landed, or "where was I" in a YOLO repo. Derives every feature's status from git and the briefs; nothing is read from a stored status field.
yolo-verify
Use to check a feature branch against its brief's successcriteria and record the result. Writes verification.md and, on a full pass, commits it with the YOLO-Verified trailer. Triggers on "verify this feature", "does it meet the criteria", "yolo verify".
yolo-init
Use when setting up YOLO in a repo for the first time, or repairing the setup. Creates workspace/features/ and workspace/config.yaml. Triggers on "set up YOLO here", "init yolo", "yolo init".
stripe-best-practices
Guide Stripe integration decisions — API choice, Connect, billing, Treasury, key/webhook security.