components

components is a command for Claude Code from swesmith/davila7__claude-code-templates.734b8a50. It costs 0 tokens per session (619 once invoked), scanned A, a copy of components, MIT.

An Angular component generator that studies a project’s structure and conventions before creating a component, template, styles, inputs, outputs, and tests.

In plain words
What is it for?
Use it to create presentation, container, feature, shared, user-interface, or layout components in Angular.
Why use it?
It reduces repetitive setup and helps new components fit the project’s existing organization and TypeScript patterns.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

Good fit Use it to create presentation, container, feature, shared, user-interface, or layout components…

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/swesmith/davila7__claude-code-templates.734b8a50/components
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.

Clone the repo
git clone --depth 1 https://github.com/swesmith/davila7__claude-code-templates.734b8a50

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 components

README.md
[![agentmods](https://agentmods.dev/badge/commands/swesmith/davila7__claude-code-templates.734b8a50/components.svg)](https://agentmods.dev/commands/swesmith/davila7__claude-code-templates.734b8a50/components)
Your own site
<a href="https://agentmods.dev/commands/swesmith/davila7__claude-code-templates.734b8a50/components"><img src="https://agentmods.dev/badge/commands/swesmith/davila7__claude-code-templates.734b8a50/components.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 619 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 100% copy Near-identical to another mod 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.00000 $0.00619
Opus 5 $0.00000 $0.00309
Sonnet 5 $0.00000 $0.00124
Haiku 4.5 $0.00000 $0.00062

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

Security

Grade A, and why

components 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.

Origin

This is a copy

100% identical to components — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

cli-tool/templates/javascript-typescript/examples/angular-app/.claude/commands/components.md · 63 lines

How it starts

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

Angular Components

Create Angular components for $ARGUMENTS following project conventions.

Task

Create or optimize Angular components based on the requirements:

  1. Analyze existing components: Check current component patterns, naming conventions, and folder organization
  2. Examine Angular setup: Review project structure, module organization, and TypeScript configuration
  3. Identify component type: Determine the component category:
    • Presentation components (dumb/pure components)
    • Container components (smart components with state)
    • Feature components (business logic components)
    • Shared/UI components (reusable across features)
    • Layout components (structural components)
  4. Check dependencies: Review existing components and shared modules to avoid duplication
  5. Implement component: Create component with proper TypeScript types and lifecycle hooks
  6. Add inputs/outputs: Define @Input and @Output properties with proper typing
  7. Create template: Build HTML template with proper Angular directives and bindings
  8. Add styles: Implement component styles following project's styling approach
  9. Create tests: Write comprehensive unit tests with TestBed and proper mocking
  10. Update module: Register component in appropriate Angular module

Implementation Requirements

  • Follow project's Angular architecture and naming conventions
  • Use proper component lifecycle hooks (OnInit, OnDestroy, etc.)
  • Include comprehensive TypeScript interfaces for inputs and outputs
  • Implement proper change detection strategy (OnPush when possible)
  • Add proper subscription management with takeUntil or async pipe
  • Follow Angular style guide and project coding standards
  • Consider component performance and memory management

Component Patterns to Consider

Based on the request:

  • Smart Components: Container components that manage state and services
  • Dumb Components: Presentation components that only receive inputs
  • Feature Components: Components specific to business features
  • Shared Components: Reusable UI components across the application
  • Form Components: Reactive forms with validation and custom controls
  • Data Display: Components for tables, lists, cards with proper data binding

Read the full file on GitHub · 63 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 · 63 lines · 0 tokens per session scan A bea8d1c5ecab

Subscribe to this mod's changes

components is a command published in the GitHub repository swesmith/davila7__claude-code-templates.734b8a50 (2 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 619 tokens. A static security scan graded it A with 0 findings. It is 100% identical to components, differing in 0 lines, and is treated as a copy.