frontend

frontend is a skill for Claude Code from DojoCodingLabs/code-sensei. It costs 37 tokens per session (715 once invoked), scanned A, original, MIT.

Guidance for building React frontends, where reusable components are combined to create web pages and manage their data and state.

In plain words
What is it for?
Working with JSX or TSX files, React components, component properties, state management, and modern frontend development.
Why use it?
It helps structure interface code into maintainable pieces instead of putting the whole page in one large file.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the code-sensei plugin — 10 skills, 10 commands, 1 agent, 3 hooks shipped together

Good fit Working with JSX or TSX files, React components, component properties, state management, and modern frontend development.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/dojocodinglabs/code-sensei/frontend
Install

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.

Any agent
npx skills add DojoCodingLabs/code-sensei --skill frontend
Clone the repo
git clone --depth 1 https://github.com/DojoCodingLabs/code-sensei

Made for: Claude Code.

Or install code-sensei, the plugin that ships this one along with the rest of its 10 skills, 10 commands, 1 agent, 3 hooks.

Wrote 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.

agentmods badge for frontend

README.md
[![agentmods](https://agentmods.dev/badge/skills/dojocodinglabs/code-sensei/frontend/github.svg)](https://agentmods.dev/skills/dojocodinglabs/code-sensei/frontend)
Your own site
<a href="https://agentmods.dev/skills/dojocodinglabs/code-sensei/frontend"><img src="https://agentmods.dev/badge/skills/dojocodinglabs/code-sensei/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.

agentmods 80×15 button for frontend

Your own site · 80×15
<a href="https://agentmods.dev/skills/dojocodinglabs/code-sensei/frontend"><img src="https://agentmods.dev/badge/skills/dojocodinglabs/code-sensei/frontend.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 37 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 715 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00037 $0.00715
Opus 5.5 $0.00015 $0.00286
Sonnet 5.5 $0.00007 $0.00143
Haiku 4.5 $0.00004 $0.00072

Measured 1mo ago against content hash 9a4bc946bb1e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

  • frontend — 100% identical, 0 lines differ
skills/frontend/SKILL.md · 52 lines

How it starts

The opening of the file, as written. The whole thing — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Frontend Development — CodeSensei Teaching Module

React

  • Analogy: React lets you build a webpage out of LEGO bricks. Each brick (component) is a self-contained piece that knows how to display itself. You snap them together to build the full page.
  • Key insight: Instead of one giant HTML file, React breaks the page into small, reusable pieces. A "Navbar" component, a "Card" component, a "Button" component — each one independent.

Components

  • Analogy: A component is like a custom sticker. You design it once (define the component), then stick it anywhere on the page as many times as you want.
  • Teaching flow:
    1. A component is a function that returns HTML-like code (JSX)
    2. Components can receive data through "props" (like settings or configuration)
    3. Components can have their own memory through "state"
  • Quiz: "If we have a 'UserCard' component, how many times can we use it on a page?"

Props

  • Analogy: Props are like the settings on a TV remote. The TV (component) is always the same, but you can change the channel, volume, and brightness (props) to customize what you see.
  • <UserCard name="Juan" role="CEO" /> — the component receives name and role as props
  • Key insight: Props flow DOWN. A parent component passes data to its children, not the other way around.

State (useState)

  • Analogy: State is the component's personal notebook. It remembers things that can change — like whether a menu is open, what the user typed, or how many items are in a cart.
  • Key insight: When state changes, React automatically re-draws that part of the page. You don't have to manually update the HTML — just change the state and React handles the rest.
  • Quiz: "If a counter starts at 0 and the user clicks '+' three times, what should the state be?"

useEffect

  • Analogy: A "when this happens, do that" instruction. Like setting an alarm — when the component first appears, go fetch the latest data from the server.
  • Key insight: Effects run AFTER the component displays. They're for side effects — things that happen outside the component itself, like loading data or starting a timer.

Read the full file on GitHub · 52 lines

Changes

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.

  1. 1mo ago First seen · 52 lines · 37 tokens per session scan A 9a4bc946bb1e

Subscribe to this mod's changes

frontend is a skill published in the GitHub repository DojoCodingLabs/code-sensei (14 stars, last pushed 22d ago), licensed MIT. It adds 37 tokens to every session and 715 once invoked, about $0.0001 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.