generate-component

generate-component is a command for Claude Code from TheBeardedBearSAS/claude-craft. It costs 6 tokens per session (1,165 once invoked), scanned A, original, MIT.

A generator for Angular standalone components, which are self-contained UI building blocks that do not need a separate module. It creates the component’s code, template, styles, tests, and export file.

In plain words
What is it for?
Use it to create a component such as a user card or data table, optionally inside a feature folder, with its supporting files ready for development.
Why use it?
It removes repetitive setup and keeps new components in the project’s expected folder structure. Tests are created at the same time as the component.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter.

Part of the claude-craft plugin — 56 skills, 94 commands, 47 agents, 5 hooks shipped together

Install

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.

agentmods
npx agentmods add commands/thebeardedbearsas/claude-craft/generate-component
Clone the repo
git clone --depth 1 https://github.com/TheBeardedBearSAS/claude-craft

Made for: Claude Code.

Or install claude-craft, the plugin that ships this one along with the rest of its 56 skills, 94 commands, 47 agents, 5 hooks.

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

README.md
[![agentmods](https://agentmods.dev/badge/commands/thebeardedbearsas/claude-craft/generate-component.svg)](https://agentmods.dev/commands/thebeardedbearsas/claude-craft/generate-component)
Your own site
<a href="https://agentmods.dev/commands/thebeardedbearsas/claude-craft/generate-component"><img src="https://agentmods.dev/badge/commands/thebeardedbearsas/claude-craft/generate-component.svg" alt="Measured on agentmods" height="20"></a>
Per session 6 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,165 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.00006 $0.01165
Opus 5 $0.00003 $0.00583
Sonnet 5 $0.00001 $0.00233
Haiku 4.5 $0.00001 $0.00117

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

Security

Grade A, and why

generate-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 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/angular/generate-component.md · 221 lines

How it starts

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

Generate Angular Component

Generate a complete Angular standalone component with tests and proper structure.

Arguments

$ARGUMENTS

  • component-name: Name of the component (e.g., "user-card", "data-table")
  • feature (optional): Feature folder (e.g., "users", "dashboard")

What This Command Generates

  1. Component file ({name}.component.ts)
  2. Template file ({name}.component.html)
  3. Styles file ({name}.component.scss)
  4. Test file ({name}.component.spec.ts)
  5. Index file (index.ts)

Generated Structure

src/app/features/{feature}/components/{name}/
├── {name}.component.ts
├── {name}.component.html
├── {name}.component.scss
├── {name}.component.spec.ts
└── index.ts

Component Template

// {name}.component.ts
import {
  Component,
  ChangeDetectionStrategy,
  input,
  output,
  computed,
  signal
} from '@angular/core';
import { CommonModule } from '@angular/common';

@Component({
  selector: 'app-{name}',
  standalone: true,
  imports: [CommonModule],
  templateUrl: './{name}.component.html',
  styleUrl: './{name}.component.scss',
  changeDetection: ChangeDetectionStrategy.OnPush
})
export class {PascalName}Component {
  // Inputs
  // data = input.required<DataType>();
  // optional = input<string>('default');

  // Outputs
  // action = output<void>();

  // Internal state
  // loading = signal(false);

  // Computed
  // derived = computed(() => this.data().property);

  // Event handlers
  // onAction(): void {
  //   this.action.emit();
  // }
}

Template File

<!-- {name}.component.html -->
<div class="{name}">
  <!-- Component content -->
</div>

Styles File

// {name}.component.scss
.{name} {
  // Component styles
}

Test Template

// {name}.component.spec.ts
import { ComponentFixture, TestBed } from '@angular/core/testing';
import { {PascalName}Component } from './{name}.component';

describe('{PascalName}Component', () => {
  let component: {PascalName}Component;
  let fixture: ComponentFixture<{PascalName}Component>;

  beforeEach(async () => {
    await TestBed.configureTestingModule({
      imports: [{PascalName}Component]
    }).compileComponents();

    fixture = TestBed.createComponent({PascalName}Component);
    component = fixture.componentInstance;
  });

  it('should create', () => {
    expect(component).toBeTruthy();
  });

  describe('rendering', () => {
    it('should render component', () => {
      fixture.detectChanges();
      const element = fixture.nativeElement;
      expect(element.querySelector('.{name}')).toBeTruthy();
    });
  });

  describe('inputs', () => {
    // Add input tests here
  });

  describe('outputs', () => {
    // Add output tests here
  });

  describe('interactions', () => {
    // Add interaction tests here
  });
});

Read the full file on GitHub · 221 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 · 221 lines · 6 tokens per session scan A f698900370a9

Subscribe to this mod's changes

generate-component is a command published in the GitHub repository TheBeardedBearSAS/claude-craft (105 stars, last pushed 3d ago), licensed MIT. It adds 6 tokens to every session and 1,165 once invoked, about $0.0000 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-30.