SC4SAP Eco
One-off entry point for eco cost mode — same deliverable as standard, cheaper models and effort. Rules: ../../common/cost-mode.md. This skill's effort: low frontmatter lowers the main-thread effort while it is active — that is lever B of the cost mode. The effect ends at the next user turn, so eco runs re-enter here with --attach.
<Response_Prefix>
Every response triggered by this skill MUST begin with [Model: <main-model> · Dispatched: <sub-summary> · Mode: eco] per ../../common/model-routing-rule.md § Response Prefix Convention — except in --attach mode, which emits nothing.
</Response_Prefix>
--attach
Called by a skill already running in eco (first action of the run when eco came from preferences / --eco, and first action of every continuation turn). Do nothing else: no output, no file reads. Return control to the calling skill and continue its work in this same turn.
<skill> <args> (user-facing)
- If the arguments contain
--standard→ say that eco and standard conflict, and stop. Parse the first token as the target skill. Acceptcreate-program,/sc4sap:create-program,sc4sap:create-program. Normalize to the bare name. - If the target has no eco variant (
setup,sap-option,sap-doctor,mcp-setup,trust-session,eco, and every skill listed as "No eco variant" incommon/cost-mode.md§ lever C) → say so in one line and stop. Do not run it. - If the target is unknown or missing → list the skills that have an eco recipe (
common/cost-mode.md§ lever C) and stop. - Invoke
Skill("sc4sap:<target>", "<args> --eco --via-eco"). The target resolves--ecofirst and skips its first--attachbecause of--via-eco(cost-mode § Resolution), so preferences are not read for the mode and not changed. - The target skill owns the run from here: its own prefix (with
· Mode: eco), banners, questions, and report.


