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 ericroliver/tinytask --skill skillgit clone --depth 1 https://github.com/ericroliver/tinytaskWrote 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/ericroliver/tinytask/skill)<a href="https://agentmods.dev/skills/ericroliver/tinytask/skill"><img src="https://agentmods.dev/badge/skills/ericroliver/tinytask/skill/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/ericroliver/tinytask/skill"><img src="https://agentmods.dev/badge/skills/ericroliver/tinytask/skill.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.00021 | $0.04085 |
| Opus 5.5 | $0.00008 | $0.01634 |
| Sonnet 5.5 | $0.00004 | $0.00817 |
| Haiku 4.5 | $0.00002 | $0.00409 |
Grade A, and why
task-management 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.
How it starts
The opening of the file, as written. The whole thing — 315 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent names (e.g.,
tko-sword,tko-shield) are examples. Use actual names from your environment — defined in yourAGENTS.mdfile. Replace placeholders like<your-agent>,<qa-agent>,<developer>with real names.
TinyTask Shared Skill
Overview
TinyTask is a task management system for LLM agent collaboration, exposed as an MCP server, HTTP API, and CLI. The tinytask CLI communicates with the server over HTTP. Role-specific workflows live in developer.md, tester.md, reviewer.md, and coordinator.md — this file is the CLI syntax and conventions reference.
Core Concepts
| Concept | Description |
|---|---|
| Task | Fundamental unit of work — has title, description, status, assignee, queue, priority, tags, optional parent and blocked-by |
| Subtask | Task with parent_task_id set — full task with own lifecycle; does not auto-change parent status |
| Queue | Named collection of tasks — routing mechanism determining which agent picks up work |
| Comment | Annotation attached to a task — primary inter-agent communication channel |
| Link | Typed URL-based relationship between tasks or external resources (PRs, docs) |
| History | Immutable log of every task change (status, queue, assignee, fields) with timestamp and agent |
Task Fields
| Field | Type | Required | Description |
|---|---|---|---|
id |
integer (auto) | Yes | Unique ID (sequential integer, e.g. 892) |
title |
string | Yes | Short summary, <80 chars, action verb prefix |
description |
string | Yes | What, why, acceptance criteria |
status |
enum | Yes | idle | working | complete |
assigned_to |
string | No | Agent responsible for the task |
created_by |
string | Yes | Agent that created the task |
priority |
enum | No | low | medium | high | urgent (default: medium) |
tags |
JSON array | No | Lowercase, hyphenated labels |
queue_name |
string | No | Queue the task belongs to |
parent_task_id |
string | No | Parent task if subtask |
blocked_by_task_id |
string | No | Task ID that blocks this task |
created_at |
ISO 8601 | Yes | Creation timestamp |
updated_at |
ISO 8601 | Yes | Last modification time |
completed_at |
ISO 8601 | No | When marked complete (nullable) |
archived_at |
ISO 8601 | No | When archived (nullable) |
What ships with it
6 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.
- 1mo ago Changed e129a5c4ef6e
- 1mo ago First seen · 315 lines · 21 tokens per session scan A 0a713d8d285e
task-management is a skill published in the GitHub repository ericroliver/tinytask (1 stars, last pushed 16d ago), licensed MIT. It adds 21 tokens to every session and 4,085 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-31.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…