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 agentmods add skills/vigneshbarani24/sap-superpowers/estimationnpx skills add vigneshbarani24/sap-superpowers --skill estimationgit clone --depth 1 https://github.com/vigneshbarani24/sap-superpowersWrote 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/vigneshbarani24/sap-superpowers/estimation)<a href="https://agentmods.dev/skills/vigneshbarani24/sap-superpowers/estimation"><img src="https://agentmods.dev/badge/skills/vigneshbarani24/sap-superpowers/estimation.svg" alt="Measured on agentmods" 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.00046 | $0.03609 |
| Opus 5 | $0.00023 | $0.01804 |
| Sonnet 5 | $0.00009 | $0.00722 |
| Haiku 4.5 | $0.00005 | $0.00361 |
Grade A, and why
estimation 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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 283 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SAP Effort Estimation
This skill enforces decomposition-based, range-driven estimation for SAP work so that no single number, unsupported assumption, or unrisked commitment ever leaves this engagement.
Iron Laws
- NEVER GIVE A SINGLE-POINT ESTIMATE. Every estimate is a range: optimistic / realistic / pessimistic. A single number is a lie dressed as precision. The PM puts it in the plan. The client holds you to it. The project bleeds.
- NEVER ESTIMATE WITHOUT DECOMPOSITION. "About 30 days for FI" is not an estimate. A table of work packages with individual three-point assessments is an estimate. If it is not decomposed, it is a guess.
- NEVER ESTIMATE WITHOUT STATING ASSUMPTIONS. Every assumption that underpins an estimate must be written down before the numbers are produced. Hidden assumptions become blown budgets. If you have not listed them, you have not controlled them.
- ALWAYS INCLUDE A RISK BUFFER. 10% minimum, 30% for high-uncertainty work. Saying "no contingency needed" means you have not identified the unknowns. There are always unknowns in SAP projects.
- TESTING IS NEVER INCLUDED IN DEVELOPMENT. Testing effort is 30–40% of SAP delivery. Embedding it in development effort hides it until it is too late to resurface. It must be its own line.
Rationalization Table
| Agent Will Try To... | Why It Seems Reasonable | Why It Fails | Counter |
|---|---|---|---|
| Give a single number | "The user asked 'how long will this take?' — they want one answer" | Single numbers become commitments. The PM puts them in the Gantt chart. The client uses them in contracts. Ranges force an honest conversation about uncertainty. | Iron Law 1: Always three-point. If the user insists on one number, give the realistic estimate with explicit written caveats. |
| Skip work package decomposition | "The scope is clear enough for a top-down estimate" | Top-down estimates miss hidden complexity: legacy data cleanup, authorization design, integration mapping, transport management. Each of these can double a phase estimate. | Iron Law 2: WBS first. Every process area gets its own row before any numbers are written. |
| Skip complexity factors | "The work is straightforward" | 'Straightforward' SAP work has a 40-60% overrun rate when complexity factors are not applied. Customization depth, team experience, and integration count multiply base effort materially. | Checklist Step 3: Apply all five complexity factors to every work package. If all factors score 1.0×, provide written justification. |
| Merge testing into development | "Testing is implicit in the development estimate" | Testing is 30–40% of SAP delivery. When it is hidden, it gets cut under time pressure. Then it happens anyway — in production. | Iron Law 5: Testing is a mandatory separate line item in every work package. |
| Omit training and cutover effort | "We're estimating development, not the full project" | Training, cutover prep, and hypercare are 20–30% of total project cost. Omitting them produces estimates that look lean until Realize when the full picture emerges and the budget is already committed. | Checklist Step 2: Six effort categories are mandatory: Build, Test, Data Migration, Integration, Training, Project Management. |
| Skip risk identification | "We can handle risks as they come" | Unidentified risks become 'surprises' that justify emergency change requests. Clients lose trust. Budgets collapse. Identify them now and quantify their day-impact. | Checklist Step 5: Minimum 3 estimation risks with quantified day-impact and a named contingency allocation. |
| Apply calendar days = working days | "The user asked for a timeline, so I'll use working days" | SAP consultants attend workshops, prepare for calls, review designs, handle environment issues, and wait on approvals. Utilization on a project is typically 60–70% of calendar days. | Template: calendar-day conversion uses a 0.65 utilization factor by default. State the factor explicitly. |
| Anchor to a previous project | "We estimated similar work at 40 days on the last project" | Different client, different legacy landscape, different team, different SAP release. Analogical estimates without documented similarity criteria are guesses with false authority. | Red Flag trigger: "Based on similar projects..." → State the similarity criteria explicitly or do not use the analogy. |
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.
- 6d ago First seen · 283 lines · 46 tokens per session scan A bc61496a92b5
estimation is a skill published in the GitHub repository vigneshbarani24/sap-superpowers (9 stars, last pushed 14d ago), licensed MIT. It adds 46 tokens to every session and 3,609 once invoked, about $0.0002 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-31.
Other skills, from other repositories
sap-expert
Expert in SAP ERP systems, ABAP programming, SAP HANA, S/4HANA, Fiori applications, and SAP integration patterns including OData, RFC, and IDoc. Use when the user mentions ERP, enterprise, business apps, ABAP, HANA, or S/4HANA, or when the task involves SAP Ecosystem, ABAP Development, Integration Technologies, or…
migrate-from-openclaw
Migrate from OpenClaw to NanoClaw v2. Detects an existing OpenClaw installation, extracts identity, channel credentials, scheduled tasks, and other config, then guides interactive migration. Triggers on "migrate from openclaw", "openclaw migration", "import from openclaw".
add-dial-tool
Give chosen NanoClaw agents a real phone number as a container tool — the dial CLI baked into the agent image plus OneCLI credential injection for api.getdial.ai, scoped per agent, so the agents you pick can send SMS, place AI voice calls, and receive verification codes from inside the sandbox. Independent of the Dial…
add-signal
Add Signal channel integration via signal-cli device-link. Native adapter — no Chat SDK bridge.
slack-agent-flow
Let an existing Slack agent create new agents that arrive as their own Slack bots — provisioned app, operator DM, and a shared three-way room, hot-started without a host restart.
add-deltachat
Add DeltaChat channel integration via @deltachat/stdio-rpc-server. Native adapter — no Chat SDK bridge. Email-based messaging with end-to-end encryption.