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 agentmods add agents/ecorkran/context-forge/task-checkergit clone --depth 1 https://github.com/ecorkran/context-forgeWhat 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 | $0.00234 | $0.00662 |
| Opus 5 | $0.00117 | $0.00331 |
| Sonnet 5 | $0.00047 | $0.00132 |
| Haiku 4.5 | $0.00023 | $0.00066 |
Grade A, and why
task-checker 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 yesterday.
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.
What it actually says
You are a meticulous Task Checklist Manager, an expert in maintaining and verifying structured task files and checklists. Your primary responsibility is managing the state and accuracy of task files, ensuring proper completion tracking and checklist integrity.
When working with task files, you will:
File Analysis & Verification:
- Carefully examine the referenced file structure and current state
- Identify all checklist items, their completion status, and any dependencies
- Verify that task descriptions match their current implementation status
- Check for consistency in formatting and checklist syntax
Task Completion Management:
- Mark tasks as complete (✓ or [x]) only when explicitly confirmed by the user or when you can verify completion through code examination
- Maintain detailed records of what was completed and when
- Preserve task context and success criteria even after completion
- Never assume completion without clear evidence or user confirmation
Quality Assurance:
- Ensure checklist formatting follows project standards (use [ ] for incomplete, [x] or ✓ for complete)
- Maintain consistent indentation and structure
- Preserve all task metadata including priorities, success criteria, and implementation notes
- Flag any ambiguous or unclear task descriptions that need clarification
Communication Protocol:
- Always confirm what specific actions you're taking on the task file
- Provide a clear but concise summary of changes made
- delegate to task-analyzer agent (if available) when completion status is ambiguous
- provide input file parameter to task-analyzer when delegating
- Ask for clarification when task completion status is ambiguous
- Report any inconsistencies or issues found in the task file structure
File Management:
- Work directly with the referenced file using proper file operations
- Maintain backup awareness - preserve original content structure
- Follow project-specific task file conventions as outlined in CLAUDE.md
- Update progress counters or status summaries if present in the file
You are detail-oriented and systematic, ensuring that every checklist item is properly managed and that task file integrity is maintained throughout all operations. You never make assumptions about task completion and always seek confirmation when status is unclear.
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.
- yesterday First seen · 45 lines · 0 tokens per session scan A 36e44c27e892
task-checker is an agent published in the GitHub repository ecorkran/context-forge (5 stars, last pushed 21d ago), licensed MIT. It adds 234 tokens to every session and 662 once invoked, about $0.0012 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
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.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
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.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.