Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/jpicklyk/task-orchestratornpx agentmods add skills/jpicklyk/task-orchestrator/manage-schemasWrote 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/manage-schemas)<a href="https://agentmods.dev/skills/jpicklyk/task-orchestrator/manage-schemas"><img src="https://agentmods.dev/badge/skills/jpicklyk/task-orchestrator/manage-schemas/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/manage-schemas"><img src="https://agentmods.dev/badge/skills/jpicklyk/task-orchestrator/manage-schemas.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.00174 | $0.03602 |
| Opus 5.5 | $0.00070 | $0.01441 |
| Sonnet 5.5 | $0.00035 | $0.00720 |
| Haiku 4.5 | $0.00017 | $0.00360 |
Grade A, and why
manage-schemas 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 — 216 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Manage Schemas — Note Schema Lifecycle
Create, view, edit, delete, and validate note schemas in .taskorchestrator/config.yaml. Schemas define which notes agents must fill at each workflow phase before advancing items.
Every tool call below is a to-call block, {tool, select|op, args}, in the shapes of call-shapes.md. The config tool is served by the orchestration profile only.
Step 1 — Determine Intent
Classify from $ARGUMENTS and conversation context before making any tool calls.
| Signal words | Action |
|---|---|
| "create", "build", "new", "add schema", "define", "set up" | CREATE |
| "recommend", "advise", "design", "what schema should I use", "help me choose", a described workflow with no schema name | CREATE (advisor path) |
| "show", "view", "list", "what schemas", "display" | VIEW |
| "edit", "modify", "change", "update", "add note to", "remove note from" | EDIT |
| "delete", "remove schema", "drop" | DELETE |
| "validate", "check", "verify", "lint" | VALIDATE |
If $ARGUMENTS contains both an action and a schema name (e.g., "view bug-fix"), extract both. If intent cannot be determined, ask via AskUserQuestion with options: Create, View / Validate, Edit, Delete.
Validate is grouped with View — both leave the config file unchanged.
Step 2 — Config Bootstrap
The target file is the path on the SessionStart context's Config: line (project or personal scope) when there is one, otherwise .taskorchestrator/config.yaml. In personal scope that is the user-level file, so an edit applies to every directory that has no project config of its own. Check if the target file exists by reading it.
If the file does not exist:
- For VIEW or VALIDATE: report "No schemas configured —
.taskorchestrator/config.yamldoes not exist." and stop. - For CREATE, create the file with the new schema (create-workflow Step 4). For EDIT or DELETE, report "No schemas configured" and stop.
If the file exists: Read and parse it. Proceed to Step 3.
What ships with it
18 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/companion-template.md 4.6 KB
- references/config-format.md 71 KB
- references/create-workflow.md 16 KB
- references/delete-workflow.md 2.6 KB
- references/edit-workflow.md 5.8 KB
- references/example-schemas.md 15 KB
- references/profiles/autonomous-loop.md 1.4 KB
- references/profiles/content-production.md 2.1 KB
- references/profiles/data-pipeline-ops.md 2.0 KB
- references/profiles/document-review.md 1.6 KB
- references/profiles/incident-response.md 1.7 KB
- references/profiles/multi-project.md 1.2 KB
- references/profiles/research-pipeline.md 1.9 KB
- references/profiles/schema-free.md 898 B
- references/profiles/spec-driven-team.md 2.1 KB
- references/profiles/support-triage.md 1.6 KB
- references/validate-workflow.md 7.8 KB
- references/workflow-patterns.md 11 KB
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 Changed · -28 lines · -38 tokens per session dd8ef204b570
- 20d ago Changed 54a567a9ad6c
- 22d ago Changed e82e75682053
- 28d ago Changed 724a6ba6a3d1
- 1mo ago Changed · +7 lines 8c4195f04aec
- 1mo ago First seen · 237 lines · 212 tokens per session scan A 2f00aa995270
manage-schemas is a skill published in the GitHub repository jpicklyk/task-orchestrator (209 stars, last pushed yesterday), licensed MIT. It adds 174 tokens to every session and 3,602 once invoked, about $0.0007 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
debugging
Systematic root-cause debugging with verification. Use for errors, stack traces, broken tests, flaky tests, regressions, or anything not working as expected. For validating bug reports before fixing, use bug-reproduction-validator agent.
pinescript
Pine Script v6: syntax, performance, error diagnosis, backtesting, visualization. Use when writing or debugging .pine files or TradingView Pine indicators/strategies.
meta-prompting
Structured decision modifiers (/think, /verify, /adversarial, /edge, /confidence, /assumptions, etc.) to stress-test conclusions, evidence, assumptions, alternatives, and edge cases. Use when validating an important design, architecture decision, or ambiguous plan before committing.
document-review
Structural and accuracy review of documents: gaps, clarity, completeness, organization, and claims checked against the code. Use when a brainstorm, plan, spec, ADR, or any doc needs polish before the next workflow step. For exploring new ideas from scratch, use brainstorming instead.
reflect
Session retrospective and skill audit. Use when asked to reflect, do a retrospective, review lessons learned, audit what went well or wrong, or review session effectiveness.
cpp-systems
Modern C++ patterns: RAII and ownership, rule of zero/five, exceptions and error handling, API and ABI boundaries, templates, and CMake tooling. Use when writing, reviewing, refactoring, or debugging C++, working with smart pointers, move semantics, memory leaks, template errors, or gtest. For plain C, see…