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 commands/khanh-vu/claude-force/new-taskgit clone --depth 1 https://github.com/khanh-vu/claude-forceWrote 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/khanh-vu/claude-force/new-task)<a href="https://agentmods.dev/commands/khanh-vu/claude-force/new-task"><img src="https://agentmods.dev/badge/commands/khanh-vu/claude-force/new-task.svg" alt="Measured on agentmods" 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 | $0.00006 | $0.00564 |
| Opus 5 | $0.00003 | $0.00282 |
| Sonnet 5 | $0.00001 | $0.00113 |
| Haiku 4.5 | $0.00001 | $0.00056 |
Grade A, and why
new-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 4d 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
New Task Command
Initialize a new task in .claude/task.md using the standard template.
Process
- Read the task template from
.claude/task.md - If task.md already has content, archive it
- Create new task.md with template structure
- Prompt for key information:
- Task title
- Objective
- Priority (High/Medium/Low)
- Type (Feature/Bug Fix/Refactor/Documentation)
- Fill in template with provided information
- Leave other sections for user to complete
Template Structure
The generated task will include:
- Objective: Clear goal statement
- Requirements: Functional, non-functional, technical
- Context: Background, assumptions, constraints
- Acceptance Criteria: Specific, measurable criteria
- Scope: What's in and out of scope
- Resources: Links to designs, docs, data
- Deliverables: Expected outputs
- Success Metrics: How to measure success
- Workflow: Suggested agent sequence
- Risk Assessment: Potential risks and mitigations
- Timeline: Estimated phases and duration
Interactive Mode
/new-task
> Task title: Build Product Catalog UI
> Priority: High
> Type: Feature
> Brief objective: Create responsive product catalog with filters
✅ Created new task in .claude/task.md
📝 Please complete remaining sections before running agents
Quick Mode
/new-task --quick --title "Add search feature" --type Feature
Archive Previous Task
If .claude/task.md exists:
📦 Archived previous task to .claude/archives/task-2025-11-13.md
✅ Created new task.md
Next Steps After Creation
- Complete all task sections
- Review acceptance criteria
- Select appropriate workflow
- Run first agent:
/run-agent <agent-name>
Example Generated Task
# Task: Build Product Catalog UI
**Created**: 2025-11-13
**Owner**: [Your Name]
**Priority**: High
**Type**: Feature
## Objective
Create responsive product catalog with filters
[... rest of template ...]
Options
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.
- 4d ago First seen · 98 lines · 6 tokens per session scan A 38daa614adfe
new-task is a command published in the GitHub repository khanh-vu/claude-force (5 stars, last pushed 9mo ago), licensed MIT. It adds 6 tokens to every session and 564 once invoked, about $0.0000 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.