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 skills add kouroshez/coding-os --skill frontend-fundamentalsgit clone --depth 1 https://github.com/kouroshez/coding-osWrote 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/kouroshez/coding-os/frontend-fundamentals)<a href="https://agentmods.dev/skills/kouroshez/coding-os/frontend-fundamentals"><img src="https://agentmods.dev/badge/skills/kouroshez/coding-os/frontend-fundamentals/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/skills/kouroshez/coding-os/frontend-fundamentals"><img src="https://agentmods.dev/badge/skills/kouroshez/coding-os/frontend-fundamentals.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.00068 | $0.02890 |
| Opus 5 | $0.00034 | $0.01445 |
| Sonnet 5 | $0.00014 | $0.00578 |
| Haiku 4.5 | $0.00007 | $0.00289 |
Grade A, and why
frontend-fundamentals 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 — 214 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend Fundamentals — Stack-Agnostic UI Patterns
Universal guidance for every component-based UI framework: React, React Native, Vue, Svelte, Solid. Framework-specific layering (Next.js App Router, React Native navigation, Vue composition API) lives in the stack-specific skill that depends_on: [frontend-fundamentals].
Loaded automatically when enforce-skill.sh routes a file under frontend/ that matches a stack skill.
0. Every async UI is three-state
Every screen or section that fetches data MUST explicitly handle three states. Missing any of them is a bug:
| State | Required UI |
|---|---|
| Loading | skeleton or spinner; indication of progress |
| Error | actionable message + retry affordance; never a blank screen |
| Empty | explains why it's empty + suggests next action; never an ambiguous zero rows |
A fourth state — stale/refreshing while data exists — is a common polish item. Render the previous data with a subtle loading indicator; don't blank the UI.
Anti-pattern: {data && <List data={data} />}. This silently hides error AND empty AND loading behind a single falsy check.
1. Server components vs. client components (React 19+ / Next 15+)
Default everything to server components. Convert to client only when one of these is present:
- Interactive state (
useState,useReducer, form state). - Event handlers (
onClick,onChange,onSubmit). - Browser-only APIs (
window,localStorage,navigator,document,IntersectionObserver). - Hooks that require a client (
useEffect,useLayoutEffect, most third-party hooks).
Server components don't ship JS to the browser and can fetch directly. This is the single biggest first-load perf win in modern React. A component that's "use client" without a reason is accidental bundle bloat.
2. Hydration safety
Anything whose output differs between the first server render and the first client render causes a hydration mismatch. Common culprits:
new Date(),Math.random()at top level of a client component.window.matchMedia(...)defaulting to different value.- Reading
localStoragesynchronously during render.
What ships with it
3 files 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.
- 8d ago First seen · 214 lines · 68 tokens per session scan A 5438516ff5d1
frontend-fundamentals is a skill published in the GitHub repository kouroshez/coding-os (6 stars, last pushed yesterday), licensed Apache-2.0. It adds 68 tokens to every session and 2,890 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
graph-mutation-plan
Cookbook for composing an applygraphmutations plan — stable entitykey patterns, the canonical label/edge vocabulary, evidence/invalidation/confidence discipline, and a worked example. Load this when building a non-trivial mutation plan.
potpie-cli
Use when the task is centered on running, explaining, configuring, or troubleshooting the potpie command: doctor, login, pot management, source registration, search, graph workbench reads/writes, and pot scope behavior.
potpie-infra-architecture
Use for project infra and architecture context: environments, adapters, runtime configuration, deployments, service dependencies, datastores, API contracts, ownership, incidents, and dependency blast radius.
screenshot-studio
Regenerate the Pisper product screenshots under docs/shots/ against the current UI. Starts an isolated dev instance, seeds fictional demo data through the real runtime APIs, captures every referenced page at the exact 2558x1380 asset size, and replaces the files. Use only when the user asks to refresh product…
css-debug
Use this skill to diagnose CSS and frontend layout issues such as positioning, overflow clipping, Tailwind class conflicts, z-index stacking, and React rendering visibility problems.
ring:validating-ux-completeness
Validating that UX specifications are complete before technical design: a read-only checklist over wireframes, states, responsive behavior, accessibility, and component-library alignment, emitting a DESIGN VALIDATED / NEEDS REVISION verdict to design-validation.md. Standalone utility — run after a product-designer…