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/Surya8991/AgentMasterWrote 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/rules/surya8991/agentmaster/task-viewer)<a href="https://agentmods.dev/rules/surya8991/agentmaster/task-viewer"><img src="https://agentmods.dev/badge/rules/surya8991/agentmaster/task-viewer/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/rules/surya8991/agentmaster/task-viewer"><img src="https://agentmods.dev/badge/rules/surya8991/agentmaster/task-viewer.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.00076 | $0.00612 |
| Opus 5.5 | $0.00030 | $0.00245 |
| Sonnet 5.5 | $0.00015 | $0.00122 |
| Haiku 4.5 | $0.00008 | $0.00061 |
Grade A, and why
task-viewer 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.
`status`: `curl -s -o /dev/null -w '%{http_code}' http://localhost:3456` (try the reported port) — 200 means running. What it actually says
Launches and manages the claude-task-viewer dashboard — a real-time Kanban board that reads ~/.claude task JSON and serves it in the browser. Observation only: Claude Code controls task state, this just visualizes it.
Resolve the app directory
The app lives outside ~/.claude/skills (it's a full Node app, not a skill). Its location is stored in a config file so this skill stays portable:
CFG="$HOME/.claude/.agentmaster-cache/task-viewer.path"
APP_DIR="$(cat "$CFG" 2>/dev/null)"
If $CFG is missing or $APP_DIR doesn't contain server.js, tell the user the app isn't installed/registered and ask for its path, then write it back:
printf '%s' "<path>" > "$CFG". Do not guess absolute paths.
Commands
Default (no arg) or start:
- Read
$APP_DIRas above. - Ensure deps exist: if
$APP_DIR/node_modulesis missing, runnpm installin$APP_DIRfirst. - Start the server in the background and open the browser:
PORT=<port-if-given> node "$APP_DIR/server.js" --open- Default port is 3456; it auto-increments if busy (unless
PORTis set). - Run it as a background process so it keeps serving after this turn.
- Default port is 3456; it auto-increments if busy (unless
- Report the URL it printed (
http://localhost:<port>).
status: curl -s -o /dev/null -w '%{http_code}' http://localhost:3456 (try the reported port) — 200 means running.
stop: kill the running server process.
- Windows:
taskkill //F //IM node.exeis too broad — prefer finding the PID bound to the port. If unsure, tell the user which PID/port and let them confirm. - Unix:
pkill -f "server.js"scoped to this app.
Notes
- The viewer reads task data from
$CLAUDE_DIR(defaults to~/.claude). Override withCLAUDE_DIR=<path>or--dir <path>if the user keeps tasks elsewhere. - It's read-only over tasks; never claim it can create/modify/delete task state on Claude's behalf.
- This is a long-running server. Don't block the conversation waiting on it — start it detached and move on.
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 · 43 lines · 76 tokens per session scan A 5558d86e6c2c
task-viewer is a cursor rule published in the GitHub repository Surya8991/AgentMaster (2 stars, last pushed 1mo ago), licensed MIT. It adds 76 tokens to every session and 612 once invoked, about $0.0003 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-31.
Other cursor rules, from other repositories
project-epic-template-cursorrules-prompt-file
Cursor rules for project development with epic template integration.
optimize-dry-solid-principles-cursorrules-prompt-f
Cursor rules for optimization development with DRY and SOLID principles integration.
monorepo-and-tooling
Rules for projects that may use a monorepo, a single repository containing multiple applications or shared packages. They also define Taskfile commands and how to keep environment settings outside the code.
swamr-state-manager
Swamr State Manager — tracks task progress, manages the execution pipeline, handles retries and escalation. Maintains swamr/state.json as the single source of truth for swarm progress.
api-design-typescript
API Design for TypeScript — Express, NestJS, Fastify patterns, middleware, validation, and error handling. Extends core/rules/api-design.mdc with TypeScript-specific guidance.
tasks
Guidelines for implementing task management operations.