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 skills add lukacf/meerkat --skill task-workflowgit clone --depth 1 https://github.com/lukacf/meerkatWrote 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/lukacf/meerkat/task-workflow)<a href="https://agentmods.dev/skills/lukacf/meerkat/task-workflow"><img src="https://agentmods.dev/badge/skills/lukacf/meerkat/task-workflow/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/lukacf/meerkat/task-workflow"><img src="https://agentmods.dev/badge/skills/lukacf/meerkat/task-workflow.svg" alt="Reviewed on agentmods" width="80" 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.00014 | $0.00323 |
| Opus 5.5 | $0.00006 | $0.00129 |
| Sonnet 5.5 | $0.00003 | $0.00065 |
| Haiku 4.5 | $0.00001 | $0.00032 |
Grade A, and why
Task 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 1mo 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.
What it actually says
Task Workflow
Use builtin task tools for lightweight project work tracking. A configured store may persist them, but they remain scratch structure rather than the claim-safe shared WorkGraph authority.
Operating Rules
- Use
task_createfor planning, checklists, or local project tasks that do not need realm-wide claims, evidence, or cross-agent readiness. - Use clear imperative subjects and descriptions with acceptance criteria.
- Read an exact task with
task_get, and usetask_updateto move it toin_progresswhen you start andcompletedonly when it is actually done. - Use
task_listafter completing a task to find the next local item. - Keep dependencies simple. If blocking relationships must coordinate multiple agents or survive compaction/restarts as shared truth, use WorkGraph instead.
Boundary With WorkGraph
- Builtin tasks: lightweight project task lists and simple progress tracking; no claims, leases, revisions, or evidence authority.
- WorkGraph: realm-scoped durable commitments, readiness, dependency topology, authorized claims, leases, evidence, and terminal truth. Its ledger is the shared authority, not a peer message, prompt, actor, or task-list projection.
- Schedule: time-based wakeups, recurrence, occurrence claims, and delivery outcomes. It does not decide WorkGraph readiness or completion.
- Memory: recalled knowledge, not live task state.
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.
- 1mo ago First seen · 34 lines · 14 tokens per session scan A 863da112b553
Task Workflow is a skill published in the GitHub repository lukacf/meerkat (23 stars, last pushed today), licensed Apache-2.0. It adds 14 tokens to every session and 323 once invoked, about $0.0001 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
create-issue
Draft and submit a GitHub issue from a user idea or bug description, with bilingual body and correct labels.
issue-creator
A guide for turning unclear user feedback from text, chat excerpts, or screenshots into a focused GitHub issue, a tracked software-work item. It preserves the original request and separates evidence from information that is still unknown.
status
Surfaces the current state of work in gflow-cli. Three variants at different levels of detail: full state (status), next task only (next), active plan identity (active). All variants run scripts/dev/activeplan.py and filter its output to the requested detail level.
hatch3r-board-groom
Ongoing backlog refinement for existing board items. Re-prioritize, reclassify, re-scope, archive stale items, decompose oversized issues, merge duplicates, refresh dependencies, and remediate board health findings.
hatch3r-board-init
Initializes a project board (GitHub Projects V2, Azure Boards, or GitLab Issue Boards) with hatch3r's label taxonomy, status fields, and board structure. Platform detected from hatch.json.
hatch3r-board-shared
Shared context and procedures for all board commands. Provides platform-agnostic board config, label taxonomy, branch conventions, sync enforcement, and tooling directives. Platform-specific details are in commands/board/shared-{platform}.md.