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/onatm/agent-skills/linear-task-planningnpx skills add onatm/agent-skills --skill linear-task-planninggit clone --depth 1 https://github.com/onatm/agent-skillsWrote 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/onatm/agent-skills/linear-task-planning)<a href="https://agentmods.dev/skills/onatm/agent-skills/linear-task-planning"><img src="https://agentmods.dev/badge/skills/onatm/agent-skills/linear-task-planning.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.00034 | $0.00716 |
| Opus 5 | $0.00017 | $0.00358 |
| Sonnet 5 | $0.00007 | $0.00143 |
| Haiku 4.5 | $0.00003 | $0.00072 |
Grade A, and why
linear-task-planning 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.
How it starts
The opening of the file, as written. The whole thing — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Linear Task Planning
Turn approved engineering plans into clear, self-contained Linear issues. Use the official Linear MCP for discovery and mutations. Do not implement code or edit project files.
Source Authority
Read only the project material needed for the requested scope. Resolve conflicts in this order unless the project says otherwise:
- Accepted architecture decisions.
- Architecture and component designs.
- Roadmap phase gates and phase plans.
- The user's current instruction.
Do not generate implementation work that depends on an unresolved decision. Create a decision or research issue only when the source plan explicitly allows it or the user approves it.
Discover Linear Context
Use Linear MCP read tools before proposing work:
- Identify the workspace and candidate team.
- Find an existing project before proposing a new one.
- Read available statuses, labels, milestones, cycles, and issue relationships.
- Search for matching issue titles and source identifiers to prevent duplicates.
- Ask the user when team or project placement is ambiguous.
Never invent Linear IDs, status names, labels, projects, or relationships.
Decompose Work
Generate tasks from one approved phase, work package, or implementation plan at a time.
- Target roughly half a day to three engineering days per issue.
- Split work above five days or work containing independent contracts.
- Preserve prerequisite order and capability gates.
- Prefer a vertical, observable outcome over vague layer activity.
- Separate reusable harnesses, research decisions, persisted-format changes, and migrations when independently deliverable.
- Do not add speculative features, abstractions, or compatibility work.
Each issue must be implementable without hidden decisions and contain:
- Outcome.
- Scope.
- Non-goals.
- Prerequisites and dependencies.
- Affected contracts or components.
- Proposed implementation steps when established by source material.
- Failure cases.
- Required tests and benchmarks.
- Documentation impact.
- Acceptance evidence.
What ships with it
1 file 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.
- 6d ago First seen · 96 lines · 34 tokens per session scan A 9afcf47d491f
linear-task-planning is a skill published in the GitHub repository onatm/agent-skills (7 stars, last pushed 1mo ago), licensed MIT. It adds 34 tokens to every session and 716 once invoked, about $0.0002 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
workers-best-practices
Reviews and authors Cloudflare Workers code against production best practices. Load when writing new Workers, reviewing Worker code, configuring wrangler.jsonc, or checking for common Workers anti-patterns (streaming, floating promises, global state, secrets, bindings, observability). Biases towards retrieval from…
find-journalists
Build, refine, dedupe, and enrich small fit-checked journalist lists for newsjack campaigns. Uses the newsjack CLI (preferred) or the medialyst MCP for news search and journalist enrichment, and falls back to a best-effort local mode with no verified contacts; the agent owns how returned data is organized.
story-origin-check
Recover the first public timestamp and canonical major coverage for a newsjacking signal, then decide whether newer coverage is the same story, a different story, or a materially new development.
relevance-coarse-filter
Cheap, high-recall first-pass filter that removes obvious junk from a detector candidate pool before expensive story-origin research and PR judgment. Decides keep, monitoronly, or reject — never ranks, writes angles, verifies dates, or decides whether to pitch.
annotating-task-lineage
Annotate Airflow tasks with data lineage using inlets and outlets. Use when the user wants to add lineage metadata to tasks, specify input/output datasets, or enable lineage tracking for operators without built-in OpenLineage extraction.
managing-astro-local-env
Manage local Airflow environment with Astro CLI (Docker and standalone modes). Use when the user wants to start, stop, or restart Airflow, view logs, query the Airflow API, troubleshoot, or fix environment issues. For project setup, see setting-up-astro-project.