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/kensaurus/cursor-kenji/deploy-checkergit clone --depth 1 https://github.com/kensaurus/cursor-kenjiWhat 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.00039 | $0.00609 |
| Opus 5 | $0.00019 | $0.00304 |
| Sonnet 5 | $0.00008 | $0.00122 |
| Haiku 4.5 | $0.00004 | $0.00061 |
Grade A, and why
deploy-checker 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.
What it actually says
When Invoked
Run all checks in sequence. Stop at first critical failure.
Check Pipeline
1. Build Check
npm run build 2>&1
- Zero errors required
- Warnings acceptable but note them
2. Type Check
npx tsc --noEmit 2>&1
- Zero type errors required
- Strict mode must pass
3. Lint Check
npm run lint 2>&1
- Zero errors required
- Warnings acceptable in non-critical paths
4. Test Check
npm run test -- --run 2>&1
- All tests must pass
- Note any skipped tests
5. Security Scan
# Check for secrets in staged files
git diff --cached --name-only | while read f; do
grep -l "sk_live\|SUPABASE_SERVICE\|password.*=\|token.*=" "$f" 2>/dev/null
done
# Check for exposed env vars
grep -r "process.env\." --include="*.tsx" --include="*.ts" -l | grep -v "server\|action\|api\|config"
6. Dependency Check
npm audit --production 2>&1 | tail -5
- No critical vulnerabilities
7. Database Check (if migrations exist)
# Check for unapplied migrations
ls -la supabase/migrations/ | tail -5
# Verify RLS on all tables (Supabase MCP)
8. Git Hygiene
git status
git log --oneline -5
- No uncommitted changes
- Commit messages follow conventional format
- No merge conflicts
Output Format
## Deploy Check Results
| Check | Status | Details |
|-------|--------|---------|
| Build | PASS/FAIL | |
| Types | PASS/FAIL | |
| Lint | PASS/FAIL | X warnings |
| Tests | PASS/FAIL | X passed, Y skipped |
| Security | PASS/FAIL | |
| Dependencies | PASS/FAIL | |
| Database | PASS/FAIL | |
| Git | PASS/FAIL | |
## Verdict: READY TO SHIP / BLOCKED
### Blockers (if any)
1. [Critical issue that must be fixed]
### Warnings (non-blocking)
1. [Issue to be aware of]
If all checks pass: "All clear. Ship it." If any critical failure: "BLOCKED. Fix [issue] before deploying."
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 · 100 lines · 39 tokens per session scan A 0040732775e2
deploy-checker is an agent published in the GitHub repository kensaurus/cursor-kenji (9 stars, last pushed 4d ago), licensed MIT. It adds 39 tokens to every session and 609 once invoked, about $0.0002 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
debugger
Debugging specialist for errors, test failures, and unexpected behavior. Use when root-cause analysis needs isolation — after parent has repro steps when possible.
verifier
Validates completed work. Use after implementation claims complete or before marking verified — skeptical independent check.
codex-coder
Coding agent via Codex CLI. Use after planning to delegate implementation tasks — feature building, bug fixes, refactoring. Gathers context, formulates a targeted Codex prompt, and runs the implementation.
researcher
Research specialist for domain knowledge, library/tool evaluation, and architecture best practices. Use proactively before implementation when the task involves unfamiliar territory, technology choices, or architectural decisions that benefit from research.
verifier
Verification and QA specialist. Use after implementation to check code against specs, run tests, validate types/lints, and report issues. Reports problems — does not fix them.
engineer
Full-stack coding agent. Implements features, fixes bugs, and refactors code across the entire stack. Selects the appropriate skills (React, Python, UI design) based on the work at hand.