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 commands/davistroy/claude-marketplace/analyze-transcript.evalgit clone --depth 1 https://github.com/davistroy/claude-marketplaceWrote 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/commands/davistroy/claude-marketplace/analyze-transcript.eval)<a href="https://agentmods.dev/commands/davistroy/claude-marketplace/analyze-transcript.eval"><img src="https://agentmods.dev/badge/commands/davistroy/claude-marketplace/analyze-transcript.eval.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.1 | $0.00000 | $0.00672 |
| Opus 5 | $0.00000 | $0.00336 |
| Sonnet 5 | $0.00000 | $0.00134 |
| Haiku 4.5 | $0.00000 | $0.00067 |
Grade A, and why
analyze-transcript.eval 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.
How it starts
The opening of the file, as written. The whole thing — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Eval: /analyze-transcript
Purpose
Reads a meeting transcript and produces a structured report with key discussion points, action items, decisions, and risks. Good output captures all explicit action items and decisions from the transcript without fabricating details.
Fixtures
| Fixture | Purpose |
|---|---|
docs/meeting-transcript.md |
20-min kickoff meeting with 4 action items, 3 decisions, 2 risks |
Test Scenarios
S1: Happy path — markdown output
Invocation: /analyze-transcript fixtures/docs/meeting-transcript.md
Must:
- Creates a report file (timestamped) in the current directory or
reports/ - Report contains an action items section with at least 3 of the 4 actual action items
- Report contains a decisions section listing all 3 technology decisions (Node.js, PostgreSQL, Block Kit)
- Report contains a risks section identifying both risks (rate limiting, Jamie's availability)
- Each action item includes the owner and due date when stated in the transcript
Should:
- Action items include: Dev/scheduler spike (Jan 16), Sam/ECS provisioning (Jan 17), Alex/MVP doc (Jan 14), Alex/Payments PM follow-up (Jan 12)
- Decisions include: Node.js 20 LTS confirmed, PostgreSQL 15 confirmed, Slack Block Kit confirmed
- Report includes a participants section
- Meeting date and duration captured
Must NOT:
- Invent action items not in the transcript
- Invent attendees not listed
S2: JSON output format
Invocation: /analyze-transcript fixtures/docs/meeting-transcript.md --format json
Must:
- Output file is valid JSON
- JSON contains
action_items,decisions,risksarrays - Each action item has
owneranddue_datefields where available
Must NOT:
- Create a markdown file when
--format jsonis specified
S3: Error — file not found
Invocation: /analyze-transcript fixtures/docs/nonexistent.txt
Must:
- Displays error message referencing the missing file
- Does not create output file
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 · 94 lines · 0 tokens per session scan A 6c2d33381bfc
analyze-transcript.eval is a command published in the GitHub repository davistroy/claude-marketplace (5 stars, last pushed 5d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 672 tokens. 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 commands, from other repositories
brand-generate
Generate an on-brand document from a saved Brand Profile.
prose-review-docs
Reviews markdown documentation files or directories against the active prose style rules — the plugin's vendor-neutral baseline plus your organization's overlay when one is configured. Accepts a file path or directory (recursive). Runs prose-style-checker and optionally Vale. Supports --fix to auto-apply safe…
cti-report
Render case deliverables — relationship graph (PNG/SVG/Mermaid) and a polished PDF/DOCX assessment. Usage: /cti-report [--graph|--pdf].
ppt-image2-editable-rebuild
Rebuild image2 or imagegen reference slides as editable PowerPoint decks.
convert
Convert a file to Markdown using markitdown.
render-figures
Compile all .tex and .typ figure files in a directory.