follow-up

follow-up is a skill for Claude Code from etrebels/claude-code-growth-os. It costs 38 tokens per session (233 once invoked), scanned A, original, MIT.

A meeting debrief and follow-up drafting guide that turns notes or a recap into internal conclusions and a short message for the other people involved.

In plain words
What is it for?
Use it to identify decisions, commitments, risks, and next steps, then draft a follow-up with a subject line or a later reminder if someone stays silent.
Why use it?
It removes the guesswork after a meeting by separating decisions and commitments from the message you need to send. It also helps avoid vague check-ins and unsupported claims.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

Good fit Use it to identify decisions, commitments, risks, and next steps, then draft a follow-up with a subject line or a later reminder if someone stays silent.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/etrebels/claude-code-growth-os/follow-up
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 etrebels/claude-code-growth-os --skill follow-up
Clone the repo
git clone --depth 1 https://github.com/etrebels/claude-code-growth-os

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 follow-up

README.md
[![agentmods](https://agentmods.dev/badge/skills/etrebels/claude-code-growth-os/follow-up/github.svg)](https://agentmods.dev/skills/etrebels/claude-code-growth-os/follow-up)
Your own site
<a href="https://agentmods.dev/skills/etrebels/claude-code-growth-os/follow-up"><img src="https://agentmods.dev/badge/skills/etrebels/claude-code-growth-os/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.

agentmods 80×15 button for follow-up

Your own site · 80×15
<a href="https://agentmods.dev/skills/etrebels/claude-code-growth-os/follow-up"><img src="https://agentmods.dev/badge/skills/etrebels/claude-code-growth-os/follow-up.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 38 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 233 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.00038 $0.00233
Opus 5 $0.00019 $0.00117
Sonnet 5 $0.00008 $0.00047
Haiku 4.5 $0.00004 $0.00023

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

Security

Grade A, and why

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 8d 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/skills/follow-up/SKILL.md · 19 lines

What it actually says

Debrief & Follow-up

From a meeting note (point me at one in ops/ or demo/meetings/) or a pasted recap:

  1. Debrief (for you): decisions made, commitments — yours and theirs — and any new risk or signal. Offer to append it to ops/daily-log.md.
  2. Follow-up (for them): lead with the commitment you made or the decision they owe — not "just checking in". One clear next step with a date. Keep it short; a follow-up that needs scrolling doesn't get read.

Don't invent facts the note doesn't contain. Bring your own voice; this drafts the structure.

Depth

  • quick: the follow-up message only.
  • standard: debrief notes + the message + a subject line.
  • deep: + a second nudge for if they go quiet, with the date to send it.
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. 8d ago First seen · 19 lines · 38 tokens per session scan A ae1d31ed1a15

Subscribe to this mod's changes

follow-up is a skill published in the GitHub repository etrebels/claude-code-growth-os (20 stars, last pushed 2d ago), licensed MIT. It adds 38 tokens to every session and 233 once invoked, about $0.0002 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-08-30.

Related

Other skills, from other repositories

leadmagic-cli

Use the LeadMagic CLI for enrichment automation — find emails, validate contacts, enrich CSVs in batch, find decision-makers by role, and push to outbound platforms (Smartlead, Instantly). Use when automating enrichment from the command line, batch-processing contacts, or integrating LeadMagic into scripts. Triggers…

LeadMagic/gtm-skills · 99 tokens

revenue-team-onboarding

Revenue team onboarding — security access provisioning, ramp schedules, 30-60-90 plans, Slack engagement, shadowing, certification, and time-to-first-meeting reduction. Use when onboarding SDRs, AEs, managers, or RevOps hires. Triggers on: "sales onboarding", "SDR ramp", "30-60-90 sales", "reduce ramp time", "Slack…

LeadMagic/gtm-skills · 104 tokens

team-management

Team management for startup leaders — 1:1s, performance reviews, goal setting (OKRs), delegation, feedback culture, remote team management, team rituals, and scaling from IC to manager. Use when building team processes, managing first direct reports, or scaling management as the company grows. Triggers on: "team…

LeadMagic/gtm-skills · 95 tokens

marketing-loops

When the user wants to set up a recurring, self-running marketing workflow — a repeatable loop an AI agent runs on a cadence (weekly, daily, on a trigger) rather than a one-off task. Also use when the user mentions 'marketing loop,' 'recurring marketing workflow,' 'automate my marketing,' 'marketing on autopilot,'…

coreyhaines31/marketingskills · 158 tokens

engagement-inbox-manager

Use when the user asks to "triage our comments, DMs, and mentions", "draft replies to this thread", "can we repost this fan post", or "set up inbox SLAs and an escalation path"; produces a ranked triage queue with register detection (sincere / ironic / performative / parasocial, sentiment-inversion table included …

aaron-he-zhu/aaron-marketing-skills · 216 tokens

automations

Schedule or manage recurring and one-shot BB agent or script automations.

get-bb/bb · 17 tokens