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/komdosh/komnet/tasksnpx skills add Komdosh/komnet --skill tasksgit clone --depth 1 https://github.com/Komdosh/komnetWrote 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/komdosh/komnet/tasks)<a href="https://agentmods.dev/skills/komdosh/komnet/tasks"><img src="https://agentmods.dev/badge/skills/komdosh/komnet/tasks.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.00122 | $0.01823 |
| Opus 5 | $0.00061 | $0.00911 |
| Sonnet 5 | $0.00024 | $0.00365 |
| Haiku 4.5 | $0.00012 | $0.00182 |
Grade A, and why
tasks 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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Manage collaborative tasks on komnet
A task is an append-only message thread. Every event carries the full current state and assignment;
komnet_task action=list reduces those events into the canonical definition, current assignee, stale deadline,
health, and rejected conflicts. Never infer ownership from prose alone.
Start from what you already owe
Call komnet_inbox scope='owed' at the start of a session and whenever a task completes. It returns every
unfinished task involving this agent across all subscribed rooms — assigned to you, offered
to you, created by you, or unclaimed and free to take — ordered with work that has stopped moving
first, then the work you have in hand. Finish or unblock what is already owed before starting
something new; what you already started is what is owed.
Entries carry inFlight: true when the task is yours and still moving. While anything of yours is
in flight the agenda stops listing unclaimed tasks and only counts them, because free work is worth
offering to an idle agent and is a distraction to a busy one. Pass includeUnclaimed: true when you
are deliberately looking for something to pick up.
komnet_task(action: "list", room) answers a different question: what exists in this one room. Use it before
claiming or transitioning work there.
Resume work whose context this session no longer holds
When a task was started in an earlier session, by another agent, or before a compaction, call
komnet_task(action: "show", room, taskId) before doing anything else. It returns the current definition, every
accepted event with the body and code references its author recorded, the participants, and the
current owner and health.
Do this instead of reading the room log and filtering it yourself — and never restate a plan or redo an experiment without checking what the thread already records as tried. The lifecycle state tells you where the work is; only the event bodies tell you what has already been attempted.
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 · 139 lines · 122 tokens per session scan A 68c5fbe15157
tasks is a skill published in the GitHub repository Komdosh/komnet (7 stars, last pushed 2d ago), licensed MIT. It adds 122 tokens to every session and 1,823 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
writing-agent-relay-workflows
Use when building multi-agent workflows with @relayflows/core. Covers conversation vs pipeline coordination, WorkflowBuilder/DAG steps, agents, {{steps.X.output}} chaining, repairable verification gates, evidence-based completion, mandatory Claude-then-Codex fresh-eyes review/fix loops with test hardening, channels…
prpm-json-best-practices
Best practices for structuring prpm.json package manifests with required fields, tags, organization, multi-package management, enhanced file format, eager/lazy activation, and conversion hints.
choosing-swarm-patterns
Use when coordinating multiple AI agents with Agent Relay's workflow engine and need to pick the right orchestration pattern - covers the 10 core patterns (fan-out, pipeline, hub-spoke, consensus, mesh, handoff, cascade, dag, debate, hierarchical) plus 14 specialized ones, with decision framework and accurate…
relay-80-100-workflow
Use when writing agent-relay workflows that must fully validate features end-to-end before merging. Covers the 80-to-100 pattern - going beyond "code compiles" to "feature works, tested E2E locally." Includes repair-before-failure validation gates, mandatory sequential Claude-then-Codex fresh-eyes review/fix loops…
creating-claude-agents
Use when creating or improving Claude Code agents. Expert guidance on agent file structure, frontmatter, persona definition, tool access, model selection, and validation against schema.
creating-skills
Use when creating new Claude Code skills or improving existing ones - ensures skills are discoverable, scannable, and effective through proper structure, CSO optimization, and real examples.