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 signalcompose/claude-tools --skill next-tasksgit clone --depth 1 https://github.com/signalcompose/claude-toolsWrote 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/signalcompose/claude-tools/next-tasks)<a href="https://agentmods.dev/skills/signalcompose/claude-tools/next-tasks"><img src="https://agentmods.dev/badge/skills/signalcompose/claude-tools/next-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.1 | $0.00078 | $0.00324 |
| Opus 5 | $0.00039 | $0.00162 |
| Sonnet 5 | $0.00016 | $0.00065 |
| Haiku 4.5 | $0.00008 | $0.00032 |
Grade A, and why
next-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 6d 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.
What it actually says
Next Tasks
Extract "next tasks" from ~/.ypm/PROJECT_STATUS.md and display in priority order.
Prerequisites
- Run
/ypm:setupfirst if~/.ypm/config.ymldoesn't exist - Run
/ypm:project-status-updatefirst if~/.ypm/PROJECT_STATUS.mddoesn't exist
Display Format
- Project name
- Current Phase
- Next task
- Last update date
Priority Order
- Active projects (updated within 1 week)
- Projects with high implementation progress
- By Phase order
Recommended Action
- Suggest the highest priority project
- Clarify the next task to work on
CRITICAL: Reporting Guidelines
- Display "next task" as-is from PROJECT_STATUS.md
- DO NOT create new plans or features
- Include Issue number if GitHub Issues exist
- Add "(source unknown)" if information source is unclear
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.
- 6d ago First seen · 47 lines · 78 tokens per session scan A 6e82bdd83fd6
next-tasks is a skill published in the GitHub repository signalcompose/claude-tools (4 stars, last pushed 10d ago), licensed MIT. It adds 78 tokens to every session and 324 once invoked, about $0.0004 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
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…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.