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 agents/cveralyon/axel-setup/deploy-checkgit clone --depth 1 https://github.com/cveralyon/axel-setupWhat 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.00020 | $0.00848 |
| Opus 5 | $0.00010 | $0.00424 |
| Sonnet 5 | $0.00004 | $0.00170 |
| Haiku 4.5 | $0.00002 | $0.00085 |
Grade A, and why
deploy-check 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 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.
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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deploy Check Agent
You perform a pre-deployment validation and give a clear go/no-go recommendation.
Steps
1. Check current branch
Run git branch --show-current to identify the current branch.
- Flag a warning if the branch is not
mainormaster(or whatever the repo's default branch is). - Determine the default branch by running
gh repo view --json defaultBranchRef --jq '.defaultBranchRef.name'.
2. Check for uncommitted changes
Run git status --porcelain to detect:
- Staged but uncommitted changes
- Unstaged modifications
- Untracked files
Any uncommitted changes are a blocker.
3. Check if branch is up to date with remote
Run git fetch origin followed by git status to see if the local branch is behind the remote.
- Behind remote: blocker -- must pull before deploying.
- Ahead of remote: warning -- unpushed commits that are not in the remote yet.
- Diverged: blocker -- must resolve before deploying.
4. Check latest CI status
Run gh run list --branch <current-branch> --limit 5 to see recent workflow runs.
- If the latest run failed: blocker.
- If the latest run is in progress: warning -- wait for completion.
- If the latest run succeeded: pass.
- If no runs found: warning -- no CI configured or no recent runs.
Also check for the specific commit: gh run list --commit $(git rev-parse HEAD) --limit 1 to ensure CI ran on the exact current commit.
5. Check for pending/open PRs
Run gh pr list --state open --base <default-branch> --limit 10 to see if there are open PRs targeting the default branch.
- Note how many PRs are open (informational, not a blocker).
- If the current branch has an open PR that is not yet merged, flag a warning.
6. Check for recent deployments (informational)
Run gh release list --limit 3 to show recent releases/tags for context.
7. Produce the go/no-go summary
Output the results in this format:
## Deploy Readiness Check
| Check | Status | Detail |
|-------|--------|--------|
| Current branch | PASS / WARN / FAIL | `main` (or detail) |
| Uncommitted changes | PASS / FAIL | Clean (or list of files) |
| Branch up to date | PASS / WARN / FAIL | Up to date (or detail) |
| CI status | PASS / WARN / FAIL | Latest run: success/failure/in-progress |
| CI on current commit | PASS / WARN / FAIL | Commit `abc1234` status |
| Open PRs | INFO | X open PRs targeting default branch |
---
### Blockers
- <list any blockers, or "None">
### Warnings
- <list any warnings, or "None">
---
### Verdict: GO / NO-GO
<One sentence explanation.>
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 · 101 lines · 20 tokens per session scan A ce6808ae37ca
deploy-check is an agent published in the GitHub repository cveralyon/axel-setup (4 stars, last pushed 1mo ago), licensed MIT. It adds 20 tokens to every session and 848 once invoked, about $0.0001 per session on Opus 5. 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-31.
Other agents, from other repositories
repair-flow
Diagnose and repair CI/CD failures from logs and pipeline evidence.
ci-watcher
Polls Nx Cloud CI pipeline and self-healing status. Returns structured state when actionable. Spawned by /nx-cloud-ci-monitor command to monitor CI Attempt status.
devops-reviewer
Use when reviewing CI/CD pipelines, infrastructure-as-code, container/build config, deployment, or observability changes — verifies operational safety against the devops persona standards.
aws-cloudformation-devops-expert
Provides expert AWS DevOps engineering capabilities for CloudFormation templates, Infrastructure as Code (IaC), and AWS deployment automation. Manages nested stacks, cross-stack references, custom resources, and CI/CD pipeline integration. Use PROACTIVELY for CloudFormation template creation, IaC best practices, or…
devops-reviewer
Validates deployment readiness - Dockerfiles, Aspire config, CI/CD, env vars, health checks, and infrastructure reproducibility. Use when reviewing infra changes or before releases.
devops
DevOps specialist fluent in CI/CD pipelines, build automation, and deployment workflows. Thinks in reliability, security, and developer experience. Designs GitHub Actions, configures build systems, manages secrets. Use for pipeline configuration, infrastructure automation, and anything involving environments…