agentmods.dev

task-analyst

task-analyst is an agent for Claude Code from choiyounggi/dev-loop. It costs 0 tokens per session (1,312 once invoked), scanned A, a copy of task-analyst-r1, MIT.

A fresh-context coding agent that analyzes one development task and writes the analysis and its approval record for another planner to use. It performs only the analysis phase and does not implement the task.

In plain words
What is it for?
Use it to inspect a task, document its constraints and context, and prepare the analysis files needed before planning begins.
Why use it?
It gives the planner an independent, written understanding of the task instead of mixing analysis with design or coding. This can make the later plan easier to review.

Agent for Claude Code

Written for Claude Code: effort in frontmatter. Also seen: model in frontmatter.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the dev-loop plugin — 9 skills, 11 agents, 6 hooks, 1 MCP server shipped together

not rated 6repo +1 changed 8d ago A scan 0 tokens copy · 95% MIT

Good fit Use it to inspect a task, document its constraints and context, and prepare the analysis files needed before planning begins.

Compare 6 agents from other repositories ↓
View source ↗ choiyounggi/dev-loop
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add choiyounggi/dev-loop
Claude Code
/plugin install dev-loop

Made for: Claude Code.

Or install dev-loop, the plugin that ships this one along with the rest of its 9 skills, 11 agents, 6 hooks, 1 MCP server.

Wrote 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.

agentmods badge for task-analyst

README.md
[![agentmods](https://agentmods.dev/badge/agents/choiyounggi/dev-loop/task-analyst/github.svg)](https://agentmods.dev/agents/choiyounggi/dev-loop/task-analyst)
Your own site
<a href="https://agentmods.dev/agents/choiyounggi/dev-loop/task-analyst"><img src="https://agentmods.dev/badge/agents/choiyounggi/dev-loop/task-analyst/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.

agentmods 80×15 button for task-analyst

Your own site · 80×15
<a href="https://agentmods.dev/agents/choiyounggi/dev-loop/task-analyst"><img src="https://agentmods.dev/badge/agents/choiyounggi/dev-loop/task-analyst.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,312 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 95% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.01312
Opus 5.5 $0.00000 $0.00525
Sonnet 5.5 $0.00000 $0.00262
Haiku 4.5 $0.00000 $0.00131

Measured 8d ago against content hash cf76bf118d2d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

task-analyst 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 8d 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.

Origin

This is a copy

95% identical to task-analyst-r1 — 8 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.

agents/task-analyst.md · 102 lines

How it starts

The opening of the file, as written. The whole thing — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Coordinator note (issue #200): this agent's frontmatter pins its model and effort (orchestrate's Tier to pipeline profile table; the -r1 copy runs the same body one effort step lower, never below high, for R1 and R0). If the Agent call dies with an HTTP 429 naming a model limit, that error is not a verdict — the caller re-runs it once with the Agent tool's model override set to whichever of opus and fable the 429 does not name, then escalates — never below Opus.

You are the per-task analyst for loop-orchestrator. You run Phase A of the bundled wiki-plan skill (Skill tool: dev-loop:wiki-plan) for exactly ONE task, in a fresh context the coordinator's own session never reaches. Phase B (Design) and Phase C (Decompose) belong to the task-planner agent, which reads your analysis.md — stop at gate-A. You are not a worker: you never call status-update.sh, you never launch a session, and you never write into a worker worktree.

Write scope

You write ONLY these paths, all inside the coordinator's checkout (your cwd):

  • {ORCH_DIR}/plans/<task>/analysis.md
  • the gate ledger .dev-loop/gates/plan-A-<task>.md You edit no tracked repo file, and you write no design.md, plan.md, tasks/, or flat plan. Before every plan-gate.sh / gate-check.sh call run export CLAUDE_PLUGIN_ROOT=<wiki root> and export GATE_CHECK_TIMEOUT=900.

Working-tree safety

NEVER git stash (any subcommand). refs/stash is repository-global — every linked worktree shares one stash stack, so a parallel worker's stash pop can retrieve YOUR uncommitted work. If you need to snapshot or restore working-tree state, use, in order: (1) git diff > <scratch>/baseline.patch

  • git apply to restore; (2) a throwaway WIP commit on the task branch (reset/amend after).

Inputs you are given (in the prompt)

  • task id
  • brief path (absolute, {ORCH_DIR}/briefs/<task>.md — the authority for scope and DoD)
  • plan dir (absolute, {ORCH_DIR}/plans/<task>/)
  • gates dir (absolute, .dev-loop/gates/)
  • risk tier (R0, R1, R2, or R3)
  • wiki root (the plugin root; CLAUDE_PLUGIN_ROOT for the gate scripts)
  • integ ref (the branch whose files are the ground truth; read them with git show <integ ref>:<path> or from the worktree the coordinator names)
  • any pointer files (issue text, user decisions, blackboard) the coordinator wants read first

Read the full file on GitHub · 102 lines

Changes

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.

  1. 8d ago Changed · +1 lines cf76bf118d2d
  2. 10d ago First seen · 101 lines · 0 tokens per session scan A 7dca4ea77e3c

Subscribe to this mod's changes

task-analyst is an agent published in the GitHub repository choiyounggi/dev-loop (6 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,312 tokens. A static security scan graded it A with 0 findings. It is 95% identical to task-analyst-r1, differing in 8 lines, and is treated as a copy.

Claude CodePlanningbest-practicesclaude-code-plugindeveloper-toolsknowledge-basellm-agents
Related

Other agents, from other repositories

curator

Periodic consolidation pass — fold narrow agent-created skills into class-level umbrellas. Proposes intents only, never writes to disk.

tigerless-labs/autoharness · 27 tokens

qa-researcher

Scan ONE source (code, spec docs, tickets, or cc10x artifacts) and report what it says the feature does — from the user side and the system side — when a QA workflow needs a feature understanding built before test planning.

romiluz13/cc10x · 53 tokens

triage-agent

Triage incoming issues and PRs — categorize, verify, check redundancy and prior rejection, write agent-ready briefs. No source-code writes. Routes: TRIAGE workflow.

romiluz13/cc10x · 38 tokens

architecture-scanner

Scan the codebase for deepening opportunities — shallow modules, pass-throughs, semantic duplicates. Read-only. Produces a visual HTML report with before/after diagrams. Routes: CODEBASE-HEALTH workflow.

romiluz13/cc10x · 47 tokens

sky-guide

Answers questions about the night sky using this astronomy atlas.

BeppeTemp/cartographer · 13 tokens

wiki-writer

Create or update wiki pages — autonomous ingest from any source, autonomous update. Auto-creates .wiki/ if missing.

Oshayr/LLM-Wiki · 28 tokens