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 manishiitg/coding-agent-loop --skill meeting-decision-to-owned-follow-throughgit clone --depth 1 https://github.com/manishiitg/coding-agent-loopWrote 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/manishiitg/coding-agent-loop/meeting-decision-to-owned-follow-through)<a href="https://agentmods.dev/skills/manishiitg/coding-agent-loop/meeting-decision-to-owned-follow-through"><img src="https://agentmods.dev/badge/skills/manishiitg/coding-agent-loop/meeting-decision-to-owned-follow-through/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/manishiitg/coding-agent-loop/meeting-decision-to-owned-follow-through"><img src="https://agentmods.dev/badge/skills/manishiitg/coding-agent-loop/meeting-decision-to-owned-follow-through.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.00028 | $0.00641 |
| Opus 5.5 | $0.00011 | $0.00256 |
| Sonnet 5.5 | $0.00006 | $0.00128 |
| Haiku 4.5 | $0.00003 | $0.00064 |
Grade A, and why
meeting-decision-to-owned-follow-through 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 20d 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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Meeting Decision to Owned Follow-through
Outcome
Produce a sourced meeting action register and a project status report that distinguishes proposed, accepted, open, blocked, and completed work. A note, task proposal, approved task, provider-created task, and observed completion are separate states.
When to use
Use when a small team wants decisions from authorized meeting notes tracked against a project. One Crew can carry both capabilities when owner and access are shared; use two Crews for a distinct project owner or lifecycle.
Discovery and user direction
Inspect existing Operations Crews, meeting revision, participant map, task tracker, prior actions, project scope, status rules, and review owner. Propose reuse or creation. Show the exact route before Builder applies it; selection leaves setup pending.
Required inputs
Bind tenant, meeting and notes revision, project, time zone, source spans, action and task IDs, accepted owners, due dates, duplicate rule, status evidence, and reporting owner.
Plan and AgentWorks tools
Reuse Meeting Actions Coordinator and Project Status Reporter; add Chief of Staff for a distinct leadership review. Meeting writes meeting-action-register/v1; run the bundled validator before Status consumes it. Status re-reads current task records and writes project-action-status/v1; validate the pair. Optional Review writes operations-review-brief/v1 from validated status. Insert explicit validator steps in the Workflow. Any task write or stakeholder message requires a separate exact approval and provider receipt.
Knowledge and persistence
Save tenant, meeting, revision, project, action, task, decision, owner acceptance, due date, run, source, approval, receipt, and status IDs. On later notes revisions, reconcile the same action keys and existing tracker records before proposing another write.
Validation and reporting
The validator checks identity, source spans, owner acceptance, duplicate links, status joins, and completion evidence. Fictional meeting, status, and review pass. The false completion fails. The reporting dashboard separates pending confirmation, open, blocked, done, duplicate, and unknown actions with owner decisions and cost.
What ships with it
9 files 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.
- examples/invalid-project-action-status.json 902 B
- examples/meeting-action-register.json 1.0 KB
- examples/operations-review-brief.json 591 B
- examples/project-action-status.json 996 B
- playbook.json 4.9 KB
- references/team-and-handoffs.md 2.9 KB
- scripts/test_validate_handoff.py 2.6 KB runs code
- scripts/validate_handoff.py 8.4 KB runs code
- SETUP.json 2.9 KB
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.
- 20d ago First seen · 48 lines · 28 tokens per session scan A 264e77d39089
meeting-decision-to-owned-follow-through is a skill published in the GitHub repository manishiitg/coding-agent-loop (13 stars, last pushed 19d ago), licensed MIT. It adds 28 tokens to every session and 641 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-09-27.
Other skills, from other repositories
kungfu-agent-onboarding
Use when a user asks to understand, start, inspect, extend, or safely operate installed Kungfu; verify the installed pack, select one intent route, personalize the explanation, and propose one smallest safe next action.
machinist
Use Machinist to create, assign, and monitor software tasks. Use when a coding agent needs to work with Machinist, its GitHub issue workflow, intake labels, direct runs, or managed queue.
ship-it
Worktree-side implementation orchestrator for an OpenSpec change. Idempotent: gates automated scenarios on filesystem reality, owns the red-test fix loop, runs the docker harness with always-teardown, then drives ship-change inline. Escape hatch writes SHIPITBLOCKED.md. Runnable headless. Triggers: "ship it", "build…
goga-task-by-specifying
Interactive task formulation from a raw request.
goga-cell-go
Golang rules for implementing CODEMANIFEST contracts.
kano-backlog
Prioritize and refine a GitHub Issues backlog with the Kano model — categorize every open issue as Must-be, Performance, Attractive, Indifferent, or Reverse, apply Kano + priority labels back to GitHub automatically, and recommend the single best next issue to pick up. Use this whenever the user wants to triage…