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 skills/floomhq/moto/deploynpx skills add floomhq/moto --skill deploygit clone --depth 1 https://github.com/floomhq/motoWhat 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.00062 | $0.00431 |
| Opus 5 | $0.00031 | $0.00216 |
| Sonnet 5 | $0.00012 | $0.00086 |
| Haiku 4.5 | $0.00006 | $0.00043 |
Grade A, and why
deploy scanned grade A with 1 finding 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 2d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s -X POST "https://api.render.com/v1/services/<SERVICE_ID>/deploys" \ What it actually says
Deploy Skill
Step 1: Identify the project
Determine which project to deploy from cwd or user's message. If ambiguous, ask.
Step 2: Identify the platform
Common deployment targets:
Vercel (frontend)
# Auto-deploy via git push
git push origin main # or preview/production branch
# Manual deploy
vercel --token $VERCEL_TOKEN
Render (backend)
# Trigger deploy via API
curl -s -X POST "https://api.render.com/v1/services/<SERVICE_ID>/deploys" \
-H "Authorization: Bearer $RENDER_API_KEY" \
-H "Content-Type: application/json" \
-d '{"clearCache":"clear"}'
Docker (self-hosted)
# Rebuild and restart container
docker compose build && docker compose up -d
# Or just restart
docker restart <container_name>
Supabase Edge Functions
supabase functions deploy <function-name>
Pre-deploy checklist
- Run
git diffto review what's being deployed - Run build locally:
npm run buildor equivalent - Run tests if they exist
- Check for uncommitted
.envchanges (never commit secrets)
Post-deploy verification
- Check the live URL loads correctly
- For API backends: hit the health endpoint (
/api/health) - Check deploy logs for errors
- Verify key functionality works end-to-end
Project-specific notes
Check CLAUDE.md in the project root for project-specific deploy steps, branch strategies, and gotchas.
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.
- 2d ago First seen · 69 lines · 62 tokens per session scan A 7ebbeb77181a
deploy is a skill published in the GitHub repository floomhq/moto (32 stars, last pushed 2mo ago), licensed MIT. It adds 62 tokens to every session and 431 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
rulesync
Generates and syncs AI rule configuration files (.cursorrules, CLAUDE.md, copilot-instructions.md) across 20+ coding tools from a single source. Use when syncing AI rules, running rulesync commands, importing or generating rule files, or managing shared AI coding configurations.
establishing-project-context
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.
autoprompt
Explicit-only useful-first orchestration. Invoke /autoprompt to turn a mission into one executable roadmap, build dependency-safe lanes, and verify the result with independent reviewers. Never infer invocation from ordinary requests. Never resume from leftover artifacts without an explicit resume instruction.
office-hours
YC Office Hours — two modes. Startup mode: six forcing questions that expose demand reality, status quo, desperate specificity, narrowest wedge, observation, and future-fit. Builder mode: design thinking brainstorming for side projects, hackathons, learning, and open source. Saves a design doc. Use when asked to…
memstack-business-gdpr
Use this skill when the user says 'GDPR', 'data protection', 'privacy compliance', 'DPA', 'DSAR', 'data subject request', 'cookie consent', 'privacy audit', 'CCPA', or asks 'do I need GDPR for this repo'. Scans the repository to detect what personal data is collected, classifies sensitivity, determines whether GDPR…
echo
Use when the user references past sessions, asks 'what did we do', 'do you remember', 'last session', 'recall', or 'continue from'.