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.
git clone --depth 1 https://github.com/WoJiSama/skill-based-architectureWrote 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/rules/wojisama/skill-based-architecture/frontend)<a href="https://agentmods.dev/rules/wojisama/skill-based-architecture/frontend"><img src="https://agentmods.dev/badge/rules/wojisama/skill-based-architecture/frontend/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/rules/wojisama/skill-based-architecture/frontend"><img src="https://agentmods.dev/badge/rules/wojisama/skill-based-architecture/frontend.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.00005 | $0.00197 |
| Opus 5.5 | $0.00002 | $0.00079 |
| Sonnet 5.5 | $0.00001 | $0.00039 |
| Haiku 4.5 | $0.00001 | $0.00020 |
Grade A, and why
frontend 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 1mo 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.
What it actually says
Frontend Rules
- Use
summarizeCartfor cart display data; do not duplicate subtotal math in UI components. - Keep raw cent values available for calculations and analytics.
- Format display values only with
formatMoney. - Show subtotal and total together when a discount is active.
Add UI Component Flow
- Confirm the component needs cart data.
- Use
summarizeCartfor derived values. - Keep component state in raw cents, not formatted strings.
- Test a discounted and non-discounted cart.
Pitfalls
- If a component stores
"$12.99"in state, later discount math has to parse a display string and can drift. - Cursor-only frontend rules drift from
AGENTS.mdandCLAUDE.md; this should becomeskills/demo-shop/rules/frontend-rules.md.
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.
- 1mo ago First seen · 27 lines · 5 tokens per session scan A b73387283beb
frontend is a cursor rule published in the GitHub repository WoJiSama/skill-based-architecture (619 stars, last pushed 29d ago), licensed MIT. It adds 5 tokens to every session and 197 once invoked, about $0.0000 per session on Opus 5.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 cursor rules, from other repositories
frontend-theme-guidelines
Frontend theme-system rules for NekroAgent, covering the theme architecture, core file structure, design principles, and usage guidance. A theme system controls shared visual choices such as colors, typography, and layouts.
design
All tasks related to updating frontend components, CSS, and general styling.
templates
Tera template variables, blocks, and theme conventions.
shadcn-tailwind-guide
A guide to building new components with shadcn/ui and Tailwind CSS, a utility-based system for styling interfaces.
performance-optimization
A guide to improving the speed and responsiveness of frontend applications.
40-styling
CSS modules colocated with components, kebab-case filenames. See rules/core/styling.md.