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.
git clone --depth 1 https://github.com/Justdvp/claude-code-templatesWrote 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/justdvp/claude-code-templates/component)<a href="https://agentmods.dev/commands/justdvp/claude-code-templates/component"><img src="https://agentmods.dev/badge/commands/justdvp/claude-code-templates/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.
<a href="https://agentmods.dev/commands/justdvp/claude-code-templates/component"><img src="https://agentmods.dev/badge/commands/justdvp/claude-code-templates/component.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.00258 |
| Opus 5.5 | $0.00000 | $0.00103 |
| Sonnet 5.5 | $0.00000 | $0.00052 |
| Haiku 4.5 | $0.00000 | $0.00026 |
Grade A, and why
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- component — 100% identical, 0 lines differ
What it actually says
React Component Generator
Create a React component named $ARGUMENTS following project conventions.
Steps
- Analyze project structure: Check existing components to understand file organization, naming conventions, and patterns
- Examine styling approach: Identify CSS/SCSS modules, styled-components, Tailwind, or other styling methods used
- Review testing patterns: Check existing test files to understand testing framework and conventions
- Create component structure: Generate appropriate files (component, styles, tests, index)
- Implement component: Write TypeScript/JavaScript with proper props interface and logic
- Add tests: Write comprehensive tests following project patterns
- Verify integration: Ensure component works with existing project setup
Requirements
- Follow existing project file structure and naming conventions
- Use TypeScript if project uses it
- Include proper accessibility attributes
- Add responsive design considerations
- Write tests that match project testing patterns
- Include usage examples in component documentation
Important Notes
- ALWAYS examine existing components first to understand project patterns
- Use the same styling approach as the rest of the project
- Follow the project's TypeScript conventions for props and interfaces
- Don't install new dependencies without asking first
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.
- 1mo ago First seen · 29 lines · 0 tokens per session scan A 00b1118fdcbd
component is a command published in the GitHub repository Justdvp/claude-code-templates (7 stars, last pushed 5d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 258 tokens. 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.
Other commands, from other repositories
scaffold-desktop
Scaffold a desktop application using Electron or Tauri with proper project structure.
fdk-react-create
Create a new Platform 3.0 React Meta app (default UI stack). Uses fdk create react-starter-template or react-meta skeletons with DEW components, metaConfig in manifest.json, and React Router.
fe
Invoke Frontend Developer for React, TypeScript, Next.js, and React Native development.
audit-steps
Audit one or all pipelines against layout, frontmatter, topology, and runtime-safety standards — produces a severity-classified report (SEV-0/1/2/3) with cited evidence.
delete-step
Delete a step from an existing pipeline — select pipeline, select step, perform gap analysis, optionally rewire, audit the delta, then gate on human approval before any deletion.
init-deep
Initiates a repository traversal to create localized PIPELINE-CONTEXT.md hierarchical context files.