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 nextjs-reactgit 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/nextjs-react)<a href="https://agentmods.dev/skills/kouroshez/coding-os/nextjs-react"><img src="https://agentmods.dev/badge/skills/kouroshez/coding-os/nextjs-react/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/nextjs-react"><img src="https://agentmods.dev/badge/skills/kouroshez/coding-os/nextjs-react.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.00065 | $0.03261 |
| Opus 5 | $0.00032 | $0.01631 |
| Sonnet 5 | $0.00013 | $0.00652 |
| Haiku 4.5 | $0.00006 | $0.00326 |
Grade A, and why
nextjs-react 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 5d 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 — 486 lines — stays where its author put it; the contents beside it link to each section on GitHub.
This skill enforces Next.js 16 App Router and React patterns. It depends_on: [clean-code, frontend-fundamentals] which are loaded transitively — clean-code gives universal code quality, frontend-fundamentals gives stack-agnostic UI patterns (three-state async, hydration, a11y, SEO). This skill adds ONLY Next.js-App-Router and React-version-specific layering on top.
Pre-Code Checklist
Before writing or modifying any .ts/.tsx file:
- Read
docs/engineering/frontend-rules.md - If touching data fetching or rendering logic: read
docs/engineering/frontend-rendering-rules.md - If touching design, layout, or styling: read
STYLE_GUIDE.md+ the relevant file indocs/design/ - If touching API calls or error handling: read
docs/api-contracts/error-format.md - Search the repo for existing components and hooks before creating new ones (use Grep/Glob)
1. Server Components First
Default to Server Components. Never add 'use client' unless the component genuinely requires it.
When to use 'use client'
- Browser APIs (
window,document,navigator,localStorage) - Event handlers (
onClick,onChange,onSubmit) - React state or effects (
useState,useEffect,useReducer,useRefwith mutations) - Third-party client-only libraries (e.g., motion, chart libraries)
Correct — Server Component (default)
// app/products/[slug]/page.tsx
// No 'use client' — this is a Server Component
import { getProduct } from "@/lib/api/products";
import { ProductDetails } from "@/components/products/product-details";
export default async function ProductPage({
params,
}: {
params: Promise<{ slug: string }>;
}) {
const { slug } = await params;
const product = await getProduct(slug);
return <ProductDetails product={product} />;
}
Correct — Client Component (only when needed)
// components/products/add-to-cart-button.tsx
"use client";
import { useState } from "react";
interface AddToCartButtonProps {
productId: string;
onAdd: (id: string) => void;
}
export function AddToCartButton({ productId, onAdd }: AddToCartButtonProps) {
const [isAdding, setIsAdding] = useState(false);
async function handleClick() {
setIsAdding(true);
try {
await onAdd(productId);
} finally {
setIsAdding(false);
}
}
return (
<button onClick={handleClick} disabled={isAdding}>
{isAdding ? "Adding..." : "Add to Cart"}
</button>
);
}
What ships with it
2 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.
- 5d ago First seen · 486 lines · 65 tokens per session scan A 7e331ec58bd6
nextjs-react is a skill published in the GitHub repository kouroshez/coding-os (6 stars, last pushed yesterday), licensed Apache-2.0. It adds 65 tokens to every session and 3,261 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-09-03.
Other skills, from other repositories
remotion
Toolkit-specific Remotion patterns — custom transitions, shared components, and project conventions. For core Remotion framework knowledge (hooks, animations, rendering, etc.), see the remotion-official skill.
frontend-code-review
Trigger when the user requests a review of frontend files (e.g., .tsx, .ts, .js). Support both pending-change reviews and focused file reviews while applying the checklist rules.
react-web
React web development with hooks, React Query, Zustand.
react-native
React Native mobile patterns, platform-specific code.
spotpatch
A development workflow for React that connects a selected page element to its JSX or TSX source code and gathers context for review.
ring:applying-composition-patterns
React composition patterns that scale. Avoid boolean prop proliferation by using compound components, lifting state, and composing internals. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or during architecture review. Skip for simple components with 1-2 props…