task-list

A read-only skill for listing work items managed through Baron, a system that connects an agent to different work-tracking providers. It can filter items by workflow role, type, sprint, or assignee.

In plain words
What is it for?
Finding your active work, open bugs, review items, backlog tasks, or work assigned to a particular person.
Why use it?
It lets you ask for work in everyday terms without learning each provider's status names or query format.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/loncadev/baron/task-list
Any agent
npx skills add loncadev/baron --skill task-list
Clone the repo
git clone --depth 1 https://github.com/loncadev/baron

Made for: Claude Code, Codex.

Per session 64 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 731 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00064 $0.00731
Opus 5 $0.00032 $0.00365
Sonnet 5 $0.00013 $0.00146
Haiku 4.5 $0.00006 $0.00073

Measured 2d ago against content hash 0e955d9fe5a1, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

task-list 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 2d 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.

plugins/claude-code/skills/task-list/SKILL.md · 47 lines

How it starts

The opening of the file, as written. The whole thing — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.

List work items

A thin, read-only wrapper over baron_issue_read op=query that maps everyday words to its normalized filters (role, typeRole, assignee, limit). It never mutates anything.

Token → filter mapping

  • Assignee: @me / "mine" / "bana atanan" → assignee: "@me". A bare handle (email/login) → that handle.
  • Role: in_progress / "active" / "devam eden" → role: "in_progress"; in_review / "test" / "review" → role: "in_review"; backlog / "new" → role: "backlog"; readyrole: "ready"; done / "closed" → role: "done". "blocked" is not a role and not a query filter — every returned item carries a blocked boolean, so answer "what is blocked?" by filtering the results, never by sending blocked as a role — the core rejects it.
  • Type: bugstypeRole: "bug"; taskstask; storiesstory; epicsepic.
  • Sprint: sprint / "this sprint" / "aktif sprint" → iteration: "@current" (the active sprint); a literal iteration path → that iteration. On providers without sprints this yields nothing.

Filters are AND-combined. baron_issue_read op=query returns a lightweight projection (no body); default cap is 50 — pass a higher limit only when the user asks for more.

Steps

  1. Parse the tokens from the argument (combinable: @me bugs, in_review, …).
  2. Query. One baron_issue_read op=query call with the mapped filters. baron_issue_read op=query takes a single role, so if the user asks for a set that spans roles (e.g. "my open work" = in_progress + in_review), run one query per role and merge. Default with no argument: assignee: "@me" across the active roles (in_progress + in_review).
  3. Present a compact table: key · title · role · typeRole · assignee (+ the item's branchName when present — it's the branch you'd resume with /baron:task-start). If empty, say so plainly.

Rules

  • Read-only: never transition, comment, or create from this skill — that's /baron:task-move / /baron:task-new.
  • Don't dump raw JSON; format the rows. For a large result, show the count and the first page, and offer to narrow the filter rather than raising limit blindly.

Read the full file on GitHub · 47 lines

Changes

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.

  1. 2d ago First seen · 47 lines · 64 tokens per session scan A 0e955d9fe5a1

Subscribe to this mod's changes

task-list is a skill published in the GitHub repository loncadev/baron (1 stars, last pushed 12d ago), licensed Apache-2.0. It adds 64 tokens to every session and 731 once invoked, about $0.0003 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.