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 agentmods add commands/thebeardedbearsas/claude-craft/generate-componentgit clone --depth 1 https://github.com/TheBeardedBearSAS/claude-craftWrote 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/thebeardedbearsas/claude-craft/generate-component)<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>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.00006 | $0.01165 |
| Opus 5 | $0.00003 | $0.00583 |
| Sonnet 5 | $0.00001 | $0.00233 |
| Haiku 4.5 | $0.00001 | $0.00117 |
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.
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
- Component file (
{name}.component.ts) - Template file (
{name}.component.html) - Styles file (
{name}.component.scss) - Test file (
{name}.component.spec.ts) - 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
});
});
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.
- 6d ago First seen · 221 lines · 6 tokens per session scan A f698900370a9
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.
Other commands, from other repositories
test-suite
Run comprehensive test suite with coverage analysis.
assemble-team
Assemble a pre-built agent team for parallel work - review, feature, debug, cross-platform, full-stack, or research.
standardize-claude-md
Add missing toolkit sections (Related Global Rules, Quick Start) to existing CLAUDE.md.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.