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/mertjane/awesome-claude-commandsWrote 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/commands/mertjane/awesome-claude-commands/nxt-component)<a href="https://agentmods.dev/commands/mertjane/awesome-claude-commands/nxt-component"><img src="https://agentmods.dev/badge/commands/mertjane/awesome-claude-commands/nxt-component/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/commands/mertjane/awesome-claude-commands/nxt-component"><img src="https://agentmods.dev/badge/commands/mertjane/awesome-claude-commands/nxt-component.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.00033 | $0.01087 |
| Opus 5 | $0.00016 | $0.00544 |
| Sonnet 5 | $0.00007 | $0.00217 |
| Haiku 4.5 | $0.00003 | $0.00109 |
Grade A, and why
nxt-component 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 9d 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate Next.js Component
Create a fully typed Next.js + Tailwind component based on the name provided in $ARGUMENTS.
Parse $ARGUMENTS:
- First word → component name (PascalCase). If not PascalCase, convert it.
- Second word (optional) → custom output path. If not provided, detect automatically.
Step 1 — Detect Project Conventions
Search for existing component files:
Glob: {components,src/components}/**/*.{tsx,jsx}
Read 2–3 existing component files and detect:
Function style:
export default function Name()→ use named function declarationconst Name = () =>orexport const Name→ use arrow function- Default to arrow function if no components found
Folder structure:
- If components are in individual folders:
components/Button/Button.tsx+components/Button/index.ts→ use folder structure - If components are flat files:
components/Button.tsx→ use single file
Import style:
- Check how
classNameis used — plain strings orcn()/clsx()/twMerge()utility - If
cnorclsxis used, import and use it in the new component
Output path:
- If second argument given → use that path
- If
src/components/exists → usesrc/components/ - If
components/exists → usecomponents/ - Otherwise → create
components/at project root
Step 2 — Check for Tailwind Config
Read tailwind.config.ts or tailwind.config.js if present:
- Note any custom colors, spacing, or font tokens to prefer in the component
Step 3 — Generate Component
Generate the component following the detected conventions. The component must:
- Accept a
classNameprop for external style overrides - Use TypeScript interface for props (never
type, alwaysinterface) - Include
childrenprop if it makes sense for the component name (e.g. Button, Card, Modal) - Use semantic HTML elements (e.g.
<button>for Button,<section>for Section) - Export the props interface alongside the component
Template (arrow function, single file):
import { cn } from "@/lib/utils" // only if cn utility detected
interface {ComponentName}Props {
className?: string
children?: React.ReactNode
// additional props based on component name
}
export const {ComponentName} = ({ className, children, ...props }: {ComponentName}Props) => {
return (
<div className={cn("", className)} {...props}>
{children}
</div>
)
}
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.
- 9d ago First seen · 133 lines · 33 tokens per session scan A f99199b713fa
nxt-component is a command published in the GitHub repository mertjane/awesome-claude-commands (2 stars, last pushed 6mo ago), licensed MIT. It adds 33 tokens to every session and 1,087 once invoked, about $0.0002 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 commands, from other repositories
svelte:component
Create new Svelte components with best practices, proper structure, and optional TypeScript support.
scaffold-nextjs
Scaffold a basic Next.js 15 project with modern best practices.
migrate-to-nextjs15
Upgrade this Next.js project to version 15. Update package.json dependencies to Next.js 15 and React 19. Migrate App Router patterns and update metadata API usage following latest conventions. Fix breaking changes in configuration, middleware, and API routes. Update next.config.ts with new configuration options. Test…
generate-idl-client
Generate TypeScript client from Solana program IDL using Codama or Anchor.
vue3
Apply Vue 3 with TypeScript and Composition API patterns.
types
Run bun run typecheck or tsc or npx tsc and fix all type errors.