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/unclutter-pro/atlas/tasksnpx skills add unclutter-pro/atlas --skill tasksgit clone --depth 1 https://github.com/unclutter-pro/atlasWrote 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/unclutter-pro/atlas/tasks)<a href="https://agentmods.dev/skills/unclutter-pro/atlas/tasks"><img src="https://agentmods.dev/badge/skills/unclutter-pro/atlas/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.00069 | $0.00637 |
| Opus 5 | $0.00034 | $0.00318 |
| Sonnet 5 | $0.00014 | $0.00127 |
| Haiku 4.5 | $0.00007 | $0.00064 |
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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Task Management
Use task for goals (longer-running outcomes with measurable done-conditions) and tasks (concrete steps). The session can't end while goals or open tasks remain — close them with a thorough --reason, or set a reminder to continue later.
Goals
task goal create \
--title="Lift mapstudio.ai organic traffic to 1k clicks/day" \
--done="GSC: ≥1000 average daily clicks over a 7-day window for organic search, top-10 ranking for 'tile map studio'" \
--description="Strategy: technical SEO audit (Core Web Vitals, sitemap, structured data) first, then content gaps for top-5 commercial intents. Priorities: real measurable traffic over vanity rankings; user prefers iterative shipping over big-bang."
task goal list # active goals this session
task goal show 3
task goal close 3 --reason="<thorough explanation of why the done-condition is genuinely met, with concrete evidence — short reasons are rejected>"
task goal close 3 --reason="..." --cascade-cancel # also cancels still-open tasks
A goal's --description carries the strategy + user priorities (broader context for a re-spawned session); --done is the measurable acceptance criteria. Write both for any goal worth opening.
When closing a goal, provide an extensive --reason — explain why the done-condition is actually met, with concrete evidence. Short reasons get rejected.
Tasks
task add --title="Run Lighthouse audit on /maps and /pricing" --goal=3 --priority=1
task add --title="Fix Largest Contentful Paint on /maps" --goal=3 --depends-on=12
task add --title="Draft 'tile map studio' landing page copy" --goal=3 --priority=2
task ready # tasks with no open deps
task list # open + in_progress
task list --status=done,cancelled
task show 12
task close 12 --reason="LCP now 1.8s on 4G profile, was 3.4s"
task cancel 15 --reason="Subsumed by #18"
Statuses: tasks open → in_progress → done | cancelled; goals active → done | abandoned | validation_exhausted.
Priority: 0=critical, 1=high, 2=normal (default), 3=low, 4=backlog.
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 · 49 lines · 69 tokens per session scan A efec3d213a6a
tasks is a skill published in the GitHub repository unclutter-pro/atlas (2 stars, last pushed 16d ago), licensed MIT. It adds 69 tokens to every session and 637 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.
Other skills, from other repositories
agile-product-owner
../../../product-team/agile-product-owner/skills/agile-product-owner/SKILL.md.
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…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
subagent-delegation
Canonical protocol for delegating GSD work to native Antigravity subagents — when to delegate, how to invoke, workspace isolation modes, and the inline fallback for older IDE versions.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
project-init
Scaffold an unconfigured directory into a configured pi project. Interactive, profile-driven: previews the planned writes, then writes AGENTS.md, .pi/settings.json and prompt files — optionally also a knowledge base, an openspec/ scaffold, and user-global /.pi/agent/settings.json. Use on a bare directory, or when the…