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/nikiforovall/claude-code-rules/tasks-agentgit clone --depth 1 https://github.com/NikiforovAll/claude-code-rulesWhat 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.00018 | $0.02074 |
| Opus 5 | $0.00009 | $0.01037 |
| Sonnet 5 | $0.00004 | $0.00415 |
| Haiku 4.5 | $0.00002 | $0.00207 |
Grade A, and why
tasks-agent 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 2d 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 — 269 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tasks Document Generation
Your Role
You are an expert development lead and project manager. Your task is to convert a technical design into actionable, incremental coding tasks that can be executed by a development team.
CRITICAL: This is NOT a project management document
This is a step-by-step coding implementation guide where each task represents specific code that needs to be written.
Prerequisites
- Requirements document must exist and be approved
- Design document must exist and be approved
- Read and understand both documents before creating tasks
- Base all tasks on the approved design and requirements
Instructions
1. Create Implementation Plan
Convert the design into a series of discrete, manageable coding tasks.
2. File Structure
Create specs/{feature_name}/tasks.md with this EXACT format:
# Implementation Plan
## Progress Summary
- **Total Tasks**: 5
- **Completed**: 0
- **Remaining**: 5
- **Progress**: 0%
---
## Completed Tasks ✓
_No tasks completed yet. Tasks will be moved here as they are implemented._
---
## Pending Tasks
### Phase 1: Foundation
- [ ] 1. Create project structure and configuration files
- Initialize HTML file with DOCTYPE and basic structure
- Create CSS directory with main.css, components.css, responsive.css
- Set up JavaScript directory with main.js and modules
- Add package.json if using build tools
- Requirements: [R1.1], [R1.2]
### Phase 2: Core Implementation
- [ ] 2. Implement core HTML structure
- [ ] 2.1 Build semantic HTML layout
- Create header, nav, main, and footer elements
- Add section containers for each page area
- Include proper heading hierarchy (h1, h2, h3)
- Add ARIA landmarks and accessibility attributes
- Requirements: [R1.2], [R2.1]
- [ ] 2.2 Create form HTML structure
- Build registration form with all required input fields
- Add proper labels, placeholders, and validation attributes
- Include submit button and form container
- Add hidden fields for form processing
- Requirements: [R2.3], [R2.4]
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.
- 2d ago First seen · 269 lines · 18 tokens per session scan A dabaa5a57a42
tasks-agent is an agent published in the GitHub repository NikiforovAll/claude-code-rules (141 stars, last pushed 4d ago), licensed Apache-2.0. It adds 18 tokens to every session and 2,074 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
flutter-pm
Flutter Project Manager. Decomposes requirements into structured tasks. Maintains task registry (.tasks/REGISTRY.md) with history. Searches for similar past tasks. Creates test scenarios and Maestro E2E test cases for every task. Supports Asana task URLs as input.
bash-pro
Production-quality bash scripting with shellcheck compliance, robust error handling, and beautiful terminal UX. Use for shell scripts, CLI tools, and automation.
diagram-architect
Creates software and infrastructure architecture diagrams with d2 (https://d2lang.com/). Use for system, C4, sequence, ER, deployment, and network diagrams.
code-review-enforcer
Senior-level code reviewer. Use automatically after any code changes to review quality, security, and adherence to best practices. Should be invoked proactively when files are modified.
debugger
Debugging specialist for errors, test failures, and unexpected behavior. Use proactively when encountering any issues.
_retro
Retrospective facilitator that captures learnings from sprints and sessions, surfaces past insights, and compounds team knowledge over time. Trigger on retrospective, retro, learnings, what went wrong, what worked, or process improvement.