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 OrcaQubits/agentic-commerce-skills-plugins --skill sf-b2c-jobsgit clone --depth 1 https://github.com/OrcaQubits/agentic-commerce-skills-pluginsWrote 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/orcaqubits/agentic-commerce-skills-plugins/sf-b2c-jobs)<a href="https://agentmods.dev/skills/orcaqubits/agentic-commerce-skills-plugins/sf-b2c-jobs"><img src="https://agentmods.dev/badge/skills/orcaqubits/agentic-commerce-skills-plugins/sf-b2c-jobs/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/orcaqubits/agentic-commerce-skills-plugins/sf-b2c-jobs"><img src="https://agentmods.dev/badge/skills/orcaqubits/agentic-commerce-skills-plugins/sf-b2c-jobs.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.00063 | $0.01318 |
| Opus 5 | $0.00032 | $0.00659 |
| Sonnet 5 | $0.00013 | $0.00264 |
| Haiku 4.5 | $0.00006 | $0.00132 |
Grade A, and why
sf-b2c-jobs 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 2d 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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Salesforce B2C Commerce Jobs
Before Writing Code
ALWAYS fetch live documentation BEFORE writing any job code:
- Web-search: "Salesforce B2C Commerce job framework documentation 2026"
- Web-search: "SFCC custom job step implementation guide 2026"
- WebFetch official Salesforce docs for:
- Job framework reference and execution context
- System job types and parameters
- Cron expression syntax for B2C Commerce
- sfcc-ci job command reference
Why: Job APIs, execution contexts, and best practices evolve with each B2C Commerce release. Always verify current patterns.
Conceptual Architecture
Job Framework Overview
The job framework provides scheduled background processing in B2C Commerce:
- Job execution engine: Server-side background task runner
- Job steps: Individual units of work within a job (one job can have multiple steps)
- Job scheduling: Cron-based recurring or manual/API triggering
- Job monitoring: Business Manager dashboard (Administration > Operations > Jobs)
Job Types
| Type | Description | Approach |
|---|---|---|
| System jobs | Built-in import/export/reindex/cleanup | Configured in Business Manager |
| Script module steps | Custom JavaScript (modern approach) | exports.execute = function(jobStepExecution) {} |
| Pipeline steps | Legacy pipeline-based steps | Maintenance mode; avoid for new work |
| Chunk steps | Large dataset processing | Read-process-write pattern with commit intervals |
Step Types
| Step Type | Use Case | Key Characteristic |
|---|---|---|
| Script | General custom logic | Single execute() entry point; return Status |
| Pipeline | Legacy flows | Deprecated for new development |
| Chunk | Large dataset processing | Framework manages read/process/write lifecycle with batching |
Cron Expression Examples
0 0 2 * * ? Every day at 2:00 AM
0 */15 * * * ? Every 15 minutes
0 0 0 1 * ? First day of month at midnight
0 0 18 ? * MON-FRI Weekdays at 6:00 PM
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.
- 2d ago First seen · 137 lines · 63 tokens per session scan A e461ef7179e3
sf-b2c-jobs is a skill published in the GitHub repository OrcaQubits/agentic-commerce-skills-plugins (39 stars, last pushed 2d ago), licensed MIT. It adds 63 tokens to every session and 1,318 once invoked, about $0.0003 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-09-15.
Other skills, from other repositories
mppx
TypeScript SDK for the Payment HTTP Authentication Scheme. Handles 402 Payment Required flows with Tempo, Stripe, and other payment methods. Use when integrating payments or mppx into a client or server application.
managing-archestra-releases
Runs rolling beta releases, stable patches, and complete stable-line cutovers. Use when backporting fixes, cutting or retiring release branches, configuring release protections, testing artifacts, recovering failed runs, or approving releases.
archestra-dev-testing
Use when deciding whether a change needs a test and at which level — unit, backend route-level integration, MSW-backed frontend integration, or e2e — or when reviewing tests for the "fluff test" anti-pattern. Start here before archestra-dev-backend-tests or archestra-dev-e2e.
migrate-to-archestra
Migrate an existing agentic PoC/pilot (Claude Code project files, MCP configs, hooks, local tools, openclaw config, or similar hand-rolled setup artifacts) into an Archestra instance. Use when the user wants to move, port, or convert an existing agentic setup into an Archestra pilot.
archestra-dev-backend-tests
Use when writing or modifying Archestra backend unit tests (platform/backend/src//.test.ts) — mocking modules, stubbing globals, database fixtures, vitest projects/isolation, or test performance.
archestra-dev-frontend
Use when modifying Archestra frontend Next.js/React code, UI components, forms, TanStack Query hooks, generated API client usage, frontend copy, or documentation links.