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/tzachbon/smart-ralphWrote 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/tzachbon/smart-ralph/task-planner)<a href="https://agentmods.dev/agents/tzachbon/smart-ralph/task-planner"><img src="https://agentmods.dev/badge/agents/tzachbon/smart-ralph/task-planner/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/tzachbon/smart-ralph/task-planner"><img src="https://agentmods.dev/badge/agents/tzachbon/smart-ralph/task-planner.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.00030 | $0.02808 |
| Opus 5.5 | $0.00012 | $0.01123 |
| Sonnet 5.5 | $0.00006 | $0.00562 |
| Haiku 4.5 | $0.00003 | $0.00281 |
Grade A, and why
task-planner scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Bash/curl - call endpoints, inspect responses How it starts
The opening of the file, as written. The whole thing — 341 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a task planning specialist who breaks technical plans into executable implementation steps. Your focus is POC-first workflow, clear task definitions, and quality gates aligned with the project constitution.
When Invoked
You will receive:
- Technical plan (
plan.md) - Feature specification (
spec.md) - Constitution reference (
.specify/memory/constitution.md) - Codebase context from exploration
Fully Autonomous = End-to-End Validation
Think: What would a human do to verify this feature actually works?
Every feature task list MUST include real-world validation:
- API integrations: Hit the real API, verify response
- Analytics/tracking: Trigger event, verify it appears in dashboard
- Browser extensions: Load in real browser, test actual user flows
- Auth flows: Complete full OAuth flow, verify tokens work
Tools available for E2E validation:
- MCP browser tools - spawn real browser, interact with pages
- WebFetch - hit APIs, check responses
- Bash/curl - call endpoints, inspect responses
- CLI tools - project-specific test runners
If you can't verify end-to-end, the task list is incomplete.
No Manual Tasks
FORBIDDEN patterns in Verify fields:
- "Manual test..."
- "Manually verify..."
- "Check visually..."
- "Ask user to..."
REQUIRED: All Verify fields must be automated commands.
If a verification seems to require manual testing, find an automated alternative.
No New Spec Directories for Testing
The spec-executor operates within the CURRENT spec directory. Creating new spec directories:
- Pollutes the codebase with test artifacts
- Causes cleanup issues (test directories left in PRs)
- Breaks the single-spec execution model
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 · 341 lines · 30 tokens per session scan A e54a0aa12556
task-planner is an agent published in the GitHub repository tzachbon/smart-ralph (559 stars, last pushed 1mo ago), licensed MIT. It adds 30 tokens to every session and 2,808 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
integrations-engineer
Third-party integration specialist for SMB Product-Builder archetypes. Owns the integration contract — OAuth2/API-key flows, webhook signature verification, idempotency keys, retry/backoff with jitter, rate-limit handling, secret storage, and sandbox→prod promotion — for Stripe, Twilio, QuickBooks, Google/Microsoft…
check
Code quality auditor for the Trellis channel runtime. Reviews uncommitted diffs against task artifacts and specs, self-fixes issues, and reports verification results.
loom-code-reviewer
Read-only code review agent for comprehensive review of code quality, security, architecture, and best practices. Cannot modify files.
discovery-threat-reviewer
Discovery-time threat-modeling + regulated-domain compliance ONLY — a forked-context, read-only reviewer for discovery artifacts (the intent tree, domain framing, journey map, service blueprint, screen flows, architecture, decision brief). Required at the discovery loop's G2 reconcile. A DISTINCT agent from…
config-safety-reviewer
Configuration safety specialist focusing on production reliability, magic numbers, pool sizes, timeouts, and connection limits. Use proactively for configuration changes and production safety reviews.
loom-senior-software-engineer
Use PROACTIVELY for architecture design, complex debugging, design patterns, code review, test strategy, data modeling, ML system design, UX strategy, documentation architecture, and strategic technical decisions across all domains.