meeting-pack

meeting-pack is a skill for Claude Code, Codex from ALTEN-group/coding-pal. It costs 91 tokens per session (903 once invoked), scanned A, original, MIT.

A meeting-record tool that turns a client transcript into a checked pack containing a summary, domain terms, and possible business needs with direct quotes. A transcript is a written record of a conversation.

In plain words
What is it for?
Use it to clean up transcripts, build and validate meeting packs, confirm them with human review, create backlog issues, and stage new glossary terms.
Why use it?
It preserves what the client actually said and lets people verify that later requirements and backlog items match the source conversation.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: reads .claude/ paths.

Good fit Use it to clean up transcripts, build and validate meeting packs, confirm them with human review, create backlog issues, and stage new glossary terms.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/alten-group/coding-pal/meeting-pack
Install

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.

Any agent
npx skills add ALTEN-group/coding-pal --skill meeting-pack
Clone the repo
git clone --depth 1 https://github.com/ALTEN-group/coding-pal

Made for: Claude Code, Codex.

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-pack

README.md
[![agentmods](https://agentmods.dev/badge/skills/alten-group/coding-pal/meeting-pack/github.svg)](https://agentmods.dev/skills/alten-group/coding-pal/meeting-pack)
Your own site
<a href="https://agentmods.dev/skills/alten-group/coding-pal/meeting-pack"><img src="https://agentmods.dev/badge/skills/alten-group/coding-pal/meeting-pack/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.

agentmods 80×15 button for meeting-pack

Your own site · 80×15
<a href="https://agentmods.dev/skills/alten-group/coding-pal/meeting-pack"><img src="https://agentmods.dev/badge/skills/alten-group/coding-pal/meeting-pack.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 91 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 903 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.00091 $0.00903
Opus 5.5 $0.00036 $0.00361
Sonnet 5.5 $0.00018 $0.00181
Haiku 4.5 $0.00009 $0.00090

Measured 4d ago against content hash 024755cd3ca5, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

meeting-pack 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 4d ago.

The scan reads SKILL.md. This mod also ships 7 executable files (scripts/emit-candidates.mjs, scripts/emit-candidates.test.mjs, scripts/meeting-fixtures.mjs, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

skills/meeting-pack/SKILL.md · 60 lines

How it starts

The opening of the file, as written. The whole thing — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Meeting Pack

Produce deterministic, immutable meeting records so that every later stage can be checked against what the client actually said. AI structures the dialogue; people verify and confirm.

When to Use This Skill

  • A plain-text transcript from the sanctioned meeting tool must become a normalized transcript.md.
  • A transcript must become a Meeting Pack: executive summary, domain terminology, and candidate business needs with verbatim, client-attributed quotes.
  • CI must gate a pack (draft) or confirm it after human verification (confirmed).
  • A confirmed pack must become backlog issues for Triage, and new terms must be staged for the glossary.

Path resolution

Resolve references/ and scripts/ relative to this skill's install directory (the folder that contains this SKILL.md), not the consumer repository root or the current shell cwd. If the skill was installed under .agents/skills/meeting-pack/ or .claude/skills/meeting-pack/, use that base path.

Workflow

  1. Read references/meeting-pack-contract.md now. It is the authoritative source for file layout, headings, fields, stages, the glossary, and the Triage handoff. Scope and judgement are owned by the calling Meeting Analyst agent or session.
  2. Normalize the plain-text export once. The result is immutable:
node scripts/normalize-transcript.mjs --input exports/call.txt --roster roster.json \
  --title "Acme discovery call" --date 2026-09-24 --tool "<meeting tool>" \
  --consent "Yes - announced at the start of the call" \
  --output meetings/2026-09-24-acme-discovery/transcript.md
  1. Draft pack.md from the transcript and docs/glossary.md. Copy quotes character for character. Leave every confirmation Pending. Record the transcript's SHA-256 (printed by the script).
  2. Validate with the deterministic script. Treat a nonzero exit as invalid output and fix the file. To prove the transcript came from a sanctioned tool, add --sanctioned docs/governance/sanctioned-tools.md (a Markdown bullet list, or one tool per line; headings, # comments, and prose around the bullets are ignored): the transcript header Tool must appear on it, case-insensitively.

Read the full file on GitHub · 60 lines

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. 4d ago First seen · 60 lines · 91 tokens per session scan A 024755cd3ca5

Subscribe to this mod's changes

meeting-pack is a skill published in the GitHub repository ALTEN-group/coding-pal (5 stars, last pushed 5d ago), licensed MIT. It adds 91 tokens to every session and 903 once invoked, about $0.0004 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-10-14.