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/NikiforovAll/claude-code-rulesWrote 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/nikiforovall/claude-code-rules/tasks-agent)<a href="https://agentmods.dev/agents/nikiforovall/claude-code-rules/tasks-agent"><img src="https://agentmods.dev/badge/agents/nikiforovall/claude-code-rules/tasks-agent/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/nikiforovall/claude-code-rules/tasks-agent"><img src="https://agentmods.dev/badge/agents/nikiforovall/claude-code-rules/tasks-agent.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.02074 |
| Opus 5.5 | $0.00007 | $0.00830 |
| Sonnet 5.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 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 — 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.
- 1mo 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 15d 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.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
portfolio-surveyor
Read-only portfolio surveyor for the Agentic Engineer. Runs the cheap live-state survey across exactly the repositories the consuming deployment's Portfolio map names and returns ONE compact, fixed-shape digest of operate and advance signals — breakage, per-PR hygiene, review-lane state, triage, and roadmap state …
agentic-engineer
Autonomous primary engineer for a whole portfolio of repositories — not just upkeep, but ownership of each product's direction, growth, and running cost. Each run it surveys every in-scope product's live state, then OPERATES the portfolio (hotfixes breakage, drives trusted-author PRs to merge, triages, keeps…
project-manager
Roadmap steward that recommends what to work on next, decomposes pitches into epics, and tidies roadmap hygiene. Use when a user asks about roadmap, what to work on next, project status, what's in flight, sequence the backlog, decompose this pitch, break down this feature, what's blocked, show me the backlog…
Project Manager Agent
Meta-layer agent that orchestrates specialists and manages project knowledge.
sync-spec-kit-agent
Analyzes implementation changes on a feature branch and updates the spec-kit specification folder (.specify/specs/ /) to reflect the current state — new requirements, architecture changes, completed tasks, research findings, and any drift from the original specification. Context: User finished implementing something…
visual-fixer-page
Fixes visual issues on ONE page of a built website — starts its own dev server on an assigned port, inspects every section and element using Playwright DOM inspection, compares against the design document, and fixes all issues directly in the source files for that page only. Multiple instances run in parallel, each…