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.
npx agentmods add commands/appwrite/cursor-plugin/deploy-sitegit clone --depth 1 https://github.com/appwrite/cursor-pluginWhat 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 | $0.00011 | $0.00984 |
| Opus 5 | $0.00005 | $0.00492 |
| Sonnet 5 | $0.00002 | $0.00197 |
| Haiku 4.5 | $0.00001 | $0.00098 |
Grade A, and why
deploy-site 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.
This is a copy
97% identical to deploy-site — 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.
How it starts
The opening of the file, as written. The whole thing — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deploy a site 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 sites
Full Workflow
1. Initialize a new site
appwrite init sites
2. Pull existing sites from Console
appwrite pull sites
3. Configuration
Sites are configured in appwrite.config.json:
{
"projectId": "<PROJECT_ID>",
"endpoint": "https://<REGION>.cloud.appwrite.io/v1",
"sites": [
{
"$id": "<SITE_ID>",
"name": "My Site",
"enabled": true,
"logging": true,
"framework": "astro",
"timeout": 30,
"installCommand": "npm install",
"buildCommand": "npm run build",
"outputDirectory": "./dist",
"specification": "s-1vcpu-512mb",
"buildRuntime": "node-22",
"adapter": "ssr",
"fallbackFile": "",
"path": "sites/my-site"
}
]
}
4. Deploy
appwrite push sites
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 sites
appwrite push sites --all --force
# Push a specific site
appwrite push sites --site-id <SITE_ID> --force
Site Management Commands
| Command | Description |
|---|---|
appwrite sites list |
List all sites in the project |
appwrite sites create |
Create a new site |
appwrite sites get --site-id <ID> |
Get a site by ID |
appwrite sites update --site-id <ID> |
Update a site |
appwrite sites delete --site-id <ID> |
Delete a site |
appwrite sites list-frameworks |
List available frameworks |
appwrite sites list-specifications |
List allowed site specifications |
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.
- yesterday First seen · 139 lines · 11 tokens per session scan A 6fd4cc1c9396
deploy-site 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 984 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-site, differing in 1 line, and is treated as a copy.
Other commands, from other repositories
migrate
Command "migrate" from chohra-med/expo_boilerplate, covering invocation, steps and rule.
cost-tracker
Track session costs, understand token spend, and get optimization tips.
lians-recall
Recall current (non-stale) facts from Lians memory, optionally as-of a past date.
t800-onboard
Для чата с новичками. Показывает, что настроено в Cursor (global + local), и что умеет отдел T-800.
scorecard
Run a repeatable weekly health check. Score Brain OS out of 100. Compare week-over-week.
dev-planner
Generate or update DEV-PLAN.md with phased development plan from Product-Spec.md.