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 skills/jpicklyk/task-orchestrator/schema-workflownpx skills add jpicklyk/task-orchestrator --skill schema-workflowgit 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/schema-workflow)<a href="https://agentmods.dev/skills/jpicklyk/task-orchestrator/schema-workflow"><img src="https://agentmods.dev/badge/skills/jpicklyk/task-orchestrator/schema-workflow.svg" alt="Measured on agentmods" 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 | $0.00028 | $0.02411 |
| Opus 5 | $0.00014 | $0.01205 |
| Sonnet 5 | $0.00006 | $0.00482 |
| Haiku 4.5 | $0.00003 | $0.00241 |
Grade A, and why
schema-workflow 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 4d 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 — 216 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Schema Workflow
Drive any schema-tagged MCP work item through its gate-enforced lifecycle. This skill is schema-driven — it reads note requirements and authoring guidance from the item's tag schema at runtime, never hardcoding what notes should contain.
When this skill applies: Any item whose type field matches a schema defined in
work_item_schemas: in .taskorchestrator/config.yaml, or whose tags match a schema in
note_schemas: (legacy). Items without a matching type or tags advance freely (no gates).
Entry Point
Start by loading the item's context:
get_context(itemId="<uuid>")
The response tells you everything needed to proceed:
| Field | What it means |
|---|---|
currentRole |
Which phase the item is in (queue, work, review, terminal) |
canAdvance |
Whether the gate is satisfied for the next start trigger |
missing |
Required notes not yet filled for the current phase |
expectedNotes |
All notes defined by the schema, with exists and filled status (keys-only — no description/guidance/skill) |
guidanceKey |
Key of the first unfilled required note with guidance; resolve its text via query_items(operation="schema", itemId=...) |
noteSchema |
The full schema definition matching the item's tags |
If currentRole is terminal, the item is already complete — nothing to do.
If noteSchema is null or empty, no schema matches the item. This means either:
.taskorchestrator/config.yamldoesn't exist or has nowork_item_schemasornote_schemassection- The item's
typefield doesn't match any configured schema key inwork_item_schemas - The item's tags don't match any configured schema key in
note_schemas(legacy fallback) - No
defaultschema exists as a fallback
Inform the user: "No schema found for this item's type/tags. Use /manage-schemas to configure gate workflows." The item can still advance freely — this is non-blocking, but gate enforcement won't apply.
Phase Progression Loop
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.
- 4d ago First seen · 216 lines · 28 tokens per session scan A 167803b86ba7
schema-workflow is a skill published in the GitHub repository jpicklyk/task-orchestrator (205 stars, last pushed 1mo ago), licensed MIT. It adds 28 tokens to every session and 2,411 once invoked, about $0.0001 per session on Opus 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
pneuma-project
Project-context awareness — multi-session workflows around one topic, shared materials and preferences, and cross-mode handoffs as a high-value user path.
vc-generate-phase-program
Generate kickoff artifacts for a multi-phase program: umbrella plan, Program Goal Charter, session-goal block, per-phase plan stubs, and the 7-step per-phase inner loop reference.
vc-intent-clarify
Clarify intent before RIPER-5 phase delegation. Scores ambiguity (4 signals); generates structured multi-choice questions for Tier 2. Two-mode: SIMPLE and DEEP.
vc-agent-browser
AI-optimized browser automation CLI with context-efficient snapshots. Use for long autonomous sessions, self-verifying workflows, video recording, and cloud browser testing (Browserbase).
vc-scenario
Generate comprehensive edge cases and test scenarios by decomposing features across 12 dimensions. Use before implementation or testing to catch issues early.
vc-audit-context
Audit project context routing, shared-skill discoverability, and Claude/Codex wiring. Use when context docs or skill surfaces move, split, or drift.