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 nobodyohm-web/Thot --skill meeting-action-itemsgit clone --depth 1 https://github.com/nobodyohm-web/ThotWrote 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/nobodyohm-web/thot/meeting-action-items)<a href="https://agentmods.dev/skills/nobodyohm-web/thot/meeting-action-items"><img src="https://agentmods.dev/badge/skills/nobodyohm-web/thot/meeting-action-items/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/nobodyohm-web/thot/meeting-action-items"><img src="https://agentmods.dev/badge/skills/nobodyohm-web/thot/meeting-action-items.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.00015 | $0.00769 |
| Opus 5 | $0.00008 | $0.00385 |
| Sonnet 5 | $0.00003 | $0.00154 |
| Haiku 4.5 | $0.00002 | $0.00077 |
Grade A, and why
meeting-action-items 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 6d 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
100% identical to meeting-action-items — 0 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.
How it starts
The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Meeting Action Items
Convert an existing transcript or notes set into accountable follow-through. teams-meeting-pipeline can retrieve Teams artifacts; this skill begins once notes/transcript content is available, from any source.
When to Use
- "Extract action items from this meeting."
- "What did we decide and who owns what?"
- "Draft the follow-up and create tickets."
- "Reconcile these notes with the existing project board."
Don't use for: retrieving meeting recordings or transcripts (use teams-meeting-pipeline or the relevant connector first).
Procedure
1. Establish meeting evidence
Use read_file on the provided notes/transcript files. Identify meeting title/date, participants, source files, transcript completeness, and whether speaker/time references exist. Done when missing portions and low-confidence transcription are stated.
2. Separate evidence types
Extract into distinct lists:
- decisions actually made
- proposals not decided
- explicit commitments
- questions and blockers
- risks and dependencies
- facts/context
Do not turn brainstorming into decisions. Done when each candidate item has a supporting quote, timestamp, page, or note reference when available.
3. Normalize action items
For every commitment record:
| Field | Rule |
|---|---|
| outcome | Concrete result, not a vague topic |
| owner | Explicit named owner; otherwise unresolved |
| due date | Explicit date or unresolved; never invent one |
| dependency | What must happen first |
| acceptance | Observable completion condition |
| source | Transcript/note reference |
Done when every action has supported fields or visible unresolved values.
4. Reconcile existing records
Load the user's tracker connector (notion, github-issues, or whichever system owns the work). Search for matching open items before creating anything — recurring meetings breed duplicate tickets. Preserve conflicts in owner/date/status for confirmation rather than silently overwriting. Done when proposed creates vs updates are distinguished.
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.
- 6d ago First seen · 88 lines · 15 tokens per session scan A 1902f782551d
meeting-action-items is a skill published in the GitHub repository nobodyohm-web/Thot (0 stars, last pushed 15d ago), licensed MIT. It adds 15 tokens to every session and 769 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to meeting-action-items, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
batch-all-issues
Resolve every open issue one at a time: fact-check each with web research, close the ones that need no action, and run the goal-pr skill to fix, review, and merge the ones that do — repeating until no actionable issues remain.
post-issue-comment
Post a reply comment on a GitHub issue in English with a natural, concise writing style, based on the intent passed as arguments.
secretary
Workspace and research management — dispatch analyses, monitor running agents, manage workspaces and threads.
cocoplus-config
CocoPlus configuration SSOT — $cocoplus sync propagates cocoplus.toml into downstream artifacts; $cocoplus migrate-config converts legacy safety-config.json. Invoked via $cocoplus sync and $cocoplus migrate-config.
project-manager
Project management expert for Agile, estimation, risk management, and stakeholder communication.
seed-list
Evaluate all pending seed trigger conditions against current project state and show which ideas are ready to promote and which are still waiting.