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 skills/kohj1018/agentic-dev-harness/implement-workitemnpx skills add kohj1018/agentic-dev-harness --skill implement-workitemgit 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/implement-workitem)<a href="https://agentmods.dev/skills/kohj1018/agentic-dev-harness/implement-workitem"><img src="https://agentmods.dev/badge/skills/kohj1018/agentic-dev-harness/implement-workitem.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 | $0.00029 | $0.00271 |
| Opus 5 | $0.00015 | $0.00135 |
| Sonnet 5 | $0.00006 | $0.00054 |
| Haiku 4.5 | $0.00003 | $0.00027 |
Grade A, and why
implement-workitem 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.
This is a copy
83% 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/implement-workitem/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.
Slash command translation: 본문 안의 /implement-workitem 표기는 Claude 슬래시 커맨드다. Codex에서는 $implement-workitem으로 읽고 사용자에게 안내한다 (예: 본문 "다음 단계: /finalize-workitem T-001" → Codex 응답에서는 "다음 단계: $finalize-workitem T-001"). 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.
- 3d ago First seen · 15 lines · 29 tokens per session scan A 78af51fd634e
implement-workitem is a skill published in the GitHub repository kohj1018/agentic-dev-harness (2 stars, last pushed 6d ago), licensed MIT. It adds 29 tokens to every session and 271 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 83% identical to accept-milestone, differing in 10 lines, and is treated as a copy.
Other skills, from other repositories
deploy
Use when shipping a release of Agent Sessions — bumping version, updating CHANGELOG, building, signing, notarizing, publishing appcast, and creating a GitHub release.
release-notes
Use when writing or curating the user-facing release copy for an Agent Sessions release — README "What's New", GitHub release notes, Sparkle release notes, or website/launch copy. Not for the internal CHANGELOG, which stays a full development history.
sc-skill
Capture deterministic macOS screenshots for testing, docs, release notes, and marketing assets. Use when asked to automate app screenshots, batch-generate screenshot sets, standardize window sizing/composition, or choose between Peekaboo and native macOS screenshot tooling.
add-agent-support
Create and ship AgentSessions support for a new or changed local AI agent/provider. Use when adding, reviewing, testing, documenting, or marketing a provider integration, session parser, transcript source, support-matrix entry, verified-version bump, or provider UI surface; drives the full loop from pre-support…
handover
Use when wrapping up or capturing the current state of a coding session — writes a short, dated entry to the repo's RepoHandover.md so a future agent or you can resume without grepping archived sessions. Triggers on "handover", "hand off", "write handover", "capture state", "checkpoint this session".
agent-session-format-check
Verify agent session format compatibility for Agent Sessions. Use when any agent CLI updates, when monitoring flags drift, or when bumping max verified versions (fixtures + docs + tests). Covers session schema, usage/limits tracking, storage backends, and discovery path contracts for all supported agents.