agentspec: Command for Claude Code

.claude/commands/core/meeting.md

meeting is a command for Claude Code from luanmorenommaciel/agentspec. It costs 17 tokens per session (343 once invoked), scanned A, original, MIT.

A command that reads meeting notes or transcripts and turns them into structured documentation. It identifies decisions, assigned tasks, unresolved questions, and notable findings.

In plain words
What is it for?
Use it to analyze one meeting, create requirements from it, or combine several meetings into one summary.
Why use it?
It makes responsibilities and follow-up work easier to find after a meeting.

Command for Claude Code

Written for Claude Code: installed under .claude/.

This is luanmorenommaciel/agentspec's own configuration. It tells Claude Code how to work on agentspec itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything agentspec configures →

Reuse

Borrowing it

Nothing to install: this file belongs to luanmorenommaciel/agentspec. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/luanmorenommaciel/agentspec/main/.claude/commands/core/meeting.md
Clone the repo
git clone --depth 1 https://github.com/luanmorenommaciel/agentspec

Made for: Claude Code.

Wrote 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.

agentmods badge for meeting

README.md
[![agentmods](https://agentmods.dev/badge/commands/luanmorenommaciel/agentspec/meeting.svg)](https://agentmods.dev/commands/luanmorenommaciel/agentspec/meeting)
Your own site
<a href="https://agentmods.dev/commands/luanmorenommaciel/agentspec/meeting"><img src="https://agentmods.dev/badge/commands/luanmorenommaciel/agentspec/meeting.svg" alt="Measured on agentmods" height="20"></a>
Per session 17 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 343 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00017 $0.00343
Opus 5 $0.00009 $0.00171
Sonnet 5 $0.00003 $0.00069
Haiku 4.5 $0.00002 $0.00034

Measured 6d ago against content hash b213a727419e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

meeting 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.

.claude/commands/core/meeting.md · 58 lines

What it actually says

/meeting Command

Analyze meeting transcripts and extract structured, actionable documentation.

Usage

# Analyze a meeting transcript
/meeting notes/standup-2026-03-26.md

# Analyze and create requirements
/meeting notes/stakeholder-review.md --output define

# Consolidate multiple meetings
/meeting notes/sprint-*.md --consolidate

What It Does

  1. Invokes the meeting-analyst agent
  2. Reads meeting transcript (notes, recording summary, or raw text)
  3. Extracts:
    • Decisions made (with who decided and context)
    • Action items (with owner, deadline, priority)
    • Open questions (unresolved, needs follow-up)
    • Key insights (non-obvious observations)
    • Data engineering context (if present: sources, SLAs, schema changes)

Output Format

## Meeting Analysis: {Title}

### Decisions
| # | Decision | Decided By | Context |
|---|----------|-----------|---------|

### Action Items
| # | Action | Owner | Deadline | Priority |
|---|--------|-------|----------|----------|

### Open Questions
| # | Question | Blocker? | Follow-up |
|---|----------|----------|-----------|

### Key Insights
- {Non-obvious observation}

Integration with SDD

Use --output define to generate a DEFINE document from meeting notes — the meeting-analyst extracts requirements and feeds them into the define-agent.

Changes

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.

  1. 6d ago First seen · 58 lines · 17 tokens per session scan A b213a727419e

Subscribe to this mod's changes

meeting is a command published in the GitHub repository luanmorenommaciel/agentspec (246 stars, last pushed 2d ago), licensed MIT. It adds 17 tokens to every session and 343 once invoked, about $0.0001 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-09-01.