Awesome Claude Code Toolkit is a curated collection of extensions and configuration for Claude Code, including agents, skills, commands, plugins, hooks, rules, templates, MCP configurations, and companion apps. It is for Claude Code users who want ready-made workflows and integrations for different development tasks. The catalogue add-ons are selected components from this toolkit.
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/rohitg00/awesome-claude-code-toolkitWrote 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/rohitg00/awesome-claude-code-toolkit/create-view)<a href="https://agentmods.dev/commands/rohitg00/awesome-claude-code-toolkit/create-view"><img src="https://agentmods.dev/badge/commands/rohitg00/awesome-claude-code-toolkit/create-view/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/rohitg00/awesome-claude-code-toolkit/create-view"><img src="https://agentmods.dev/badge/commands/rohitg00/awesome-claude-code-toolkit/create-view.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.00306 |
| Opus 5.5 | $0.00000 | $0.00122 |
| Sonnet 5.5 | $0.00000 | $0.00061 |
| Haiku 4.5 | $0.00000 | $0.00031 |
Grade A, and why
create-view 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.
What it actually says
/create-view - Create SwiftUI View
Generate a SwiftUI view with proper architecture and best practices.
Steps
- Ask the user for the view name, purpose, and data requirements
- Determine the view type: screen (full page), component (reusable), or sheet (modal)
- Create the SwiftUI view file with the appropriate structure
- Add @State, @Binding, @ObservedObject, or @EnvironmentObject properties as needed
- Implement the view body with proper layout: VStack, HStack, ZStack, List, or Grid
- Add navigation elements: NavigationLink, sheet, alert, or confirmationDialog
- Include loading, empty, and error states with appropriate UI
- Add accessibility modifiers: accessibilityLabel, accessibilityHint, accessibilityValue
- Implement dark mode support with proper color assets
- Create a PreviewProvider with multiple preview configurations
- Add the view to the navigation flow in the appropriate coordinator or router
- Document the view's purpose, parameters, and usage examples
Rules
- Follow MVVM architecture: views should not contain business logic
- Use @StateObject for owned data, @ObservedObject for injected data
- Keep views small; extract subviews for sections over 30 lines
- Use SF Symbols for icons instead of custom assets when available
- Support Dynamic Type for all text elements
- Add proper keyboard handling for form views
- Use the project's design system colors and typography
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 57dffefc12c6
create-view is a command published in the GitHub repository rohitg00/awesome-claude-code-toolkit (2,717 stars, last pushed 5mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 306 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-09-03.
Other commands, from other repositories
mobile
Start mobile design workflow.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.