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 commands/yousefnabil-soc/claude-apex/deploygit clone --depth 1 https://github.com/YousefNabil-SOC/claude-apexWrote 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/yousefnabil-soc/claude-apex/deploy)<a href="https://agentmods.dev/commands/yousefnabil-soc/claude-apex/deploy"><img src="https://agentmods.dev/badge/commands/yousefnabil-soc/claude-apex/deploy.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.00174 |
| Opus 5 | $0.00000 | $0.00087 |
| Sonnet 5 | $0.00000 | $0.00035 |
| Haiku 4.5 | $0.00000 | $0.00017 |
Grade A, and why
deploy 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 6d 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.
What it actually says
Deploy the current project to Vercel.
Steps:
- Run
git statusto check for uncommitted changes — warn the user if any exist - Check if
vercelCLI is logged in:vercel whoami - If not logged in, prompt: "Run
vercel loginin your terminal first" - Check for
vercel.jsonin the project root — create a basic one if missing - Run
vercel --prodto deploy to production - Output the deployment URL
Pre-flight checks:
- Confirm environment variables are set in Vercel dashboard (remind user)
- Check that build script exists in package.json
- Verify the framework is detected correctly
After deploy: show the live URL and suggest running vercel env ls to verify env vars.
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.
- 6d ago First seen · 17 lines · 0 tokens per session scan A 20dd70cbdb13
deploy is a command published in the GitHub repository YousefNabil-SOC/claude-apex (2 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 174 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-31.
Other commands, from other repositories
security-scan
Run security audit on codebase.
test-suite
Run comprehensive test suite with coverage analysis.
run
Execute prompt(s) from ./prompts/ with automatic archiving - for structured prompt-based work.
assemble-team
Assemble a pre-built agent team for parallel work - review, feature, debug, cross-platform, full-stack, or research.
standardize-claude-md
Add missing toolkit sections (Related Global Rules, Quick Start) to existing CLAUDE.md.
help
Explain Ralph Wiggum technique and available commands.