Borrowing it
Nothing to install: this file belongs to salesforce-ux/design-system-2-starter-kit. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/salesforce-ux/design-system-2-starter-kit/main/AGENTS.mdgit clone --depth 1 https://github.com/salesforce-ux/design-system-2-starter-kitWrote 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/instructions/salesforce-ux/design-system-2-starter-kit/agents-md)<a href="https://agentmods.dev/instructions/salesforce-ux/design-system-2-starter-kit/agents-md"><img src="https://agentmods.dev/badge/instructions/salesforce-ux/design-system-2-starter-kit/agents-md.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.01518 | $0.01518 |
| Opus 5 | $0.00759 | $0.00759 |
| Sonnet 5 | $0.00304 | $0.00304 |
| Haiku 4.5 | $0.00152 | $0.00152 |
Grade A, and why
design-system-2-starter-kit AGENTS.md 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 8d 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent guidelines: Design System 2 Starter Kit
This repository is a starter template for prototyping Salesforce-aligned UIs locally. It uses LWC (Lightning Web Components), Vite, SLDS (Salesforce Lightning Design System), and lightning-base-components, with synthetic shadow DOM and client-side routing.
Project-specific guidance
Where to put code
- Route-level views:
src/modules/page/<name>/→ tagpage-<name>. Add a route insrc/routes.config.js, then import and register the component insrc/modules/shell/app/app.js(ROUTE_COMPONENTS). The router picks up new routes automatically;src/router.jsdoes not need editing. - New features and pages are primary by default: When the user requests a new feature or page, make it the primary navigation tab and initial landing page without asking for confirmation. Give it a
navPage, place that id first in every applicable navigation app'spageslist insrc/apps.config.js, and set each applicable app'sdefaultPathto its app-prefixed route so it appears immediately on page load. Keep existing pages as secondary tabs unless the user explicitly requests different behavior. Apps without primary navigation, such as the Builder app, are exempt. - Reusable UI / SLDS blueprints:
src/modules/ui/<name>/→ tagui-<name>. Use inside pages, the shell, or other components. - App shell:
src/modules/shell/<name>/→ tagshell-. Root app, layout, theme, docked panels — not route views (page-) and not reusable components (ui-*). - Do not add components under
src/build/lightning-icon/shims/except the checked-in icon overrides, or undersrc/modules/lightning/.
SLDS linter
After you change any .html or .css file, run the SLDS linter on each file you touched before considering the task complete:
npx @salesforce-ux/slds-linter@latest lint <path-to-changed-file>
Fix reported issues where possible. If something cannot be fixed, say so briefly.
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.
- 8d ago First seen · 68 lines · 1,518 tokens per session scan A 8b3eaaeed26d
design-system-2-starter-kit AGENTS.md is an instructions file published in the GitHub repository salesforce-ux/design-system-2-starter-kit (23 stars, last pushed 17d ago), licensed Apache-2.0. It adds 1,518 tokens to every session, about $0.0076 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-30.
Other instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.