setup-functions

A command that configures and deploys an Azure Functions application, which runs small pieces of code in response to events or requests.

In plain words
What is it for?
Use it to create function handlers, configure HTTP or event triggers and service bindings, set up authentication and managed access, and prepare Azure deployment files.
Why use it?
It turns the many setup choices—runtime, triggers, hosting, settings, monitoring, and deployment—into a documented configuration workflow.

Command

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.

agentmods
npx agentmods add commands/rohitg00/awesome-claude-code-toolkit/setup-functions
Clone the repo
git clone --depth 1 https://github.com/rohitg00/awesome-claude-code-toolkit
Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 320 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found 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 $0.00011 $0.00320
Opus 5 $0.00005 $0.00160
Sonnet 5 $0.00002 $0.00064
Haiku 4.5 $0.00001 $0.00032

Measured 3d ago against content hash f8ee43dd00aa, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 3d 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.

plugins/azure-helper/commands/setup-functions.md · 34 lines

What it actually says

/setup-functions - Setup Azure Functions

Configure and deploy an Azure Functions application.

Steps

  1. Ask the user for the function name, runtime (.NET, Node.js, Python, Java), and trigger type
  2. Initialize the function app project with the appropriate runtime template
  3. Create the function handler with the selected trigger binding
  4. Configure app settings and connection strings for the function
  5. Set up the hosting plan: Consumption (serverless), Premium, or Dedicated
  6. Configure authentication and authorization if the function exposes HTTP endpoints
  7. Set up managed identity for accessing Azure resources without credentials
  8. Configure Application Insights for monitoring and logging
  9. Set up input and output bindings: Blob Storage, Queue, Cosmos DB, Event Hub
  10. Create the deployment configuration: Azure DevOps pipeline or GitHub Actions
  11. Generate the ARM template or Bicep file for infrastructure as code
  12. 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
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. 3d ago First seen · 34 lines · 11 tokens per session scan A f8ee43dd00aa

Subscribe to this mod's changes

setup-functions is a command published in the GitHub repository rohitg00/awesome-claude-code-toolkit (2,578 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 11 tokens to every session and 320 once invoked, about $0.0001 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.