claude-workspace: Command for Claude Code

.claude/commands/component-gen.md

component-gen is a command for Claude Code from Piyush8296/claude-workspace. It costs 13 tokens per session (556 once invoked), scanned A, original, MIT.

A React component starter that creates the component, its TypeScript types, a test, and a Storybook story using the project's expected structure.

In plain words
What is it for?
Use it when adding a React component, including one inside a specified folder, and when you want the related test and story scaffolded with it.
Why use it?
It removes the repeated setup work and helps new components begin with testing, examples, and typed interfaces in place.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

This is Piyush8296/claude-workspace's own configuration. It tells Claude Code how to work on claude-workspace itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything claude-workspace configures →

Reuse

Borrowing it

Nothing to install: this file belongs to Piyush8296/claude-workspace. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/Piyush8296/claude-workspace/main/.claude/commands/component-gen.md
Clone the repo
git clone --depth 1 https://github.com/Piyush8296/claude-workspace

Made for: Claude Code.

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 component-gen

README.md
[![agentmods](https://agentmods.dev/badge/commands/piyush8296/claude-workspace/component-gen.svg)](https://agentmods.dev/commands/piyush8296/claude-workspace/component-gen)
Your own site
<a href="https://agentmods.dev/commands/piyush8296/claude-workspace/component-gen"><img src="https://agentmods.dev/badge/commands/piyush8296/claude-workspace/component-gen.svg" alt="Measured on agentmods" height="20"></a>
Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 556 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.00013 $0.00556
Opus 5 $0.00006 $0.00278
Sonnet 5 $0.00003 $0.00111
Haiku 4.5 $0.00001 $0.00056

Measured 6d ago against content hash 03f98b0eef5c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

component-gen 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 6d 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.

.claude/commands/component-gen.md · 95 lines

How it starts

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

Component Generator

Generate component: $ARGUMENTS

Instructions

1. Determine component location

  • If the component name includes a path (e.g., features/auth/LoginForm), use that path
  • Otherwise, place in src/components/$ARGUMENTS/
  • Check if the component already exists — if so, ask before overwriting

2. Create the component file

<ComponentName>.tsx

import { type ComponentProps } from 'react';

interface <ComponentName>Props {
  // TODO: Define props
}

export function <ComponentName>({ ...props }: <ComponentName>Props) {
  return (
    <div data-testid="<component-name>">
      {/* TODO: Implement */}
    </div>
  );
}

Follow these conventions:

  • Named export (no default export)
  • Props interface defined in same file
  • data-testid for testing
  • Semantic HTML
  • TypeScript strict — no any

3. Create the test file

<ComponentName>.test.tsx

import { render, screen } from '@testing-library/react';
import { describe, it, expect } from 'vitest';
import { <ComponentName> } from './<ComponentName>';

const getDefaultProps = (overrides?: Partial<ComponentProps<typeof <ComponentName>>>) => ({
  // Default props
  ...overrides,
});

describe('<ComponentName>', () => {
  it('renders without crashing', () => {
    render(<<ComponentName> {...getDefaultProps()} />);
    expect(screen.getByTestId('<component-name>')).toBeInTheDocument();
  });

  it('handles empty state', () => {
    // TODO: Test empty state
  });

  it('handles loading state', () => {
    // TODO: Test loading state
  });

  it('handles error state', () => {
    // TODO: Test error state
  });
});

4. Create barrel export

index.ts

export { <ComponentName> } from './<ComponentName>';
export type { <ComponentName>Props } from './<ComponentName>';

5. Summary

After generating, print:

  • Files created (with paths)
  • Next steps: implement the component logic, fill in props, write real tests
  • Remind about the react-patterns skill for component architecture guidance

Read the full file on GitHub · 95 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. 6d ago First seen · 95 lines · 13 tokens per session scan A 03f98b0eef5c

Subscribe to this mod's changes

component-gen is a command published in the GitHub repository Piyush8296/claude-workspace (2 stars, last pushed 4mo ago), licensed MIT. It adds 13 tokens to every session and 556 once invoked, about $0.0001 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.