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/mountainunicorn/add/deploynpx skills add MountainUnicorn/add --skill deploygit clone --depth 1 https://github.com/MountainUnicorn/addWhat 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.00016 | $0.04496 |
| Opus 5 | $0.00008 | $0.02248 |
| Sonnet 5 | $0.00003 | $0.00899 |
| Haiku 4.5 | $0.00002 | $0.00450 |
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 https://api.example.com/health How it starts
The opening of the file, as written. The whole thing — 558 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ADD Deploy Skill v{{VERSION}}
Execute environment-aware deployment: commit changes, push to remote, trigger CI/CD, and verify successful deployment.
Overview
The Deploy skill orchestrates the final step of the development workflow:
- Commit — Stage and commit code changes with traceability
- Push — Push to remote repository and branch
- CI/CD — Trigger or monitor CI pipeline
- Verify — Confirm deployment success and run smoke tests
The skill is environment-aware: deployment to production is gated with additional safety checks and requires human approval.
Deployment flows:
- Local: Commit only (no push)
- Dev: Commit → Push → Optional CI
- Staging: Commit → Push → CI required → Verify
- Production: Commit → Push → CI required → Gated approval → Verify smoke tests
Pre-Flight Checks
-
Verify code quality
- Run /add:verify --level deploy (unless --skip-verify)
- Halt if quality gates fail
- Ensure all tests passing
-
Load configuration
- Read .add/config.json
- Extract deployment settings:
- ci.enabled (true/false)
- ci.provider (github, gitlab, circleci, etc.)
- environments: dev, staging, production configs
- deployment.strategy (direct, blue-green, canary)
- Load credential/auth settings
-
Verify git repository
- Confirm working directory is a git repo
- Check git is configured (user.name, user.email)
- Verify branch protection rules won't block merge
-
Determine environment
- Use --env flag or prompt user
- Default: staging (safe default)
- Validate environment exists in config
-
Check for uncommitted changes
- Run
git status - Verify all relevant changes are staged
- Halt if unintended changes exist
- Ask user to review staged changes
- Run
-
Verify feature branch
- Confirm on feature branch (not main/master)
- For production, branch should be up-to-date with main
- For dev, any branch acceptable
-
Check for session handoff
- Read
.add/handoff.mdif it exists - Note any in-progress work or decisions relevant to this operation
- If handoff mentions blockers for this skill's scope, warn before proceeding
- Read
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 · 558 lines · 16 tokens per session scan A e9bd3d283cbc
deploy is a skill published in the GitHub repository MountainUnicorn/add (11 stars, last pushed 1mo ago), licensed MIT. It adds 16 tokens to every session and 4,496 once invoked, about $0.0001 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
release-patterns
PR creation, CI/CD validation, merge coordination, and release patterns. Use when creating pull requests, running pre-PR validation, checking CI status, coordinating merges, or managing releases. Do NOT use for routine development commits -- see safe-workflow skill instead.
safe-workflow
SAFe development workflow guidance including branch naming conventions, commit message format, rebase-first workflow, and CI validation. Use when starting work on a Linear ticket, preparing commits, creating branches, writing PR descriptions, or asking about contribution guidelines.
harden-gitlab-ci
Harden GitLab CI/CD pipelines for supply-chain security — SHA-pin include: and CI/CD components, scope the CIJOBTOKEN allowlist, protect and mask variables, pin job image digests, and use idtokens/OIDC instead of long-lived secrets. Use when adding or auditing a .gitlab-ci.yml, before making a GitLab project public…
validate-quality-config
Validate consistency across quality configuration files. Use after setup-git-hooks, when debugging "works locally, fails in CI" issues, before major releases, or when onboarding.
megalinter-setup
Install or upgrade MegaLinter on a repository. Use when the user wants to add MegaLinter to a project, set up linting CI, update MegaLinter configuration or version, or says "install megalinter", "setup linting", "add code quality checks". Always goes through npx mega-linter-runner (--install or --upgrade), then…
pr-watch-fix
Watch the GitHub PR for the current branch, wait for CI to finish, and autonomously fix failing jobs by reading logs, editing sources, and pushing. Stops cleanly when stuck.