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/varienos/agentic-workflowWrote 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/commands/varienos/agentic-workflow/task-master.skeleton)<a href="https://agentmods.dev/commands/varienos/agentic-workflow/task-master.skeleton"><img src="https://agentmods.dev/badge/commands/varienos/agentic-workflow/task-master.skeleton/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/commands/varienos/agentic-workflow/task-master.skeleton"><img src="https://agentmods.dev/badge/commands/varienos/agentic-workflow/task-master.skeleton.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.00000 | $0.01870 |
| Opus 5.5 | $0.00000 | $0.00748 |
| Sonnet 5.5 | $0.00000 | $0.00374 |
| Haiku 4.5 | $0.00000 | $0.00187 |
Grade A, and why
task-master.skeleton 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 25d 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.
How it starts
The opening of the file, as written. The whole thing — 204 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Task Master — Backlog Priority Ranker
Evaluates all backlog tasks with 4-dimension scoring and builds a priority order. Usage:
/task-master
Step 1 — Collect Tasks
backlog task list --plain
List all tasks. For each task extract:
- ID
- Title
- Status (To Do, In Progress, Done)
- Priority (if any)
- Labels (if any)
- Dependencies (if any)
RULE: SKIP tasks in "Done" status. Score only "To Do" and "In Progress" tasks.
To read each task in detail:
backlog task <id> --plain
Step 2 — 4-Dimension Scoring
Evaluate each task on 4 dimensions (1-10):
2.1 — Impact — Weight: x3
How much value does the task add to the project when done?
| Score | Meaning |
|---|---|
| 9-10 | Critical business function; project does not work without it |
| 7-8 | Important feature; seriously affects user experience |
| 5-6 | Useful improvement; creates a visible difference |
| 3-4 | Small improvement; "nice to have" |
| 1-2 | Cosmetic; minimal impact |
2.2 — Risk — Weight: x2.5
What happens if this task is not done?
| Score | Meaning |
|---|---|
| 9-10 | Security hole, data-loss risk, legal issue |
| 7-8 | Performance problem, user-churn risk |
| 5-6 | Technical debt buildup, maintenance difficulty |
| 3-4 | Small technical debt; may become a problem later |
| 1-2 | No risk; fully optional |
2.3 — Dependency — Weight: x2
Do other tasks depend on this?
| Score | Meaning |
|---|---|
| 9-10 | 5+ tasks depend on this; blocker |
| 7-8 | 3-4 tasks depend |
| 5-6 | 1-2 tasks depend |
| 3-4 | Indirect dependency exists |
| 1-2 | Independent; affects nothing |
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.
- 25d ago Changed · -1 lines 66ac5a2bb974
- 1mo ago First seen · 205 lines · 0 tokens per session scan A 9ee631d6f8b1
task-master.skeleton is a command published in the GitHub repository varienos/agentic-workflow (59 stars, last pushed 25d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,870 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-30.
Other commands, from other repositories
luda
Invoke Luda, your Scrum Master, for board integrity — orphan work items, plan-vs-tracker divergence, Done-without-negative-criteria, parked-without-a-trigger — plus ticket creation and team orchestration.
max
Invoke Max, your Senior Product Owner for product vision, backlog management, user stories, and sprint planning.
team-review
Coordinate a multi-role review of the current change.
sm
Invoke Scrum Master for board integrity — orphan work items, plan-vs-tracker divergence, Done-without-negative-criteria, parked-without-a-trigger — plus ticket creation and team orchestration.
po
Invoke Product Owner for product vision, backlog management, user stories, and sprint planning.
anchors
List what each requirement tag anchors to (read-only).