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 currentgit 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/current)<a href="https://agentmods.dev/skills/ericroliver/tinytask/current"><img src="https://agentmods.dev/badge/skills/ericroliver/tinytask/current/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/current"><img src="https://agentmods.dev/badge/skills/ericroliver/tinytask/current.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.00025 | $0.01983 |
| Opus 5.5 | $0.00010 | $0.00793 |
| Sonnet 5.5 | $0.00005 | $0.00397 |
| Haiku 4.5 | $0.00003 | $0.00198 |
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 — 411 lines — stays where its author put it; the contents beside it link to each section on GitHub.
We use the tinytask CLI and it is typically in your path.
Task Commands
Create Task
tinytask task create "Task title"
tinytask task create "Task title" -d "Description" -a alice -p 5
tinytask task create "Task title" --assigned-to bob --priority 8 --tags "bug,urgent"
# Create as subtask
tinytask task create "Write tests" --parent 5 --assigned-to alice
# Create and assign to queue
tinytask task create "Fix bug" --queue dev --priority 8
Get Task
tinytask task get 1
tinytask task get 1 --json
Update Task
tinytask task update 1 --status working
tinytask task update 1 --title "New title" --priority 9
tinytask task update 1 --assigned-to charlie --tags "feature,ui"
# Change parent or make top-level
tinytask task update 10 --parent 5
tinytask task update 10 --parent null
# Change queue
tinytask task update 1 --queue qa
List Tasks
tinytask task list
tinytask task ls
tinytask task list --assigned-to alice
tinytask task list --status working --limit 10
tinytask task list --include-archived
# Filter by queue or parent
tinytask task list --queue dev
tinytask task list --parent 5
tinytask task list --exclude-subtasks
Delete Task
tinytask task delete 1
tinytask task delete 1 --yes
Archive Task
tinytask task archive 1
Subtask Commands
Manage task hierarchies and break down complex work into subtasks.
Create Subtask
tinytask subtask create 5 "Design database schema"
tinytask st create 5 "Write tests" -d "Unit and integration tests" -a alice
tinytask st create 5 "Deploy feature" -p 8 -q qa
List Subtasks
tinytask subtask list 5
tinytask st list 5 --recursive
tinytask st list 5 --include-archived
View Task Tree
tinytask subtask tree 5
tinytask st tree 5 --recursive
Output displays hierarchical task structure:
Task #5: User Authentication [dev] (alice)
├── Task #10: Design schema (bob)
│ └── Task #15: Create ERD (alice)
├── Task #11: Write tests (charlie)
└── Task #12: Deploy (unassigned)
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 · 411 lines · 25 tokens per session scan A 77678db1a434
task-management is a skill published in the GitHub repository ericroliver/tinytask (1 stars, last pushed 16d ago), licensed MIT. It adds 25 tokens to every session and 1,983 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-09-07.
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…