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.
git clone --depth 1 https://github.com/Ramsbaby/jarvisWrote 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/ramsbaby/jarvis/deploy)<a href="https://agentmods.dev/commands/ramsbaby/jarvis/deploy"><img src="https://agentmods.dev/badge/commands/ramsbaby/jarvis/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/ramsbaby/jarvis/deploy"><img src="https://agentmods.dev/badge/commands/ramsbaby/jarvis/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.00048 | $0.00293 |
| Opus 5.5 | $0.00019 | $0.00117 |
| Sonnet 5.5 | $0.00010 | $0.00059 |
| Haiku 4.5 | $0.00005 | $0.00029 |
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 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.
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
Jarvis 배포/업데이트
Jarvis AI 시스템을 안전하게 업데이트합니다.
배포 전 체크리스트
- 현재 시스템 상태 확인 (
/doctor) - 변경된 파일 확인
- Discord bot 활성 세션 없는지 확인
배포 단계
LaunchAgent 업데이트
launchctl unload ~/Library/LaunchAgents/ai.jarvis.discord-bot.plist
# ... 파일 수정 ...
launchctl load ~/Library/LaunchAgents/ai.jarvis.discord-bot.plist
크론 업데이트
crontab -e
# 변경 후 즉시 적용됨
tasks.json 업데이트
# ~/.jarvis/config/tasks.json 수정
# jarvis-cron.sh가 다음 실행 시 자동 반영
검증
# Discord bot 재시작 확인
launchctl list | grep jarvis
tail -5 ~/.jarvis/logs/watchdog.log
# 크론 테스트
~/.jarvis/bin/jarvis-cron.sh system-health
# E2E
~/.jarvis/scripts/e2e-test.sh
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 First seen · 47 lines · 48 tokens per session scan A de82d860939a
deploy is a command published in the GitHub repository Ramsbaby/jarvis (20 stars, last pushed 4d ago), licensed MIT. It adds 48 tokens to every session and 293 once invoked, about $0.0002 per session on Opus 5.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-30.
Other commands, from other repositories
bm-init
Onboard (or refresh) basemind in this repo — write basemind.toml and inject a "prefer basemind over grep/read/git" rules block into a rules file you choose (CLAUDE.local.md / AGENTS.local.md / CLAUDE.md / AGENTS.md / ai-rulez).
bm
Ask basemind anything about the current codebase — outlines, refs, callers, git history, blame, diffs, docs, memory.
frankx-ai-deploy
Deploy FrankX.AI website changes to Vercel with quality checks.
deploy
Deploy the current project to Vercel. Pass "prod" or "production" as argument to deploy to production. Default is preview deployment.
pg-imersao-publicar
Dia 3 · PUBLICAR — GitHub + Railway. Prova, uso e manutenção (onda 2 sem reinstalar).
gitops-drift
Detect drift between git manifests and what's actually deployed in your clusters.