copilot-dev: Command for Claude Code

.github/prompts/generate-react-component.prompt.md

generate-react-component is a command for Claude Code, GitHub Copilot from timothywarner/copilot-dev. It costs 21 tokens per session (1,902 once invoked), scanned A, original, MIT.

A command that scaffolds a TypeScript React functional component from a name, purpose, props, and state needs. It creates the component code, accessibility details, and a test stub.

In plain words
What is it for?
Use it to create new React components with typed props, React hooks, and an initial test file.
Why use it?
It removes the repetitive setup involved in starting a React component and gives the component a consistent structure.

Command for Claude CodeGitHub Copilot

Written for Claude Code and GitHub Copilot: argument-hint in frontmatter, but also a Copilot chat mode or prompt. Also seen: model in frontmatter.

This is timothywarner/copilot-dev's own configuration. It tells Claude Code and GitHub Copilot how to work on copilot-dev 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 copilot-dev configures →

Reuse

Borrowing it

Nothing to install: this file belongs to timothywarner/copilot-dev. 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/timothywarner/copilot-dev/main/.github/prompts/generate-react-component.prompt.md
Clone the repo
git clone --depth 1 https://github.com/timothywarner/copilot-dev

Made for: Claude Code, GitHub Copilot.

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 generate-react-component

README.md
[![agentmods](https://agentmods.dev/badge/commands/timothywarner/copilot-dev/generate-react-component/github.svg)](https://agentmods.dev/commands/timothywarner/copilot-dev/generate-react-component)
Your own site
<a href="https://agentmods.dev/commands/timothywarner/copilot-dev/generate-react-component"><img src="https://agentmods.dev/badge/commands/timothywarner/copilot-dev/generate-react-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.

agentmods 80×15 button for generate-react-component

Your own site · 80×15
<a href="https://agentmods.dev/commands/timothywarner/copilot-dev/generate-react-component"><img src="https://agentmods.dev/badge/commands/timothywarner/copilot-dev/generate-react-component.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 21 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,902 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.00021 $0.01902
Opus 5.5 $0.00008 $0.00761
Sonnet 5.5 $0.00004 $0.00380
Haiku 4.5 $0.00002 $0.00190

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

Security

Grade A, and why

generate-react-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 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.

.github/prompts/generate-react-component.prompt.md · 237 lines

How it starts

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

Your goal is to scaffold a complete, production-ready React functional component based on the information provided.

What I need from you

If the component name and purpose are not already specified, ask for:

  1. Component name — PascalCase, descriptive (e.g., UserProfileCard, SearchResultsList)
  2. Component purpose — one sentence describing what it renders and what it does
  3. Key props — what data does it accept? What callbacks does it expose?
  4. State needed? — does it manage any local state (loading, open/closed, selected item)?

Component name: ${input:componentName:MyComponent} Component purpose: ${input:componentPurpose:Describe what this component does}


What I'll generate

1. The component file: ${input:componentName:MyComponent}.tsx

import { useState, useEffect, useCallback } from 'react'

// --- Types ---

/**
 * Props for the ${input:componentName:MyComponent} component.
 */
export interface ${input:componentName:MyComponent}Props {
  /** Primary data to display */
  data: SomeDataType
  /** Called when the user performs the primary action */
  onAction?: (item: SomeDataType) => void
  /** Optional CSS class for the root element */
  className?: string
  /** When true, renders in a loading/skeleton state */
  isLoading?: boolean
}

// --- Component ---

/**
 * ${input:componentName:MyComponent} — ${input:componentPurpose:describe what this renders}
 *
 * @example
 * ```tsx
 * <${input:componentName:MyComponent}
 *   data={myData}
 *   onAction={(item) => console.log('Action on', item)}
 * />
 * ```
 */
export function ${input:componentName:MyComponent}({
  data,
  onAction,
  className = '',
  isLoading = false,
}: ${input:componentName:MyComponent}Props) {
  // Local state
  const [isExpanded, setIsExpanded] = useState(false)

  // Side effects
  useEffect(() => {
    // Example: reset expanded state when data changes
    setIsExpanded(false)
  }, [data])

  // Stable callbacks
  const handleAction = useCallback(() => {
    onAction?.(data)
  }, [data, onAction])

  // Loading state guard
  if (isLoading) {
    return (
      <div
        className={`animate-pulse rounded-lg bg-gray-100 h-24 ${className}`}
        aria-busy="true"
        aria-label="Loading..."
      />
    )
  }

  return (
    <article
      className={`rounded-lg border p-4 ${className}`}
      aria-label={`${input:componentName:MyComponent} for ${data.name ?? 'item'}`}
    >
      {/* Header */}
      <header className="flex items-center justify-between">
        <h2 className="text-lg font-semibold">{data.name}</h2>
        <button
          type="button"
          onClick={() => setIsExpanded((prev) => !prev)}
          aria-expanded={isExpanded}
          aria-controls="component-details"
          className="text-sm text-blue-600 hover:underline focus-visible:outline-2"
        >
          {isExpanded ? 'Collapse' : 'Expand'}
        </button>
      </header>

      {/* Expandable details */}
      {isExpanded && (
        <section id="component-details" className="mt-2 text-sm text-gray-600">
          {data.description}
        </section>
      )}

      {/* Primary action */}
      {onAction && (
        <footer className="mt-4">
          <button
            type="button"
            onClick={handleAction}
            className="rounded bg-blue-600 px-4 py-2 text-white hover:bg-blue-700 focus-visible:outline-2"
          >
            Take Action
          </button>
        </footer>
      )}
    </article>
  )
}

export default ${input:componentName:MyComponent}

Read the full file on GitHub · 237 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 · 237 lines · 21 tokens per session scan A 13571305e751

Subscribe to this mod's changes

generate-react-component is a command published in the GitHub repository timothywarner/copilot-dev (46 stars, last pushed 1mo ago), licensed MIT. It adds 21 tokens to every session and 1,902 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-09-20.