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/ozzy-labs/suasor/commitment-chasenpx skills add ozzy-labs/suasor --skill commitment-chasegit clone --depth 1 https://github.com/ozzy-labs/suasorWrote 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/ozzy-labs/suasor/commitment-chase)<a href="https://agentmods.dev/skills/ozzy-labs/suasor/commitment-chase"><img src="https://agentmods.dev/badge/skills/ozzy-labs/suasor/commitment-chase.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.00202 | $0.01659 |
| Opus 5 | $0.00101 | $0.00830 |
| Sonnet 5 | $0.00040 | $0.00332 |
| Haiku 4.5 | $0.00020 | $0.00166 |
Grade A, and why
commitment-chase 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.
How it starts
The opening of the file, as written. The whole thing — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
commitment-chase
相手が負う約束（owed_to_me）のうち期限超過のものを surface し、催促文ドラフトを組み立てる read skill。commitment-review が「自分が負う約束の受動的な台帳管理」なのに対し、本 skill は「相手への能動的な催促」を補完する対の skill（ADR-0021 の台帳を read で合成）。新 MCP tool は不要で、既存 read tool の合成で実現する（ADR-0008 の skill 設計）。
いつ発火するか
- 「催促して」「フォローアップしたい約束」
- 「借りてる約束」「相手に頼んだ約束どうなった」
- 約束を明示しない「あれどうなった」は本 skill ではなく find が受ける（ここで受けると task / トピックの進捗質問に「期限超過の約束はありません」と答えてしまう）
- 「相手の約束で期限切れ」「貸してる約束の期限切れ」
何をするか（MCP tool flow）
すべて read tool（ADR-0004）。副作用なし・エージェント自律 OK。専用 tool は追加しない（既存合成、ADR-0008）。
commitment.list（state=open,direction=owed_to_me）で相手が負う未解決の約束を引く。既定で緊急度順（期限超過が先頭・超過が長い順 → 期日が近い順 → 期日なし）で返り、各行に read 時派生のoverdueが付く（#509）。超過分だけ欲しいときはoverdue: trueで絞る。各 commitment はtitle/dueDate?/person?（記録どおりの生文字列）/personId?/personName?（person identity graph で解決した正規化人物・ADR-0022）/updated_at（ADR-0021）- 期限超過（
dueDateが現在時刻より過去）の約束をホスト側で抽出する。overdue 判定は read 時のホスト側合成（dueDate < now）で行う。dueDateを持たない約束は催促対象外（期限がないため）として別枠で軽く触れるに留める graph.related（各 commitment id 起点、direction=in）で約束の出所 source を辿り、source.getで本文を補って「誰に・何を・いつ約束してもらったか」を再構成する（provenance、ADR-0018）- ホスト LLM が期限超過の約束ごとに催促文ドラフトを text-only で組み立てて提示する。並び替えは不要（基線が既に緊急度順）。まとめる単位は
personId（あれば） — 同一人物の Slack / GitHub 別名で記録された約束が別人として 2 通に割れないようにする。personIdが無い行は生のperson文字列でまとめる。緊急度（超過日数）順に並べる
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 · 49 lines · 0 tokens per session scan A 11a881b64746
commitment-chase is a skill published in the GitHub repository ozzy-labs/suasor (0 stars, last pushed 24d ago), licensed MIT. It adds 202 tokens to every session and 1,659 once invoked, about $0.0010 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 skills, from other repositories
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
flow-next-tracker-sync
Project a flow-next spec to a tracker issue (Linear, GitHub, GitLab, Jira) and reconcile two-way. Use when asked to sync to a tracker. NOT plan-sync.
loop
Full execution protocol for MODE: LOOP — the compound-engineering loop: brainstorm → plan → build → review → improve, iterating under defense-in-depth stop conditions with generator/critic separation, durable resumable state, and mandatory compounding learning capture. Loaded on demand by the architect when the loop…
subagent-delegation
Canonical protocol for delegating GSD work to native Antigravity subagents — when to delegate, how to invoke, workspace isolation modes, and the inline fallback for older IDE versions.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.