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/ch015/code-pentesterWrote 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/ch015/code-pentester/status)<a href="https://agentmods.dev/commands/ch015/code-pentester/status"><img src="https://agentmods.dev/badge/commands/ch015/code-pentester/status/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/ch015/code-pentester/status"><img src="https://agentmods.dev/badge/commands/ch015/code-pentester/status.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.00015 | $0.01591 |
| Opus 5.5 | $0.00006 | $0.00636 |
| Sonnet 5.5 | $0.00003 | $0.00318 |
| Haiku 4.5 | $0.00002 | $0.00159 |
Grade A, and why
status 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 24d 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/ch015:status — 진단 현황
당신은 CH015 보안 진단 시스템의 현황 관리자입니다. 현재 세션에서 수행된 모든 진단 활동을 요약하여 보고합니다.
Usage Examples
# 현재 세션의 전체 진단 현황 확인
/ch015:status
출력 포맷
┌──────────────────────────────────────────────────────────────┐
│ CH015 ENGAGEMENT STATUS │
├──────────────────────────────────────────────────────────────┤
│ Project: [프로젝트명] │
│ Level: [basic / standard / regulated] │
│ Date: [YYYY-MM-DD] │
├──────────────────────────────────────────────────────────────┤
│ │
│ Services Executed: │
│ ✅ VA — Score: XX/100 (등급 X) — F: C/H/M/L/I │
│ ✅ Verify — Round: 1st/2nd — 이의: N건 — Convergence:✓ │
│ ✅ Pentest — Score: XX/100 — POC: X건 — Live: Y/Z │
│ CONFIRMED: X / BLIND_ACCEPT: Y / BLOCKED: Z │
│ ⬜ Red Team — 미실행 │
│ │
│ Architecture Dimension Health: │
│ A1 인증 [Healthy/Caution/Critical] │
│ A2 인가 [Healthy/Caution/Critical] │
│ ... │
│ │
│ Total Findings: XX건 │
│ 🔴 CRITICAL: X | 🟠 HIGH: X | 🟡 MEDIUM: X │
│ 🔵 LOW: X | ⚪ INFO: X | 🔘 STRUCTURAL_WEAKNESS: X │
│ │
│ Composite Pass Conditions: │
│ Score ≥ 85 [✓/✗] │
│ CRITICAL = 0 [✓/✗] │
│ HIGH ≤ 2 [✓/✗] │
│ CVSS ≥ 9.0=0 [✓/✗] │
│ 종합 판정 [PASS/FAIL] │
│ │
│ Pending Verification: │
│ PENTEST: X건 (Route_F) │
│ REDTEAM: Y건 (Phase 4.6) │
│ EXTERNAL: Z건 (운영 환경 직접 확인) │
│ │
│ │
│ Root Cause Distribution: │
│ ARCHITECTURE: X | CONFIGURATION: X │
│ CODE: X | PROCESS: X │
│ │
│ Fix Status: │
│ 🔧 수정 가이드 제공: X건 │
│ ✅ 재검증 완료: X건 │
│ ⏳ 미처리: X건 │
│ │
├──────────────────────────────────────────────────────────────┤
│ Next Actions: │
│ → /ch015:verify 독립 검증 (R0.5 Autonomous Discovery) │
│ → /ch015:report 전체 보고서 생성 │
│ → /ch015:fix 특정 취약점 수정 가이드 │
│ → /ch015:redteam 인프라 보안 진단 │
│ → /ch015:va diff 변경분 재검증 │
│ → /ch015:compliance 이행점검 (Baseline 대비 패치 상태) │
└──────────────────────────────────────────────────────────────┘
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.
- 24d ago Changed a134d1504e3b
- 1mo ago Changed 97ebc0e66ca8
- 1mo ago First seen · 135 lines · 15 tokens per session scan A abd66232227f
status is a command published in the GitHub repository ch015/code-pentester (4 stars, last pushed 3d ago), licensed MIT. It adds 15 tokens to every session and 1,591 once invoked, about $0.0001 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-31.
Other commands, from other repositories
plugin-update
Upgrade DeepInit to the latest version — pulls the newest from the marketplace (on one confirm), then guides the host-correct reload. Ends the "is my plugin stale?" dance.
check
Is the context layer still true? 0-token staleness + broken-citation audit (no LLM, CI-friendly). Add --status for the fast hash-only subset.
impact
Which tests a change impacts, with a ready-to-run test command.
map
Generate MAP.md — a relational map of every file, function, signature, and call in the repo.
sanity
Cross-check a dekko callers/uses result against a targeted grep before trusting a low/zero count.
doctor
Diagnose dekko environment/install issues (PATH shadowing, map freshness, MCP registration, plugin, hooks, CLAUDE.md policy block).