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 skills add kohj1018/agentic-dev-harness --skill run-milestonegit clone --depth 1 https://github.com/kohj1018/agentic-dev-harnessWrote 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/skills/kohj1018/agentic-dev-harness/run-milestone)<a href="https://agentmods.dev/skills/kohj1018/agentic-dev-harness/run-milestone"><img src="https://agentmods.dev/badge/skills/kohj1018/agentic-dev-harness/run-milestone/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/skills/kohj1018/agentic-dev-harness/run-milestone"><img src="https://agentmods.dev/badge/skills/kohj1018/agentic-dev-harness/run-milestone.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.00032 | $0.00414 |
| Opus 5.5 | $0.00013 | $0.00166 |
| Sonnet 5.5 | $0.00006 | $0.00083 |
| Haiku 4.5 | $0.00003 | $0.00041 |
Grade A, and why
run-milestone 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 16d 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.
This is a copy
84% identical to accept-milestone — 10 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Source of truth: .claude/skills/run-milestone/SKILL.md. Read it and follow the workflow.
Treat all frontmatter keys other than name and description (e.g., agent:, disable-model-invocation:, allowed-tools:, context:, argument-hint:, model:, effort:) as Claude-only and ignore them — execute locally in Codex.
Sub-skill invocation in Codex (ADR-076 D15): 본문이 하위 skill을 «Skill 도구로 호출»하라고 할 때 Codex에서는 해당 .claude/skills/<name>/SKILL.md를 읽어 그 인자로 그대로 수행한다. «처음 쓸 때와 컴팩션 뒤 처음 쓸 때만 호출» 규칙은 «그때만 SKILL.md를 다시 읽는다»로 읽는다. inner-loop wrapper($implement-workitem 등)를 거치지 않는다. 서브에이전트 위임은 각 하위 skill의 Codex 순차 degrade를 따른다.
Slash command translation: 본문 안의 /run-milestone 표기는 Claude 슬래시 커맨드다. Codex에서는 $run-milestone으로 읽고 사용자에게 안내한다 (예: 본문 "다음 단계: /stabilize-milestone M2" → Codex 응답에서는 "다음 단계: $stabilize-milestone M2"). Codex CLI는 /를 빌트인 슬래시 커맨드에 쓰므로 명시적 치환이 필요.
Preserve all repo policies from AGENTS.md and docs/.
If the source path no longer exists, this wrapper is stale — see ADR-010.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 16d ago First seen · 17 lines · 32 tokens per session scan A 79e3f1946c88
run-milestone is a skill published in the GitHub repository kohj1018/agentic-dev-harness (2 stars, last pushed 17d ago), licensed MIT. It adds 32 tokens to every session and 414 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 84% identical to accept-milestone, differing in 10 lines, and is treated as a copy.
Other skills, from other repositories
acli
Atlassian CLI (official acli binary) for Jira Cloud, Confluence Cloud, and org admin tasks from the terminal. Use whenever the user wants to create, view, edit, transition, assign, clone, archive, comment on, link, or bulk-operate on Jira work items; list or manage projects, boards, sprints, filters, dashboards, or…
orca-orchestration
Multi-session agent orchestration for this repo: one conductor session coordinating a fleet of persistent worker sessions (one per story, per module, per failure cluster) through the Orca runtime, plus the non-Orca fallback where the same launch lines are pasted by hand. Owns the HOW of fleet work — terminals, Runs…
kirby-project-tour
Maps a Kirby project using Kirby MCP tools/resources, including roots, templates, snippets, controllers, models, blueprints, plugins, runtime status, and key config. Use when a user wants a project overview, file locations, or a quick orientation before making changes.
sprint-testing
Orchestrates in-sprint manual QA per issue across Stages 1 (Planning), 2 (Execution) and 3 (Reporting). Use for user-story testing, bug retesting, and sprint-wide QA loops. Creates the PBI folder, drives session-start, runs the triage + veto + risk-score decision tree on bugs, produces the ATP + ATR + TC artifacts in…
jira-administration
Run bounded Jira administration workflows for project Components or Atlassian instance migration. Use for jira-components, sync Jira components, jira-instance-migration, changed Jira URL, or repoint Jira. Both modes are sealed behind read-first analysis and explicit user approval before any Jira, credential-session…
studio-goal-progress
Use when a KIT-managed Codex or Hermes Goal needs evidence-backed percentage, ETA range, live read-only progress views, or portable append-only progress recovery.