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/kws-projects/react-boilerplate/customize-starternpx skills add kws-projects/react-boilerplate --skill customize-startergit clone --depth 1 https://github.com/kws-projects/react-boilerplateWhat 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.00907 |
| Opus 5 | $0.00030 | $0.00453 |
| Sonnet 5 | $0.00012 | $0.00181 |
| Haiku 4.5 | $0.00006 | $0.00091 |
Grade A, and why
customize-starter 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Customize Starter
Use this when a user is adapting this boilerplate into their own project. The files that contain starter/demo content are listed below, so there is no need to scan the whole repo. Edit only what the user asks for; confirm before deleting.
1. Rename the project
package.json- updatename,version(reset to0.1.0), and add adescription.index.html- update the<title>.src/config/env.ts- theappNamefallback defaults to'React Boilerplate'; change it to the new project name..env.example(and the user's.env.development.local/.env.production.local) - setVITE_APP_NAMEto the new project name.docker-compose.yml- updateimageandcontainer_name(currentlyreact-boilerplate).README.md- replace with the new project's README.
2. Remove the demo feature
The "home" feature is a placeholder example. To remove it:
- Delete
src/features/home/(containscomponents/HomePage.tsxandcomponents/__tests__/HomePage.test.tsx). src/app/App.tsx- it renders<HomePage />; replace with the real root.src/i18n/locales/en/common.jsonandsrc/i18n/locales/ar/common.json- remove the demo keys (home.*,actions.increment) and keep/add real ones. Keep keys in sync across every locale.
3. Set up analytics & monitoring
.env.development.local/.env.production.local- fill in the GA4 and Sentry values for the new project:VITE_ANALYTICS_ENABLED=true,VITE_GA_MEASUREMENT_ID=G-…VITE_SENTRY_ENABLED=true,VITE_SENTRY_DSN=https://…- Optionally set
VITE_SENTRY_ENVIRONMENT,VITE_SENTRY_RELEASE, sample rates, andVITE_GA_DEBUG_MODE.
- For Sentry source-map uploads in CI, set
SENTRY_AUTH_TOKEN,SENTRY_ORG, andSENTRY_PROJECTas build-time secrets. - See the
analytics-and-monitoringskill for usage patterns.
4. Optional cleanup
public/vite.svg- replace the favicon; update the<link rel="icon">inindex.html..cursor/skills/customize-starter/- delete this skill once the project is set up (it only applies to the starter).
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 · 75 lines · 61 tokens per session scan A 6dc3ea1e90aa
customize-starter is a skill published in the GitHub repository kws-projects/react-boilerplate (3 stars, last pushed 3mo ago), licensed MIT. It adds 61 tokens to every session and 907 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-08-31.
Other skills, from other repositories
pro-upgrade
Use when the user wants to upgrade their Ant Design Pro project to the latest version. Triggers on: upgrade pro, pro upgrade, migrate pro, update pro, 升级, 迁移项目, "how to upgrade", "update to latest", "keep project up to date".
intlayer-next-js
Integrates Intlayer internationalization with Next.js App Router and Pages Router. Use when the user asks to "setup Next.js i18n", use "useIntlayer" in Server Components, or handle client-side translations in Next.js.
intlayer-react
Integrates Intlayer internationalization with React component. Use when the user asks to "setup React i18n", create a new translated component, use the "useIntlayer" hook, or configure providers.
frontend-technical-spec
Defines React environment, component architecture, state/data flow, build verification, and frontend non-functional criteria from repository evidence. Use when configuring or designing a React frontend, its build, or its runtime boundaries.
frontend-typescript-rules
Applies React/TypeScript type safety, component design, and state management rules. Use when implementing React components.
next-upgrade
Upgrade Next.js to the latest version following official migration guides and codemods.