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 CodeInfinity1/Stram --skill meeting-follow-upgit clone --depth 1 https://github.com/CodeInfinity1/StramWrote 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/codeinfinity1/stram/meeting-follow-up)<a href="https://agentmods.dev/skills/codeinfinity1/stram/meeting-follow-up"><img src="https://agentmods.dev/badge/skills/codeinfinity1/stram/meeting-follow-up/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/codeinfinity1/stram/meeting-follow-up"><img src="https://agentmods.dev/badge/skills/codeinfinity1/stram/meeting-follow-up.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.00047 | $0.00597 |
| Opus 5.5 | $0.00019 | $0.00239 |
| Sonnet 5.5 | $0.00009 | $0.00119 |
| Haiku 4.5 | $0.00005 | $0.00060 |
Grade A, and why
meeting-follow-up 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.
How it starts
The opening of the file, as written. The whole thing — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Meeting Follow Up
Purpose
Turn meeting outcomes into concrete next actions without losing approval boundaries. This skill connects meeting evidence to Stram commitments, wakeups, notes, documents, and channel tools.
When To Use
Use after a meeting summary, call transcript, standup, planning conversation, or when the user asks to send follow-ups or track meeting action items.
Inputs And Evidence
- Meeting summary or transcript.
- Extracted action items, owners, dates, blockers, and open questions.
- Existing commitments and channel setup status.
- User instructions about which follow-ups to send or record.
Tool Map
meeting_followup_packet_createwriting_draft_createwriting_draft_inspectcognitive_commitment_recordcognitive_commitment_updatecognitive_trigger_recordchannel_message_preparewrite_notememory_writevoice_response_prepare
Workflow
- Start from verified meeting evidence, not memory alone.
- Separate internal tracking from external-visible follow-ups.
- Create a durable unsent follow-up packet with
meeting_followup_packet_createwhen there are multiple actions, reminders, or draft messages. - Record tasks or reminders only for explicit action items or user-approved follow-ups.
- Draft messages with
channel_message_prepare; do not send without approval and configured channel support. - Create notes or documents when the user wants a durable record.
- End with a clear checklist of recorded, drafted, and still-unconfirmed items.
Safety
- Do not send messages, emails, or channel replies automatically.
- Do not assign tasks to people unless meeting evidence or user instruction supports it.
- Do not use upstream meeting pipeline code as implementation.
Native Implementation Boundaries
- Use
meeting_followup_packet_createfor the local durable follow-up plan before drafting or recording multiple actions. - Use
writing_draft_create,channel_message_prepare, and commitment tools as native implementations; external-visible sends remain approval-gated. - Treat upstream meeting pipelines as reference patterns only, never as imported runtime dependencies.
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 · 74 lines · 47 tokens per session scan A 2798c1a57e32
meeting-follow-up is a skill published in the GitHub repository CodeInfinity1/Stram (11 stars, last pushed 2mo ago), licensed MIT. It adds 47 tokens to every session and 597 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-03.
Other skills, from other repositories
leadership
Executive leadership expertise for decision-making, change management, crisis management, stakeholder management, team building, and organizational leadership. Use when leading teams, managing change, navigating crises, or developing leadership skills.
product-management
Product management expertise for product strategy, roadmap planning, feature prioritization (RICE, ICE, MoSCoW), customer research, A/B testing, product analytics, and product-market fit. Use when building product roadmaps, prioritizing features, or defining product strategy.
init-project
Bootstrap a new research project. Interview for details, scaffold directory structure, create Overleaf symlink, initialise git, and create project context files.
shared-monorepo-turborepo
Turborepo, workspaces, package architecture, @repo/ naming, exports, tree-shaking.
setup
Interactive onboarding that discovers team structure, terminology, development goals, performance and management frameworks, organizational values, and ways of working by crawling Slack, Notion, Google Drive, Gmail, and Calendar. Validates everything with the manager before persisting. Run this first before using any…
workspace
Scaffold and manage the stateless AI workspace — context, packs, repos, and knowledge for multi-repo orchestration.