deploy-function

A command for publishing a server-side function through the Appwrite command-line tool. It uses the project configuration to deploy the function and its settings.

In plain words
What is it for?
Creating or pulling Appwrite functions, configuring runtimes and environment values, and deploying them with the Appwrite CLI.
Why use it?
It avoids manually copying function code and configuration into Appwrite. It also supports repeatable deployments from scripts or automated build systems.

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/appwrite/cursor-plugin/deploy-function
Clone the repo
git clone --depth 1 https://github.com/appwrite/cursor-plugin
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 1,008 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 97% 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 $0.00011 $0.01008
Opus 5 $0.00005 $0.00504
Sonnet 5 $0.00002 $0.00202
Haiku 4.5 $0.00001 $0.00101

Measured yesterday against content hash 8f6bd4dbe65b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

deploy-function 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 yesterday.

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

97% identical to deploy-function — 1 line 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.

commands/deploy-function.md · 154 lines

How it starts

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

Deploy a function using the Appwrite CLI

Prerequisites

  • Appwrite CLI installed (npm install -g appwrite-cli)
  • Authenticated with appwrite login
  • Project initialized with appwrite init

Quick Deploy

appwrite push functions

Full Workflow

1. Initialize a new function

appwrite init functions

This scaffolds a new function with a starter template and adds it to appwrite.config.json.

2. Pull existing functions from Console

appwrite pull functions

3. Configuration

Functions are configured in appwrite.config.json:

{
    "projectId": "<PROJECT_ID>",
    "endpoint": "https://<REGION>.cloud.appwrite.io/v1",
    "functions": [
        {
            "$id": "<FUNCTION_ID>",
            "name": "userAuth",
            "enabled": true,
            "live": true,
            "logging": true,
            "runtime": "node-18.0",
            "deployment": "<DEPLOYMENT_ID>",
            "vars": [],
            "events": [],
            "schedule": "",
            "timeout": 15,
            "entrypoint": "userAuth.js",
            "commands": "npm install",
            "version": "v3",
            "path": "functions/userAuth"
        }
    ]
}

4. Deploy

appwrite push functions

CI/CD (Non-Interactive)

Set up headless mode first:

appwrite client \
    --endpoint https://<REGION>.cloud.appwrite.io/v1 \
    --project-id <PROJECT_ID> \
    --key <API_KEY>

Then deploy non-interactively:

# Push all functions
appwrite push functions --all --force

# Push a specific function
appwrite push functions --function-id <FUNCTION_ID> --force

# Push all resources at once (functions, tables, buckets, teams, topics)
appwrite push all --all --force

Function Management Commands

Command Description
appwrite functions list List all functions in the project
appwrite functions create Create a new function
appwrite functions get --function-id <ID> Get a function by ID
appwrite functions update --function-id <ID> Update a function
appwrite functions delete --function-id <ID> Delete a function
appwrite functions list-runtimes List all active runtimes

Read the full file on GitHub · 154 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. yesterday First seen · 154 lines · 11 tokens per session scan A 8f6bd4dbe65b

Subscribe to this mod's changes

deploy-function is a command published in the GitHub repository appwrite/cursor-plugin (9 stars, last pushed 1mo ago), licensed BSD-3-Clause. It adds 11 tokens to every session and 1,008 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to deploy-function, differing in 1 line, and is treated as a copy.