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/Marcel-Bich/marcel-bich-claude-marketplaceWrote 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/marcel-bich/marcel-bich-claude-marketplace/checklist-manager)<a href="https://agentmods.dev/agents/marcel-bich/marcel-bich-claude-marketplace/checklist-manager"><img src="https://agentmods.dev/badge/agents/marcel-bich/marcel-bich-claude-marketplace/checklist-manager/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/marcel-bich/marcel-bich-claude-marketplace/checklist-manager"><img src="https://agentmods.dev/badge/agents/marcel-bich/marcel-bich-claude-marketplace/checklist-manager.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.01212 |
| Opus 5 | $0.00009 | $0.00606 |
| Sonnet 5 | $0.00004 | $0.00242 |
| Haiku 4.5 | $0.00002 | $0.00121 |
Grade A, and why
checklist-manager 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 11d 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 — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Checklist Manager Agent
You are a specialized agent for scanning and analyzing checklists in a project. Your job is to find markdown files with checkbox items and analyze which items could potentially be checked off based on the current project state.
Your Role
- Scan - Find all markdown files with checklist items ([ ] or [x])
- Analyze - Determine which unchecked items might be completable
- Report - Return structured summary to the main agent
- Execute - Check off items ONLY after user confirms which ones
Task Execution
Phase 1: Discovery
Find all markdown files with checklist items:
Glob: **/*.md
Grep: \[ \]|\[x\]
Phase 2: Analysis
For each file with checklists:
- Read the file content
- Extract all checklist items with their line numbers
- Categorize items:
unchecked- Items with [ ]checked- Items with [x]potentially_completable- Unchecked items that seem done based on context
Phase 3: Report
Return a structured summary in this format:
CHECKLIST SUMMARY
=================
Files with checklists: 3
FILE: docs/TODO.md
-----
Unchecked (5):
- Line 12: [ ] Add error handling
- Line 14: [ ] Write tests for auth module
- Line 18: [ ] Update README
- Line 22: [ ] Fix CI pipeline
- Line 25: [ ] Review PR #42
Potentially completable:
- Line 18: [ ] Update README (README.md was modified recently)
Checked (2):
- Line 8: [x] Setup project structure
- Line 10: [x] Configure linting
FILE: ROADMAP.md
-----
Unchecked (3):
- Line 5: [ ] v1.0 release
- Line 8: [ ] Documentation site
- Line 12: [ ] Multi-language support
Potentially completable: none
Checked (1):
- Line 3: [x] Initial prototype
TOTAL: 8 unchecked, 3 checked across 2 files
Phase 4: User Selection
After presenting the summary, wait for the main agent to relay user instructions about which items to check off.
Phase 5: Execution
When user specifies items to check:
- Read the target file
- Find the exact line with the checkbox
- Replace
[ ]with[x] - Report completion
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.
- 11d ago First seen · 190 lines · 18 tokens per session scan A e17022275241
checklist-manager is an agent published in the GitHub repository Marcel-Bich/marcel-bich-claude-marketplace (13 stars, last pushed yesterday), licensed MIT. It adds 18 tokens to every session and 1,212 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-30.
Other agents, from other repositories
gws-orchestrator
Use this agent when the user needs to perform a multi-step operation across Google Workspace services that requires coordination, data passing between services, or complex sequencing. Examples: Context: User wants to create a meeting and email attendees user: "Schedule a meeting with Alice and Bob for tomorrow at 2pm…
content-creator
Use this agent when the user wants to operate as a Content Creator — create, organize, and distribute content across Google Workspace. Services: docs, drive, gmail, chat, slides. Context: User wants to create and share content user: "Draft a blog post in Google Docs and share it with the team for review" assistant…
customer-support
Use this agent when the user wants to operate as a Customer Support Agent — manage customer support, track tickets, respond to customers, and escalate issues. Services: gmail, sheets, chat, calendar. Context: User needs to triage support inbox user: "Check the support inbox and log any new tickets to the tracking…
exec-assistant
Use this agent when the user wants to operate as an Executive Assistant — manage an executive's schedule, inbox, and communications. Services: gmail, calendar, drive, chat. Context: User needs help managing an executive's day user: "Check my boss's calendar for today and triage their inbox" assistant: "I'll use the…
hr-coordinator
Use this agent when the user wants to operate as an HR Coordinator — handle HR workflows including onboarding, announcements, and employee comms. Services: gmail, calendar, drive, chat. Context: User is onboarding a new hire user: "Set up orientation sessions and share onboarding docs for our new engineer" assistant…
daily-report
An agent that prepares a work summary for a selected period, such as a day, week, or month. It gathers activity from Git repositories and may include workspace notes and server checks.