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/setup-functions)<a href="https://agentmods.dev/commands/rohitg00/awesome-claude-code-toolkit/setup-functions"><img src="https://agentmods.dev/badge/commands/rohitg00/awesome-claude-code-toolkit/setup-functions/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/setup-functions"><img src="https://agentmods.dev/badge/commands/rohitg00/awesome-claude-code-toolkit/setup-functions.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.00011 | $0.00320 |
| Opus 5.5 | $0.00004 | $0.00128 |
| Sonnet 5.5 | $0.00002 | $0.00064 |
| Haiku 4.5 | $0.00001 | $0.00032 |
Grade A, and why
setup-functions 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
/setup-functions - Setup Azure Functions
Configure and deploy an Azure Functions application.
Steps
- Ask the user for the function name, runtime (.NET, Node.js, Python, Java), and trigger type
- Initialize the function app project with the appropriate runtime template
- Create the function handler with the selected trigger binding
- Configure app settings and connection strings for the function
- Set up the hosting plan: Consumption (serverless), Premium, or Dedicated
- Configure authentication and authorization if the function exposes HTTP endpoints
- Set up managed identity for accessing Azure resources without credentials
- Configure Application Insights for monitoring and logging
- Set up input and output bindings: Blob Storage, Queue, Cosmos DB, Event Hub
- Create the deployment configuration: Azure DevOps pipeline or GitHub Actions
- Generate the ARM template or Bicep file for infrastructure as code
- Document: function URL, trigger type, bindings, app settings, scaling behavior
Rules
- Use Consumption plan for event-driven workloads to minimize costs
- Always configure Application Insights for production functions
- Use managed identities instead of connection strings for Azure resource access
- Set function timeout appropriate to the workload (Consumption max: 10 min)
- Configure CORS settings for HTTP-triggered functions called from browsers
- Enable deployment slots for production functions to support zero-downtime deploys
- Store secrets in Azure Key Vault, reference them via app settings
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 · 34 lines · 11 tokens per session scan A f8ee43dd00aa
setup-functions 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 adds 11 tokens to every session and 320 once invoked, about $0.0000 per session on Opus 5.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
rclone_mkdir
Make the path if it doesn't already exist.
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.
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.