task-orchestrator@r7
CAUTION· install onlyPublisher claims: "Model Context Protocol (MCP) server for comprehensive task and feature management, providing AI assistants with a structured, context-efficient way to interact with project data." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Nothing executable in the bundle ran; the trace covers the install step only.- Tested
- every file read, file written and host contacted by what ran
- Not tested
- use of the skill by an agent
What this means for the label: Caution here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
Code inventory arrives with this version's next honeypot run.- It will ask for
- unknown until the next run
- Where it talks to
- unknown until the next run
- What the honeypot saw
- no credential files read · no network
- What we could not test
- use of the skill by an agent
Not enough was observed to say yet. Nothing executable in the bundle ran; the trace covers the install step only. This version's code has not been inventoried for credentials and hosts either; both arrive with its next honeypot run (popular servers first). `vet-skills try task-orchestrator` runs it now and prints the full answer.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
Is task-orchestrator@r7 safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (1 scenario; nothing executable in the bundle ran; the trace covers the install step only) on 2026-11-07 and scored it 78/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: Instructs the agent to modify its persistent memory or instruction files; Auto-update or dynamic fetch configuration; Instructs the agent to modify its persistent memory or instruction files. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 1 scenarios · 0 deviationsStatic findings
Also update the version table in `claude-plugins/CLAUDE.md`: find the row for each bumped plugin andFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.- **DB permission errors:** `docker run --rm -v mcp-task-data:/app/data --user root amazoncorretto:25-al2023-headless chown -R 1001:1001 /app/data`.Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.| 5 Open | `node "<helper>" run-ops --plan <scratchpad>/run-wave/<runId>/plan.json --phase open` renders `{tool: "runs_write", ops: [{op: "open", rootId, items, scopeId?, label: <runId>, title, hints:Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.server restart, config hot-reload); resume after compaction or `--resume`. An item may addFix: Pin versions and sources; vendor anything fetched at install time.The user exports `TASK_ORCHESTRATOR_API_TOKEN` (agents) and `TASK_ORCHESTRATOR_DIRECTOR_TOKEN` (director) before starting Claude Code. The director token defaults to `kind: agent`: it still answers thFix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.Both modes, once the server answers. Locate the orchestration entry the way `hooks/session-start.mjs` does: `.mcp.json` `mcpServers`, then `~/.claude.json` `mcpServers` and `projects[<dir>].mcpServersFix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.- `rest_advance_422_feature_task.json` — `POST /api/v1/items/{feature-task id}/advance` withFix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.`/task-orchestrator:run-wave` reads the project's `.taskorchestrator/run-profile.json`, and a project dispatch contract pins its own build self-check. A seat you dispatch **by hand**, outside both of Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.| 3 Plan | `node "<helper>" plan --in <scratchpad>/run-wave/snapshot.json --scratchpad <scratchpad>` (add `--method B` whenever F1 selected Method B, so `meta.method` is `"B"`; without `--method`, theFix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.- [ ] Is any plugin file changed (skills, hooks, workflows, agents)? The cache is version-keyed and re-extracts lazily, so a plain marketplace update does not pick it up: run the forced refresh in `clFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.`state.json`. On the task notification the director sends the result JSON verbatim and the usageFix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.(env, default true) disables resource-lease gate enforcement server-wide — a kill switch for leaseFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.> `{success, data}`) and the two `rest_gate_*.json` captures are `rest_context_*.json` (`POST /api/v1/ops/items_read`,Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.sh -c 'cp /seed.sqlite /app/data/current-tasks.db && chown 1001:1001 /app/data/current-tasks.db'Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.Cost to the agent
Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.
Known vulnerabilities
Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.
What would make this Verified
2 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim jpicklyk: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- Auto-update or dynamic fetch configuration≈ +4 on the totalPin versions and sources; vendor anything fetched at install time.
- New publisher≈ +3 on the totalTime clears this on its own after 14 and 30 days. Claiming the handle (+50) is the fastest way past it.
- File permission modification command≈ +2 on the totalRequest the narrowest permission that works; replace wildcards with the exact paths or hosts.
- File type combined with upload action≈ +2 on the totalRemove the call, or declare the host in frontmatter and explain in the README what is sent and why.
- MCP server using network transport (SSE/HTTP)≈ +2 on the totalNamespace tool names and keep tool descriptions literal; no instructions to the agent inside them.