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 skills add jpicklyk/task-orchestrator --skill dependency-managergit clone --depth 1 https://github.com/jpicklyk/task-orchestratorWrote 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/skills/jpicklyk/task-orchestrator/dependency-manager)<a href="https://agentmods.dev/skills/jpicklyk/task-orchestrator/dependency-manager"><img src="https://agentmods.dev/badge/skills/jpicklyk/task-orchestrator/dependency-manager/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/skills/jpicklyk/task-orchestrator/dependency-manager"><img src="https://agentmods.dev/badge/skills/jpicklyk/task-orchestrator/dependency-manager.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00053 | $0.03424 |
| Opus 5.5 | $0.00021 | $0.01370 |
| Sonnet 5.5 | $0.00011 | $0.00685 |
| Haiku 4.5 | $0.00005 | $0.00342 |
Grade A, and why
dependency-manager 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 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.
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 — 384 lines — stays where its author put it; the contents beside it link to each section on GitHub.
dependency-manager — Dependency Visualization, Creation, and Diagnosis
Manage BLOCKS, IS_BLOCKED_BY, and RELATES_TO edges between work items. Handles all four paths: view existing dependencies, create new edges, delete edges, and diagnose why items cannot start.
Step 1: Determine Intent
Classify the user request before making any tool calls.
Resolve $ARGUMENTS to a UUID via query_items search (operation="search", query=$ARGUMENTS, limit=5); if ambiguous, present matches via AskUserQuestion. If $ARGUMENTS is already a UUID, default intent to VIEW for that item.
If $ARGUMENTS is empty, infer intent from the surrounding conversation. If intent is still unclear, ask via AskUserQuestion: "What would you like to do with dependencies? Options: view, create, delete, diagnose."
Compound requests (e.g., "show what blocks this and remove the dependency"): handle the VIEW path first, then proceed to the second action using the results.
Intent signal words:
| Signal words | Path |
|---|---|
| "show", "view", "graph", "what blocks", "what depends on", "visualize" | VIEW (Step 2) |
| "add", "create", "link", "connect", "chain", "depend on" | CREATE (Step 3) |
| "remove", "delete", "unlink", "disconnect" | DELETE (Step 4) |
| "why can't this start", "why is this blocked", "diagnose", "show blockers", "unblock" | DIAGNOSE (Step 5) |
Step 2: View Dependencies
Once you have an item ID and intent is VIEW, query its dependency edges:
query_dependencies(operation="get", itemId="<uuid>", direction="all", includeItemInfo=true)
Format the result as an ASCII tree:
◉ Design API schema (work)
↳ BLOCKS → ○ Implement data models (queue)
↳ BLOCKS → ○ Build REST endpoints (queue)
← BLOCKED BY → ◉ Finalize data contract (work)
Use the visual symbols to indicate role at a glance:
| Symbol | Role |
|---|---|
| ✓ | terminal |
| ◉ | work or review |
| ○ | queue |
| ⊘ | blocked |
Direction parameter meanings:
| Value | Returns |
|---|---|
outgoing |
Edges where this item is the source (things this item blocks) |
incoming |
Edges where this item is the target (things that block this item) |
all |
Both directions combined |
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 · 384 lines · 53 tokens per session scan A d1b408097f48
dependency-manager is a skill published in the GitHub repository jpicklyk/task-orchestrator (209 stars, last pushed 2d ago), licensed MIT. It adds 53 tokens to every session and 3,424 once invoked, about $0.0002 per session on Opus 5.5. 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 skills, from other repositories
branch-surgery-pr-split
Split oversized or mixed-concern branches into smaller, reviewable PR stacks with safety refs, topology selection, parity audits, and merge sequencing. Use when a PR or branch is too large, difficult to review, mixed across concerns, conflict-prone, or needs to be decomposed without losing net changes.
do-it
Turn the current discussion into a task step and implement it — adds step to task file, updates spec if needed, then implements with review-fix loop.
plan-tasks
Read an existing spec and propose a task breakdown — assesses separable work streams, proposes split, creates task files linked to the spec.
draft-issue
Draft a GitHub issue based on a discussion or requirements in the current conversation.
run-task
Run pending steps, then aftertask finalization; does not close the task.
load-spec
Load a feature spec, its linked tasks, and feature-level progress and gaps.