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/ohswedd/praxis/task-orchestratornpx skills add Ohswedd/praxis --skill task-orchestratorgit clone --depth 1 https://github.com/Ohswedd/praxisWrote 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/ohswedd/praxis/task-orchestrator)<a href="https://agentmods.dev/skills/ohswedd/praxis/task-orchestrator"><img src="https://agentmods.dev/badge/skills/ohswedd/praxis/task-orchestrator.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.00117 | $0.04538 |
| Opus 5 | $0.00059 | $0.02269 |
| Sonnet 5 | $0.00023 | $0.00908 |
| Haiku 4.5 | $0.00012 | $0.00454 |
Grade A, and why
task-orchestrator 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 — 345 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Task Orchestrator
This is praxis's spine. It turns a terse request into a complete, production-ready change with nothing left implicit. Run the phases in order; do not skip ahead to editing. Prioritise correctness and completeness over speed.
The golden rule: nothing may be silently dropped, stubbed, or left out-of-scope. If something cannot be done, it is stated explicitly in the report, never hidden behind a placeholder.
"Out of scope / follow-ups" is for what the user excluded or what genuinely belongs to another change. It is not a place to move work you started and did not finish, and it is not a way to hand back a first pass. Everything the spec puts in scope, including the error paths, the empty and failure states, the validation, and the tests, ships in this change.
The second golden rule: state only what you verified. Every phase below
produces claims (this passes, that is covered, the docs are updated), and a claim
that turns out on a second look to be untrue costs more than the work it was
meant to save, because it is believed. Run the command instead of predicting its
output, read the file before citing it, and when something could not be checked,
say so in the report. praxis measures what it can: report.py runs the tests,
the runtime harness and the scanners itself, and refuses a vertical citation that
does not resolve. What it cannot measure is on you.
Two house rules apply to every phase, and both are enforced deterministically, so they are not worth testing: no em dashes in anything you write (code, comments, docs, commit messages, or your reply to the user), and no AI attribution in the project's record. Use a colon, a comma, parentheses, or two sentences instead of the dash, and never add a co-author trailer or a "generated with" credit.
Phase 1: Restructure the request (spec)
Use the prompt-architect skill to convert the request into an explicit spec:
- Goal: the outcome, in one or two sentences.
- In scope: concrete deliverables.
- Out of scope / non-goals: what you will deliberately not do (surface this; never narrow scope silently).
- Acceptance criteria: testable conditions for "done".
- Affected areas: files/subsystems likely touched (fill after Phase 2).
- Assumptions: anything you inferred that the user did not state.
- Open questions: genuine ambiguities. Ask them now if they block correct work; otherwise state the assumption you will proceed under.
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 · 345 lines · 117 tokens per session scan A 97cafc796b09
task-orchestrator is a skill published in the GitHub repository Ohswedd/praxis (1 stars, last pushed 1mo ago), licensed MIT. It adds 117 tokens to every session and 4,538 once invoked, about $0.0006 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-31.
Other skills, from other repositories
scroll-craft
Build premium scroll-driven landing pages for service, product, food, and drink brands. Plan the visitor journey, page grammar, emotional peak, and bespoke signature move. Create dimensional heroes with independent visual planes, restrained motion, and separate mobile composition. Use supplied photos and footage or…
a11y-audit
Dedicated WCAG 2.2 AA/AAA accessibility audit across 10 dimensions (A1-A10) covering semantic HTML, keyboard navigation, ARIA patterns, color contrast, forms, images/media, responsive/zoom, motion/animation, reading/content, and legal compliance. Goes far beyond surface-level design-review checks with deep…
wp-demo
Demo HTML creation methodology — single-file demos with section comments for 1:1 WordPress conversion.
wp-polylang
Polylang multilingual methodology — one post per language joined by translation groups, driven through the pll API.
wp-responsive
Responsive design patterns — mobile-first breakpoints, fluid typography, responsive images, touch targets.
wp-contributing
Contributing to the claude-wp-builder plugin itself — the four-layer architecture and what may call what, why tests are grep gates over prose, the frontmatter contract per layer, the two i18n systems, and the PR and release rituals. Use when editing this repository's own commands/, agents/, skills/, starter-theme/…