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 TommyBez/evex --skill meeting-action-extractgit clone --depth 1 https://github.com/TommyBez/evexWrote 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/tommybez/evex/meeting-action-extract)<a href="https://agentmods.dev/skills/tommybez/evex/meeting-action-extract"><img src="https://agentmods.dev/badge/skills/tommybez/evex/meeting-action-extract/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/tommybez/evex/meeting-action-extract"><img src="https://agentmods.dev/badge/skills/tommybez/evex/meeting-action-extract.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.00043 | $0.00304 |
| Opus 5.5 | $0.00017 | $0.00122 |
| Sonnet 5.5 | $0.00009 | $0.00061 |
| Haiku 4.5 | $0.00004 | $0.00030 |
Grade A, and why
meeting-action-extract 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 1mo 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.
What it actually says
Meeting action extract
Read transcripts under the configured MEETING_TRANSCRIPT_ROOTS (for
example meetings, notes/meetings, transcripts). Draft Linear issues.
Stop for human approval. Never create issues.
Steps
- Call
search_meeting_transcriptswith keywords from the request (owner names, "TODO", "by Friday", a meeting date). - Call
read_meeting_transcripton the best-matching paths. - Pull title, owner, deadline, and a short evidence quote from those files.
- Call
extract_meeting_actionsonce with the structured list. - Call
draft_linear_issuesonce. It always returnscreatedfalse. - Call
create_linear_issuesso a human can approve. That call always pauses. Even after approval it never creates issues. - If nothing in-scope has an action, say so.
Do not
- Create, save, or file Linear issues
- Call
save_issueor any Linear write tool - Claim the drafts were created
- Invent owners or deadlines that the transcript does not state
- Skip the disk read when a transcript path is in scope
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.
- 1mo ago First seen · 31 lines · 43 tokens per session scan A 90217beb6713
meeting-action-extract is a skill published in the GitHub repository TommyBez/evex (25 stars, last pushed 1mo ago), licensed MIT. It adds 43 tokens to every session and 304 once invoked, about $0.0002 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-07.
Other skills, from other repositories
story-readiness
Is a story implementation-ready? Checks clear acceptance criteria, open questions, ADR refs. READY/NEEDS WORK/BLOCKED/NOT ASSESSED.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
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…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
ring:mapping-feature-relationships
Mapping how features relate and phasing the work: categorizing PRD features, grouping them into domains, charting cross-feature journeys, dependencies, and integration points, and defining the binding Phases that plan.md mirrors one-to-one at Gate 7. Gate 2 of ring:planning-large-features; runs after…