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 commands/data-wise/claude-plugins/task-outputgit clone --depth 1 https://github.com/Data-Wise/claude-pluginsWhat 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.00000 | $0.02083 |
| Opus 5 | $0.00000 | $0.01042 |
| Sonnet 5 | $0.00000 | $0.00417 |
| Haiku 4.5 | $0.00000 | $0.00208 |
Grade A, and why
task-output 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 yesterday.
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 — 436 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/task-output - View Background Task Results
Retrieve and display results from completed (or running) background tasks.
Purpose
View output from background tasks launched by:
/workflow:brainstorm --background/workflow:refine(option 2: background)- Any command with background delegation
Usage
/workflow:task-output <task_id> # View results
/workflow:task-output <task_id> --raw # Show raw output
/workflow:task-output --latest # View most recent completed task
When invoked:
View Completed Task Output
/workflow:task-output abc123
Output:
TASK OUTPUT
════════════════════════════════════════════════════════════
Task ID: abc123
Command: /workflow:brainstorm "improve test coverage"
Status: ✅ Completed
Duration: 2m 45s
Completed: 2 minutes ago
────────────────────────────────────────────────────────────
RESULTS:
────────────────────────────────────────────────────────────
💡 IDEAS: improve test coverage
⚡ Quick (< 1hr)
1. Add edge case tests for user input validation
2. Fix flaky test_auth() timeout issue
3. Add assertion messages to existing tests
🔧 Medium (1-3hrs)
4. Refactor test helpers into test_utils.R
5. Add integration tests for API endpoints
6. Set up coverage reporting with covr package
🚀 Big (1+ days)
7. Implement CI/CD with automated testing
8. Add property-based testing with hedgehog
💡 Start with #1 or #2
────────────────────────────────────────────────────────────
📋 Ideas saved to IDEAS.md
────────────────────────────────────────────────────────────
💡 NEXT STEPS:
Work on an idea:
/workflow:next - Pick from IDEAS.md and start
Check other tasks:
/workflow:task-status - List all tasks
Implementation:
- Look up task by ID
- Check if task is completed
- Use TaskOutput tool to retrieve results
- Parse and format output
- Display in clean, readable format
- Show relevant next steps
View Running Task Output (Partial)
/workflow:task-output abc123
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.
- yesterday First seen · 436 lines · 0 tokens per session scan A 4b9401c9e672
task-output is a command published in the GitHub repository Data-Wise/claude-plugins (7 stars, last pushed 5d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,083 tokens. 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-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.