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/cintia09/codenook/orchestrator-ticknpx skills add cintia09/CodeNook --skill orchestrator-tickgit clone --depth 1 https://github.com/cintia09/CodeNookWrote 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/cintia09/codenook/orchestrator-tick)<a href="https://agentmods.dev/skills/cintia09/codenook/orchestrator-tick"><img src="https://agentmods.dev/badge/skills/cintia09/codenook/orchestrator-tick.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.1 | $0.00000 | $0.01322 |
| Opus 5 | $0.00000 | $0.00661 |
| Sonnet 5 | $0.00000 | $0.00264 |
| Haiku 4.5 | $0.00000 | $0.00132 |
Grade A, and why
orchestrator-tick 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 5d 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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
orchestrator-tick — Advance one task one phase
Role: Core builtin skill that drives the per-task state machine
defined in implementation.md §3.3.
CLI
tick.sh --task <T-NNN> [--workspace <dir>] [--dry-run] [--json]
| flag | meaning |
|---|---|
--task |
task id (required) |
--workspace |
explicit workspace root; otherwise upward search |
--dry-run |
compute but do not persist or invoke dispatch |
--json |
emit ≤500-byte summary JSON to stdout |
Exit codes
| code | meaning |
|---|---|
| 0 | advanced / waiting / done (no operator action required) |
| 1 | blocked (entry-questions, HITL, max_iterations, error) |
| 2 | usage error (missing args, task/state not found) |
| 3 | (legacy mode only) idle/terminal phase |
Output (--json, ≤500 bytes UTF-8)
{
"status": "advanced|waiting|blocked|done|error",
"next_action": "<human-readable>",
"dispatched_agent_id": "ag_T-007_clarify_1",
"message_for_user": "<optional, ≤200 chars>"
}
Algorithm (M4 + v0.2.0 profiles)
Implements the §3.3 pseudocode in full. Reads
.codenook/plugins/<plugin>/{phases,transitions,entry-questions}.yaml,
mutates tasks/<id>/state.json atomically (_lib/atomic.py), and
appends to history/dispatch.jsonl via dispatch-audit/emit.sh.
Profile resolution (v0.2.0+)
When phases.yaml declares both a phases: map (the catalogue) and a
profiles: map (chains over that catalogue), the orchestrator selects
the active chain on every tick via _resolve_profile(...):
state.profile— the cached resolution from a previous tick wins.- The clarifier's output frontmatter
task_type(if present) — read from the most recentoutputs/phase-1-clarifier.md. state.task_type— caller hint from entry-questions / seed.- Fallback default (
featureif defined, else the first profile).
What ships with it
2 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.
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.
- 5d ago First seen · 116 lines · 0 tokens per session scan A d2e184bcf2a8
orchestrator-tick is a skill published in the GitHub repository cintia09/CodeNook (5 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,322 tokens. 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…