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/bunhine0452/Ocul-PMWrote 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/bunhine0452/ocul-pm/next)<a href="https://agentmods.dev/commands/bunhine0452/ocul-pm/next"><img src="https://agentmods.dev/badge/commands/bunhine0452/ocul-pm/next.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.00031 | $0.00403 |
| Opus 5 | $0.00015 | $0.00201 |
| Sonnet 5 | $0.00006 | $0.00081 |
| Haiku 4.5 | $0.00003 | $0.00040 |
Grade A, and why
next 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 3d 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
/oculpm:next
플래너 ▶실행(앱)의 플러그인 대응물 — 계획을 핸들로 쓰는 구현 루프 한 바퀴.
plan_status도구로 활성 플랜의 미완 리프를 확인한다 ([ ]/[~], 하위를 가진 부모는 롤업 자동이라 제외).$ARGUMENTS로 항목 id 나 플랜을 지정했으면 그것을 우선한다.- 미완 리프가 없으면 "활성 플랜의 항목이 모두 끝났습니다"라 보고하고 끝낸다. 후보가 여럿이면 문서 순서상 첫 번째를 잡되, 무엇을 잡았는지 먼저 알린다.
- 그 항목을 구현한다 — 항목 문구의 "검증 가능한 동사구"가 완료 기준이다. 프로젝트에 게이트(빌드/테스트/린트)가 있으면 통과를 직접 확인한다.
- 끝나면
journal_write로 일지를 남기고plan_update로 그 항목 상태를 갱신한다 (AGENTS.md 규칙 그대로).plan_update는base_hash가 필수다 — 1번에서 받은plan_status응답의plans[].hash를 그대로 넘긴다. 구현하는 동안 다른 세션이 그 플랜을 고쳤으면 충돌 오류가 돌아오니,plan_status로 다시 읽어 그 항목이 아직 유효한지 확인한 뒤 새 hash 로 재호출한다. 다음 리프가 남았으면 이어서 돌지 물어본다.
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.
- 3d ago Changed · +4 lines 9f589442f594
- 8d ago First seen · 18 lines · 31 tokens per session scan A b879007d7fff
next is a command published in the GitHub repository bunhine0452/Ocul-PM (7 stars, last pushed today), licensed MIT. It adds 31 tokens to every session and 403 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 commands, from other repositories
mach12:issue-implement
Implement a specific stage of an issue's implementation plan.
mach12:gh-assign
Assign the current user to one or more GitHub issues, handling existing assignees.
mach12:gh-issue-read
Read a GitHub issue's title, body, and all comments; optionally locate an HTML-marker comment.
mach12:gh-sub-issues
Detect sub-issues of a GitHub issue using the two-strategy approach (API, then body-parse).
mach12:plan-comment-contract
Apply the canonical contract for a durable implementation-plan comment.
mach12:issue-create
Create a structured GitHub issue from current context or description.