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/salesforcecommercecloud/b2c-developer-tooling/sfnext-routingnpx skills add SalesforceCommerceCloud/b2c-developer-tooling --skill sfnext-routinggit clone --depth 1 https://github.com/SalesforceCommerceCloud/b2c-developer-toolingWrote 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/salesforcecommercecloud/b2c-developer-tooling/sfnext-routing)<a href="https://agentmods.dev/skills/salesforcecommercecloud/b2c-developer-tooling/sfnext-routing"><img src="https://agentmods.dev/badge/skills/salesforcecommercecloud/b2c-developer-tooling/sfnext-routing.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 | $0.00061 | $0.01311 |
| Opus 5 | $0.00030 | $0.00656 |
| Sonnet 5 | $0.00012 | $0.00262 |
| Haiku 4.5 | $0.00006 | $0.00131 |
Grade A, and why
sfnext-routing 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 — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Routing Skill
This skill covers React Router 7 file-based routing in Storefront Next projects.
Overview
Storefront Next uses React Router 7 in framework mode with flat-routes file conventions. Route files live in src/routes/ and file names map directly to URL paths using dot (.) separators for nesting.
Route File Conventions
File Name to URL Mapping
| File Name | URL Path | Notes |
|---|---|---|
_app.tsx |
— | Layout route (wraps child routes) |
_app._index.tsx |
/ |
Home page (index of _app layout) |
_app.product.$productId.tsx |
/product/:productId |
Dynamic parameter |
_app.category.$categoryId.tsx |
/category/:categoryId |
Dynamic parameter |
_app.cart.tsx |
/cart |
Static route |
_app.account.tsx |
/account |
Layout for account pages |
_app.account.orders.tsx |
/account/orders |
Nested under account layout |
Naming Rules
- Dots (
.) create path segments:_app.product.tsxmaps to/product $prefix marks dynamic parameters:$productIdbecomes:productId_prefix marks layout routes (pathless):_app.tsxwraps children without adding a URL segment_indexmatches the parent path exactly (index route)
See Route Conventions Reference for the complete naming rules.
Route Module Exports
Each route file can export these values:
loader — Server-side data loading
import { createApiClients } from '@/lib/api-clients';
import type { LoaderFunctionArgs } from 'react-router';
export function loader({ params, context }: LoaderFunctionArgs) {
const clients = createApiClients(context);
return {
product: clients.shopperProducts.getProduct({
params: { path: { id: params.productId } }
}).then(({ data }) => data),
};
}
action — Handle mutations (form submissions)
import { data, redirect } from 'react-router';
import type { ActionFunctionArgs } from 'react-router';
export async function action({ request, context }: ActionFunctionArgs) {
const formData = await request.formData();
// Handle mutation...
return data({ success: true });
}
What ships with it
1 file 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.
- 2d ago First seen · 181 lines · 61 tokens per session scan A 5d938e287730
sfnext-routing is a skill published in the GitHub repository SalesforceCommerceCloud/b2c-developer-tooling (53 stars, last pushed today), licensed Apache-2.0. It adds 61 tokens to every session and 1,311 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-03.
Other skills, from other repositories
review-local-branch
Deep code review of the branch you are standing on, before it becomes a PR. Scope is merge-base..working-tree, so it covers commits, staged and unstaged changes together. Runs the same review lanes as review-pr — implementation, verification, approach, security — against the local checkout through the sandbox CLI, and…
update-cnw-templates
Update the CNW (create-nx-workspace) template repos (nrwl/empty-template, nrwl/react-template, etc.) to a target nx version via nx migrate, verify each repo, and open a PR per repo. Clones repos it needs - assumes no local checkout. Use when asked to "update the CNW templates", "migrate the templates to nx X", "bump…
gh-stack
Manages stacked PRs and splits multi-part work into reviewable branches with gh-stack. Use for stack creation, viewing, edits, push, submit, sync, rebase, merge, or checkout; when asked to split or isolate work for review; whenever a user mentions a stack, branch layers, dependent PRs, or gh stack; or when a stack is…
authoring-ci-workflows
Use when adding or editing a GitHub Actions workflow, composite action, or reusable workflow under .github/ — new CI jobs, triggers, matrices, checkout/clone tuning, action pinning, GitHub App token auth, concurrency groups, timeout-minutes, paths filters, caching, or runner choice. Covers PostHog's workflow-authoring…
trellis-update-spec
Captures executable contracts and coding conventions into .trellis/spec/ documents. Use when learning something valuable from debugging, implementing, or discussion that should be preserved for future sessions.
trellis-session-insight
Reach into past AI conversation history through the trellis mem CLI. Use whenever the user asks 'how did we solve X last time', 'have we discussed this before', 'what was the decision on X', 'remind me what we did in this task', '上次怎么解的', '之前讨论过吗', '想起一段对话', or when starting a brainstorm that overlaps prior work…