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 j-256/agent-skills --skill dsc-scenariogit clone --depth 1 https://github.com/j-256/agent-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/j-256/agent-skills/dsc-scenario)<a href="https://agentmods.dev/skills/j-256/agent-skills/dsc-scenario"><img src="https://agentmods.dev/badge/skills/j-256/agent-skills/dsc-scenario/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/j-256/agent-skills/dsc-scenario"><img src="https://agentmods.dev/badge/skills/j-256/agent-skills/dsc-scenario.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.00069 | $0.11836 |
| Opus 5 | $0.00034 | $0.05918 |
| Sonnet 5 | $0.00014 | $0.02367 |
| Haiku 4.5 | $0.00007 | $0.01184 |
Grade A, and why
dsc-scenario 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 10d 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.
**`scenario.js` owns all cache access – decide nothing by reading the cache yourself.** Before your first move: do not use shell commands, file-reading tools, or ad hoc parsers (`python3 json.load`, `node -e`) on files u How it starts
The opening of the file, as written. The whole thing — 335 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DSC Scenario Composer
Produce a plan of SCAPI / OCAPI calls – in order, with scope union, ID threading, and a runnable cURL block – to reach a target state. Every claim backed by a public developer.salesforce.com URL.
When to use
The user is trying to reproduce a customer flow on an instance and needs to know:
- Which API calls must happen before the target operation can succeed.
- Which scopes the instance's SLAS/OAuth client must be configured with.
- Where each input to the target (basket IDs, customer IDs, line-item IDs) comes from.
Or the user pastes a cURL command and asks "what else do I need to call to make this work."
Inputs
Ask for missing bits only when the skill can't proceed:
- Target – one of:
- An operationId (
createOrder,shopper-baskets.addItemToBasket). - A natural-language goal ("registered shopper adds a coupon and checks out"). You resolve this to an operationId by matching against
_index.json.title+ Summary prose across cached references; ask the user to confirm before proceeding. - A sample request (cURL, raw HTTP). Pass it to
scenario.jsasrequest(in place oftarget) and it resolves the slug for you – it parses the request and matches it against the referencereferenceUrlnames, the sameparse-request.js+resolve-slug.jspathdsc-endpoint-helpuses. You still supplyreferenceUrl(deriving it from a bare cURL is out of scope); if the request can't be resolved,scenario.jsexits non-zero – ask the user for the reference URL rather than guessing (see "Decline, don't fabricate").
- An operationId (
- Reference URL – the developer.salesforce.com URL of the reference containing the target. Usually inferrable from the request path or operationId's reference prefix.
Resolving an OCAPI target you can't name the reference for. OCAPI reference slugs are not guessable (ocapi-shop-orders, ocapi-data-code-versions – there is no ocapi-shop-api; guessing 404s). When the user gives a METHOD + path ("OCAPI shop, POST /orders", "submit a basket via POST /orders") but not the reference slug, resolve it deterministically with resolve-target.js – pass the area-landing URL (https://developer.salesforce.com/docs/commerce/b2c-commerce/references) plus the method and path; it scans the landing and returns the exact {reference, slug, referenceUrl} to hand to scenario.js:
What ships with it
60 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.
- examples/scenario-add-coupon-checkout.md 12 KB
- examples/scenario-createorder-prereqs.md 10 KB
- examples/scenario-inreference-prereq.md 9.9 KB
- examples/scenario-ocapi-submit-basket.md 12 KB
- package.json 199 B
- README.md 17 KB
- scripts/build-body.js 3.6 KB runs code
- scripts/compose.js 12 KB runs code
- scripts/curated-body.js 3.9 KB runs code
- scripts/curl-block.js 15 KB runs code
- scripts/pkce-snippet.js 151 B runs code
- scripts/resolve-target.js 7.2 KB runs code
- scripts/scenario.js 18 KB runs code
- scripts/walk-types.js 21 KB runs code
- scripts/walk-via-agent.md 4.9 KB
- shared/common/body-values.js 3.6 KB runs code
- shared/common/cite.js 677 B runs code
- shared/common/live-test.js 4.3 KB runs code
- shared/common/parse-request.js 6.7 KB runs code
- shared/common/pkce.js 679 B runs code
- shared/common/resolve-slug.js 6.9 KB runs code
- shared/common/scrape-refresh.js 2.4 KB runs code
- shared/common/shell-vars.js 1.3 KB runs code
- shared/common/spec-traversal.js 2.8 KB runs code
- shared/engine/auth-providers.js 3.8 KB runs code
- shared/engine/curated-facts.js 9.7 KB runs code
- shared/package-lock.json 183 B
- shared/package.json 245 B
- shared/products/commerce-b2c/auth-providers.js 7.5 KB runs code
- shared/products/commerce-b2c/auth-render.js 15 KB runs code
- shared/products/commerce-b2c/curated-facts.js 22 KB runs code
- shared/products/commerce-b2c/dedupe-scopes.js 2.7 KB runs code
- shared/products/commerce-b2c/live-baskets.js 2.0 KB runs code
- shared/products/commerce-b2c/persona.js 1013 B runs code
- shared/products/commerce-b2c/slas-flows.js 4.1 KB runs code
- shared/scrape/aliases.js 2.3 KB runs code
- shared/scrape/cache-access.js 5.2 KB runs code
- shared/scrape/cache-path.js 804 B runs code
- shared/scrape/catalog-keys.js 1.4 KB runs code
- shared/scrape/classify.js 2.2 KB runs code
- shared/scrape/extract-keys.js 2.6 KB runs code
- shared/scrape/fetch-url.js 5.4 KB runs code
- shared/scrape/load-yaml.js 311 B runs code
- shared/scrape/parse-amf.js 11 KB runs code
- shared/scrape/parse-api-catalog.js 1.5 KB runs code
- shared/scrape/parse-catalog.js 1.0 KB runs code
- shared/scrape/parse-oas.js 6.6 KB runs code
- shared/scrape/parse-swagger2.js 5.3 KB runs code
- shared/scrape/reference-versions.js 4.5 KB runs code
- shared/scrape/resolve-cache.js 4.4 KB runs code
- shared/scrape/scrape.js 19 KB runs code
- shared/scrape/write-slugs.js 1.5 KB runs code
- shared/test/fixtures/fake-scrape.js 4.0 KB runs code
- shared/test/fixtures/no-basepath-index.json 580 B
- shared/test/fixtures/ocapi-shop-customers-index.json 521 B
- shared/test/fixtures/shopper-orders-index.json 2.0 KB
- shared/test/run.sh 568 B runs code
- shared/test/test-aliases-live.js 1.5 KB runs code
- shared/test/test-aliases.js 1.4 KB runs code
- shared/test/test-body-values.js 1.8 KB runs code
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.
- 10d ago First seen · 335 lines · 69 tokens per session scan A 4900346303b6
dsc-scenario is a skill published in the GitHub repository j-256/agent-skills (2 stars, last pushed 7d ago), licensed MIT. It adds 69 tokens to every session and 11,836 once invoked, about $0.0003 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
add-matrix
Add Matrix channel integration via Chat SDK. Works with any Matrix homeserver.
django-storages-s3
Use when configuring Django to store static and media files on AWS S3 with django-storages. Invoke when working with the STORAGES setting, S3 buckets, presigned URLs, CloudFront, or boto3-backed file storage in settings.py. Configures the Django 4.2+ STORAGES dict, public/private custom backends, presigned GET/POST…
laravel-specialist
Build and configure Laravel 10+ applications, including creating Eloquent models and relationships, implementing Sanctum authentication, configuring Horizon queues, designing RESTful APIs with API resources, and building reactive interfaces with Livewire. Use when creating Laravel models, setting up queue workers…
sns
AWS SNS notification service for pub/sub messaging. Use when creating topics, managing subscriptions, configuring message filtering, sending notifications, or setting up mobile push.
cognito
AWS Cognito user authentication and authorization service. Use when setting up user pools, configuring identity pools, implementing OAuth flows, managing user attributes, or integrating with social identity providers.
liveview-patterns
Build LiveView: async data (assignasync), PubSub (check connected?), phx-change events, form components/modals/uploads, streams for lists, livepatch. Use when handling interactions, debugging events, or tracking Presence.