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 genudo-ai/genudo_mcp --skill stage-followupsgit clone --depth 1 https://github.com/genudo-ai/genudo_mcpWrote 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/genudo-ai/genudo_mcp/stage-followups)<a href="https://agentmods.dev/skills/genudo-ai/genudo_mcp/stage-followups"><img src="https://agentmods.dev/badge/skills/genudo-ai/genudo_mcp/stage-followups/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/genudo-ai/genudo_mcp/stage-followups"><img src="https://agentmods.dev/badge/skills/genudo-ai/genudo_mcp/stage-followups.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.00045 | $0.00732 |
| Opus 5.5 | $0.00018 | $0.00293 |
| Sonnet 5.5 | $0.00009 | $0.00146 |
| Haiku 4.5 | $0.00005 | $0.00073 |
Grade A, and why
genudo-stage-followups 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 22d 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GenuDo Stage Follow-up Sequences
Overview
Guidelines for creating and modifying automated re-engagement sequences when leads go quiet within a specific pipeline stage. Follow-ups allow the agent to reach back out after specified elapsed time intervals with context-aware, value-first messaging.
Key Tools
| Purpose | MCP Tool |
|---|---|
| Check existing stage follow-up configuration | get_stage_followup |
| Create a new follow-up sequence for a stage | create_followup |
| Update an existing follow-up sequence | update_followup |
Architecture of a Follow-up Sequence
Each pipeline stage holds at most one follow-up sequence. A sequence consists of:
- Intervals: The timed schedule of when each message fires after the contact becomes inactive.
- Format: Array of objects
{ interval_value: 1–100, interval_unit: "minute" | "hour" | "day" | "week" | "month" }. - Example: First message at 10 hours, second at 24 hours, third at 3 days.
- Format: Array of objects
- Drafting Instructions: Guidance for how the AI dynamically composes the follow-up message (e.g., "Reference the plan discussed previously, ask if they had questions regarding setup").
- Assets: Optional media or resources attached to messages (brochures, demo videos, scheduling links).
after_followup_stage_id: Optional stage to automatically move the opportunity to when all follow-up attempts are exhausted without a reply (e.g., transitioning to a "Cold Leads" or "Closed Lost" stage).
Step-by-Step Workflow
1. Check Existing Configuration
Always run get_stage_followup with the target stage_id:
- If a sequence exists, capture the
followup_idfor use withupdate_followup. - If no sequence exists, prepare to call
create_followup.
2. Design the Sequence
Collaborate with the user to establish:
- Realistic intervals that avoid spamming (e.g., 6 hours, 24 hours, 72 hours).
- Distinct angles for each follow-up message:
- Follow-up 1: Gentle check-in / question clarification.
- Follow-up 2: Value add (case study, testimonial, or brief tip).
- Follow-up 3: Soft breakup or alternative contact option.
- Expiration action: specify
after_followup_stage_idor leavenull.
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.
- 22d ago First seen · 61 lines · 45 tokens per session scan A 3beae8aa63b2
genudo-stage-followups is a skill published in the GitHub repository genudo-ai/genudo_mcp (0 stars, last pushed 6d ago), licensed MIT. It adds 45 tokens to every session and 732 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-25.
Other skills, from other repositories
sdlc-accelerate
End-to-end SDLC ramp-up from idea to construction-ready with automated phase transitions.
ralph-memory
Manage Al semantic memory entries — list, query, and clear lessons learned across loop iterations.
config-validator
Validate AIWG configuration files and project setup for correctness and completeness.
project-awareness
Detect project type, AIWG framework state, team configuration, and active work to summarize status and recommend next actions.
summarize-transcript
Analyze and summarize a transcript, meeting notes, or discussion thread into a clear actionable document.
validate-addon
Validate an entire AIWG addon package for completeness and release readiness.