Borrowing it
Nothing to install: this file belongs to RoboFinSystems/robosystems. 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/RoboFinSystems/robosystems/main/.claude/commands/deploy.mdgit clone --depth 1 https://github.com/RoboFinSystems/robosystemsWrote 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/robofinsystems/robosystems/deploy)<a href="https://agentmods.dev/commands/robofinsystems/robosystems/deploy"><img src="https://agentmods.dev/badge/commands/robofinsystems/robosystems/deploy/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/robofinsystems/robosystems/deploy"><img src="https://agentmods.dev/badge/commands/robofinsystems/robosystems/deploy.svg" alt="Reviewed on agentmods" width="80" 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.00018 | $0.01347 |
| Opus 5.5 | $0.00007 | $0.00539 |
| Sonnet 5.5 | $0.00004 | $0.00269 |
| Haiku 4.5 | $0.00002 | $0.00135 |
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 1mo 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 -sf https://<api-host>/v1/status && echo OK # public API over HTTPS How it starts
The opening of the file, as written. The whole thing — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Monitor a deployment run — pinpoint why it failed, drive it to green on a re-run, and verify health. Deploys go through GitHub Actions (workflow_dispatch); this skill is about watching and diagnosing them, not replacing the pipeline. Pairs with the deployment-monitoring runbook in local/RoboSystems/runbooks/ for account-specific stack names and failure classes — read it alongside this file.
When this runs
Most deploys (~95%) go green untouched and need no attention. The real use case is the other 5%: a deploy failed, and you're re-running it and want eyes on this one. Optimize for that — get to the failing job fast, classify it, fix the cause, re-trigger, and confirm the app is healthy afterward.
Scope & guardrails
ghreads are free; the deploy trigger is not. Reading runs, jobs, and logs (gh run list/view/watch) needs no confirmation. Triggering or re-triggering a deploy (gh workflow run,just deploy) is an outward-facing action — confirm the target (env + ref) with the user first, and default to watching a run they already started.- AWS is read-only here.
describe-*/list-*only. CloudFormation changes and stack deletions are the user's to run — nevercreate-stack/update-stack/delete-stackdirectly. - Never deploy the default branch to prod. Production should ride a version tag / release branch produced by the release workflow. Verify the ref before triggering rather than assuming the pipeline will reject a bad one, and when reviewing history (
gh run list --json headBranch,displayTitle), flag any past prod run that rode a branch rather than a tag. just deploydefaults are dangerous if you're not explicit. The recipe defaults to the prod environment and the current branch. Always pass both arguments.- Output can be sensitive. Failure logs name internal hostnames, stack names, and resource IDs. Don't paste raw infra detail into anything public; summarize.
1. Find the run
Identify env (staging | prod) and which run you're looking at. If the user didn't say, ask or infer from context.
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.
- 1mo ago Changed b86d8fb16ebf
- 1mo ago First seen · 73 lines · 18 tokens per session scan A 366a141d527d
deploy is a command published in the GitHub repository RoboFinSystems/robosystems (29 stars, last pushed today), licensed Apache-2.0. It adds 18 tokens to every session and 1,347 once invoked, about $0.0001 per session on Opus 5.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 commands, from other repositories
tools
Manage MCP tools with natural language commands to list, enable, and disable tools and tool groups.
rclone_deletefile
Remove a single file from remote.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.