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/penwyp/ClaudePreferenceWrote 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/commands/penwyp/claudepreference/m-next-task)<a href="https://agentmods.dev/commands/penwyp/claudepreference/m-next-task"><img src="https://agentmods.dev/badge/commands/penwyp/claudepreference/m-next-task/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/commands/penwyp/claudepreference/m-next-task"><img src="https://agentmods.dev/badge/commands/penwyp/claudepreference/m-next-task.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.00000 | $0.00733 |
| Opus 5.5 | $0.00000 | $0.00293 |
| Sonnet 5.5 | $0.00000 | $0.00147 |
| Haiku 4.5 | $0.00000 | $0.00073 |
Grade A, and why
m-next-task 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.
How it starts
The opening of the file, as written. The whole thing — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Next Tasks Workflow: Analyze Status & Plan Actions
Target: $ARGUMENTS (Default: medium priority if none specified)
Scope: Analyze current development status and generate prioritized action plan
Execution Steps
-
Documentation & Tracker Scan
- Inspect development tracking files (
docs/dev*.md,TODO.md, etc.) - Extract pending tasks and action items
- Review project roadmap and milestone documents
- Inspect development tracking files (
-
Git History Analysis
- Parse recent commits for TODO markers and incomplete work
- Identify new changes requiring follow-up actions
- Detect unfinished features or partial implementations
-
Task Status Assessment
- Evaluate current task completion status
- Identify blocking dependencies and prerequisites
- Assess resource availability and constraints
-
Priority Ranking
- Rank tasks based on specified priority level or default medium
- Consider business impact, technical debt, and dependencies
- Balance feature development with maintenance tasks
-
Reference Collection
- Gather relevant files, commits, and documentation
- Identify helpful discussions and decision records
- Compile supporting materials for task execution
-
Generate Next Tasks Report
- Compile findings into structured markdown format
- Save to
docs/workspaces/next-tasks-MM-dd-HH-mm-ss.md
Output Format
English Report
summary
- Concise overview of current development status
- Key context and recent progress highlights
- Overall project health and momentum assessment
tasks
Prioritized task list with structure:
{
"id": "string",
"description": "string",
"priority": "high|medium|low",
"status": "pending|blocked|in-progress",
"dependencies": ["task_id_1", "task_id_2"]
}
references
- Relevant files and documentation links
- Related commits and pull requests
- Helpful discussions and decision records
- External resources and documentation
clarifications
Questions for requirement or implementation ambiguities:
- Unclear priorities or scope boundaries
- Missing technical specifications
- Resource allocation and timeline concerns
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.
- 1mo ago First seen · 109 lines · 0 tokens per session scan A a739be14acae
m-next-task is a command published in the GitHub repository penwyp/ClaudePreference (136 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 733 tokens. 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 commands, from other repositories
template
Manage issue templates for streamlined issue creation.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
add-note
Add an internal or external note to a ConnectWise PSA ticket.
sync-linear
Sync current work with Linear ticket status.
dispatcher
Use when you want the orchestrator to pick the next repo to work on across your whole portfolio — it enumerates candidate repos below the confinement root, resolves free/busy from each repo's session.lock lease, ranks the FREE ones by backlog priority × staleness × readiness, recommends the single most worthwhile one…
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.