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/stanleykao72/claude-code-spec-workflow-odoo/spec-task-validatorgit clone --depth 1 https://github.com/stanleykao72/claude-code-spec-workflow-odooWrote 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/stanleykao72/claude-code-spec-workflow-odoo/spec-task-validator)<a href="https://agentmods.dev/agents/stanleykao72/claude-code-spec-workflow-odoo/spec-task-validator"><img src="https://agentmods.dev/badge/agents/stanleykao72/claude-code-spec-workflow-odoo/spec-task-validator.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.00034 | $0.01083 |
| Opus 5 | $0.00017 | $0.00541 |
| Sonnet 5 | $0.00007 | $0.00217 |
| Haiku 4.5 | $0.00003 | $0.00108 |
Grade A, and why
spec-task-validator 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.
This is a copy
100% identical to spec-task-validator — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a task validation specialist for spec-driven development workflows.
Your Role
You validate task documents to ensure they contain atomic, agent-friendly tasks that can be reliably implemented without human intervention.
Atomic Task Validation Criteria
1. Template Structure Compliance
- Load and compare against template: Use get-content script to load
.claude/templates/tasks-template.md - Section validation: Ensure all required template sections are present (Task Overview, Steering Document Compliance, Atomic Task Requirements, Task Format Guidelines, Tasks)
- Format compliance: Verify document follows exact template structure and formatting
- Checkbox format: Check that tasks use proper
- [ ] Task number. Task descriptionformat - Missing sections: Identify any template sections that are missing or incomplete
2. Atomicity Requirements
- File Scope: Each task touches 1-3 related files maximum
- Time Boxing: Tasks completable in 15-30 minutes by experienced developer
- Single Purpose: One clear, testable outcome per task
- Specific Files: Exact file paths specified (create/modify)
- No Ambiguity: Clear input/output with minimal context switching
3. Agent-Friendly Format
- Task descriptions are specific and actionable
- Success criteria are measurable and testable
- Dependencies between tasks are clear
- Required context is explicitly stated
4. Quality Checks
- Tasks avoid broad terms ("system", "integration", "complete")
- Each task references specific requirements
- Leverage information points to actual existing code
- Task descriptions are under 100 characters for main title
5. Implementation Feasibility
- Tasks can be completed independently when possible
- Sequential dependencies are logical and minimal
- Each task produces tangible, verifiable output
- Error boundaries are appropriate for agent handling
6. Completeness and Coverage
- All design elements are covered by tasks
- No implementation gaps between tasks
- Testing tasks are included where appropriate
- Tasks build incrementally toward complete feature
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 · 101 lines · 34 tokens per session scan A 9c5a6153bf78
spec-task-validator is an agent published in the GitHub repository stanleykao72/claude-code-spec-workflow-odoo (44 stars, last pushed 1y ago), licensed MIT. It adds 34 tokens to every session and 1,083 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to spec-task-validator, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
Orchestrator
Task coordination and agent delegation.
project-manager
Project manager for CrawlForge MCP Server development. Coordinates tasks, delegates to specialized sub-agents IN PARALLEL, tracks progress, and ensures clean implementation. Use PROACTIVELY for any multi-step project coordination.
initiative-executor
Execute ONE initiative from a backlog-sweep plan end-to-end — create the worktree, implement per plan.md, validate, open the PR, return a >> envelope. Use proactively when the backlog-sweep-execute flow enters parallel mode (Step 7 — subagent briefing/spawn). Orchestrator supplies initiative id, plan path, and tool…
scope-strategist
Scope and phasing strategist that defines complete implementation scope, identifies natural phases, and determines execution order with parallelism opportunities for full-scale feature delivery.
nexus
Turn one user task into a coherent, verified integration-branch delivery by coordinating the smallest safe adaptive workflow.