Borrowing it
Nothing to install: this file belongs to namastexlabs/automagik-tools. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/namastexlabs/automagik-tools/main/.claude/commands/deployer.mdgit clone --depth 1 https://github.com/namastexlabs/automagik-toolsWrote 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/namastexlabs/automagik-tools/deployer)<a href="https://agentmods.dev/commands/namastexlabs/automagik-tools/deployer"><img src="https://agentmods.dev/badge/commands/namastexlabs/automagik-tools/deployer.svg" alt="Measured on agentmods" 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.00000 | $0.02721 |
| Opus 5 | $0.00000 | $0.01360 |
| Sonnet 5 | $0.00000 | $0.00544 |
| Haiku 4.5 | $0.00000 | $0.00272 |
Grade A, and why
deployer 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 7d 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.
How it starts
The opening of the file, as written. The whole thing — 421 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DEPLOYER - Package & Deploy Workflow
🚀 Your Mission
You are the DEPLOYER workflow for automagik-tools. Your role is to package, configure, and deploy validated MCP tools for production use.
🎯 Core Responsibilities
1. Package Preparation
- Update version numbers
- Build distribution packages
- Create Docker images
- Generate MCP configurations
- Prepare release notes
2. Deployment Options
- PyPI/TestPyPI publishing
- Docker container deployment
- Local installation
- Cloud deployment configs
- MCP server configurations
3. Documentation
- Update main README
- Create MCP config examples
- Generate changelog entries
- Update tool listing
- Create installation guides
🚀 Simplified Deployment Process (CORRECT)
The automagik-tools project has streamlined deployment. The process is:
Step 1: Pre-Deployment Checks
# Verify validation completed
validation_report = Read("docs/qa/validation-{tool_name}.md")
if "READY" not in validation_report:
raise Exception("Tool not validated for production")
# Check git status and stage files
Bash("git status")
Bash("git add automagik_tools/tools/{tool_name}/")
Bash("git add tests/tools/test_{tool_name}.py")
Bash("git add docs/qa/validation-{tool_name}.md")
Bash("git add scripts/*{tool_name}*.py")
Bash("git add .env.example")
Bash("git commit -m 'feat: add {tool_name} MCP tool'")
Step 2: Version Bump & Commit
# Read current version from pyproject.toml
current_version = Read("pyproject.toml") # Extract version = "X.Y.Z"
# For new tool: bump minor version (0.3.10 -> 0.4.0)
# For updates: bump patch version (0.4.0 -> 0.4.1)
Edit("pyproject.toml", old_string='version = "{current}"', new_string='version = "{new}"')
# Commit version bump
Bash("git add pyproject.toml")
Bash("git commit -m 'bump: version {new_version}'")
Bash("git push origin main")
Step 3: Direct PyPI Deployment
# The project uses make publish which handles:
# 1. make clean (removes old dist/)
# 2. make build (builds wheel and sdist)
# 3. twine upload to PyPI
Bash("make publish")
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.
- 7d ago First seen · 421 lines · 0 tokens per session scan A ce81a37bcf78
deployer is a command published in the GitHub repository namastexlabs/automagik-tools (15 stars, last pushed 9mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 2,721 tokens. 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
cloudflare-api
Hit the Cloudflare REST API for bulk, fleet, and operations wrangler can't do.
d1-migration
Run D1 migration workflow — generate, inspect, apply.
cloudflare-worker-builder
Scaffold and deploy a Cloudflare Worker with Hono routing.
vite-flare-starter
Scaffold a full-stack Cloudflare app from vite-flare-starter.
monitoring-setup.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.
tunnel-start.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.