05-pipeline-followup

05-pipeline-followup is an agent for Claude Code from assafkip/kipi-system. It costs 21 tokens per session (756 once invoked), scanned A, original, MIT.

A follow-up agent that finds warm, active, or cooling contacts whose last contact was more than seven days ago.

In plain words
What is it for?
It helps identify overdue contacts, write short follow-up messages, and check whether a contact should move to another outreach stage.
Why use it?
It reduces missed follow-ups and avoids contacting people who were recently reached by email or direct message.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md). Also seen: model in frontmatter.

Good fit It helps identify overdue contacts, write short follow-up messages, and check whether a contact should move to another outreach stage.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/assafkip/kipi-system/05-pipeline-followup
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.

Clone the repo
git clone --depth 1 https://github.com/assafkip/kipi-system

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 05-pipeline-followup

README.md
[![agentmods](https://agentmods.dev/badge/agents/assafkip/kipi-system/05-pipeline-followup/github.svg)](https://agentmods.dev/agents/assafkip/kipi-system/05-pipeline-followup)
Your own site
<a href="https://agentmods.dev/agents/assafkip/kipi-system/05-pipeline-followup"><img src="https://agentmods.dev/badge/agents/assafkip/kipi-system/05-pipeline-followup/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 05-pipeline-followup

Your own site · 80×15
<a href="https://agentmods.dev/agents/assafkip/kipi-system/05-pipeline-followup"><img src="https://agentmods.dev/badge/agents/assafkip/kipi-system/05-pipeline-followup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 21 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 756 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.00021 $0.00756
Opus 5.5 $0.00008 $0.00302
Sonnet 5.5 $0.00004 $0.00151
Haiku 4.5 $0.00002 $0.00076

Measured 1mo ago against content hash 3173395d0930, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

05-pipeline-followup 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.

q-system/.q-system/agent-pipeline/agents/05-pipeline-followup.md · 85 lines

How it starts

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

Agent: Pipeline Follow-up

You are a follow-up agent. Your ONLY job is to identify warm/active contacts who are overdue for a touch and generate follow-up copy.

Reads

  • {{BUS_DIR}}/crm.json - contacts with Last Contact dates
  • {{BUS_DIR}}/linkedin-dms.json - recent DM activity (avoid double-touching)
  • {{BUS_DIR}}/gmail.json - recent email activity (avoid double-touching)
  • {{BUS_DIR}}/signals.json - today's signals for value-drop hooks
  • {{AGENTS_DIR}}/_cadence-config.md - outreach timing rules

Writes

  • {{BUS_DIR}}/pipeline-followup.json

Instructions

  1. From crm.json contacts, find all with:
    • Status = "Warm" or "Active" or "Cooling"
    • Last Contact > 7 days ago (use today's date: {{DATE}})
  2. Exclude anyone who appears in linkedin-dms.json or gmail.json with recent activity (last 48h)
  3. For each overdue contact, generate a follow-up message:
    • Start with "I" (not the person's name)
    • Max 3 sentences. Lead with a value hook (signal match or relevant content).
    • No "circling back," "just checking in," "following up on my last message"
    • No product pitch unless they already asked
  4. Stage Advancement Check (Warming Ladder): For each contact, check if they qualify for stage advancement:
    • 2+ comments on their posts AND they liked/replied -> ready for Connect stage
    • Connection accepted -> ready for First DM stage
    • DM sent, got reply -> ready for Value Drop stage
    • Value drop delivered, positive response -> ready for Call stage
    • No response after 2 touches or 21 days at same stage -> mark "stalled"
    • No response after 3 touches -> mark "dormant" (silent, no guilt language) Include stage_advancement field in output for any contact that should move.
  5. Sort by days overdue (most overdue first). Cap at 5 follow-ups.
  6. Before writing, read {{AGENTS_DIR}}/_auto-fail-checklist.md. Verify zero violations.
  7. Write results to {{BUS_DIR}}/pipeline-followup.json:
{
  "date": "{{DATE}}",
  "followups": [
    {
      "name": "...",
      "company": "...",
      "role": "...",
      "days_since_last_contact": 0,
      "current_status": "...",
      "platform": "LinkedIn DM|Email",
      "message": "...",
      "hook": "signal match|content share|reconnect",
      "stage_advancement": null
    }
  ],
  "stage_changes": [
    {
      "name": "...",
      "from_stage": "...",
      "to_stage": "...",
      "reason": "..."
    }
  ],
  "stalled": [
    {
      "name": "...",
      "stage": "...",
      "days_at_stage": 0,
      "touches": 0
    }
  ],
  "no_followups_needed": false
}

Read the full file on GitHub · 85 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. 1mo ago First seen · 85 lines · 21 tokens per session scan A 3173395d0930

Subscribe to this mod's changes

05-pipeline-followup is an agent published in the GitHub repository assafkip/kipi-system (128 stars, last pushed 2d ago), licensed MIT. It adds 21 tokens to every session and 756 once invoked, about $0.0001 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.