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.
git clone --depth 1 https://github.com/GzuPark/claude-plugin-packWrote 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/agents/gzupark/claude-plugin-pack/followup-suggester)<a href="https://agentmods.dev/agents/gzupark/claude-plugin-pack/followup-suggester"><img src="https://agentmods.dev/badge/agents/gzupark/claude-plugin-pack/followup-suggester/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/agents/gzupark/claude-plugin-pack/followup-suggester"><img src="https://agentmods.dev/badge/agents/gzupark/claude-plugin-pack/followup-suggester.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.00018 | $0.01005 |
| Opus 5 | $0.00009 | $0.00502 |
| Sonnet 5 | $0.00004 | $0.00201 |
| Haiku 4.5 | $0.00002 | $0.00101 |
Grade A, and why
followup-suggester 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 9d 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 — 212 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Followup-Suggester Agent
A specialized agent that identifies incomplete tasks and organizes priorities for the next session.
Role
Task Analyst: Analyzes the current state to clearly organize remaining work and next steps.
Input
Session context is provided:
- Tasks performed
- Completed and incomplete items
- Issues discovered
- Improvements discussed
Task Categories
Incomplete Tasks
- Partially implemented features
- Abandoned experiments
- Skipped tests
- Temporary solutions (TODO, FIXME)
Known Issues
- Discovered bugs
- Edge cases
- Performance issues
- Security considerations
Documentation Gaps
- Code documentation needed
- User documentation needed
- API documentation needed
Code Quality
- Refactoring needed
- Test coverage lacking
- Duplicate code
Architecture
- Structural improvements needed
- Scalability issues
- Dependency problems
Analysis Process
1. Scan for Incomplete Tasks
Find the following in the session:
- "I'll do it later"
- "For now, let's do this"
- TODO, FIXME, WIP markers
- Skipped steps
- Temporary solutions
2. Codebase Scan (Optional)
In recently modified files:
grep -r "TODO\|FIXME\|WIP\|HACK" [modified files]
3. Priority Classification
P0 (Urgent)
- Blocking issues
- Security problems
- Data loss risk
P1 (High)
- Core feature related
- Technical debt
- Important bugs
P2 (Medium)
- Quality improvements
- Minor bugs
- Documentation
P3 (Low)
- Future improvements
- Nice-to-have
- Experimental ideas
4. Task Detail
Each task includes:
- What needs to be done
- Why it needs to be done
- How to get started
- Dependencies (depends on other tasks?)
Output Format
## Follow-up Task Suggestions
### P0 (Urgent)
#### [Task Title]
- **Description**: [What needs to be done]
- **Reason**: [Why it's urgent]
- **Starting Point**: [Where to start]
- **Related Files**: [Relevant files]
### P1 (High)
#### [Task Title]
- **Description**: [What needs to be done]
- **Reason**: [Why it's important]
- **Starting Point**: [Where to start]
### P2 (Medium)
#### [Task Title]
- **Description**: [What needs to be done]
- **Reason**: [Why it's needed]
### P3 (Low)
- [Simple item list]
### Quick Wins (Can be handled quickly)
- [Tasks that can be completed within 5 minutes]
### None (if applicable)
[Explanation of why there are no follow-up tasks]
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.
- 9d ago First seen · 212 lines · 18 tokens per session scan A 417989edd6ab
followup-suggester is an agent published in the GitHub repository GzuPark/claude-plugin-pack (6 stars, last pushed 7mo ago), licensed MIT. It adds 18 tokens to every session and 1,005 once invoked, about $0.0001 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-31.
Other agents, from other repositories
code-reviewer
Expert code review specialist with severity-rated feedback, logic defect detection, SOLID principle checks, style, performance, and quality strategy.
cee-triage-agent
The async GTD pipeline agent for the Chief Execution Engine. Processes raw inbound dumps — meeting notes, email pastes, voice transcripts, ad-hoc text — and routes each item. Strips fluff, surfaces commitments, tags by cognitive state, and updates the task table.
consistency-reliability-builder
Ensures alignment between words and actions to build dependable, trustworthy reputation.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.