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 tommyvo/useful-prompts --skill linear-implementation-subticketsgit clone --depth 1 https://github.com/tommyvo/useful-promptsWrote 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/tommyvo/useful-prompts/linear-implementation-subtickets)<a href="https://agentmods.dev/skills/tommyvo/useful-prompts/linear-implementation-subtickets"><img src="https://agentmods.dev/badge/skills/tommyvo/useful-prompts/linear-implementation-subtickets/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/tommyvo/useful-prompts/linear-implementation-subtickets"><img src="https://agentmods.dev/badge/skills/tommyvo/useful-prompts/linear-implementation-subtickets.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.00082 | $0.00810 |
| Opus 5 | $0.00041 | $0.00405 |
| Sonnet 5 | $0.00016 | $0.00162 |
| Haiku 4.5 | $0.00008 | $0.00081 |
Grade A, and why
linear-implementation-subtickets 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 10d 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Linear implementation subtickets
Turn one Linear issue into implementation-ready [API] / [UI] subtickets that a coding agent can use as the prompt.
Repos (unless the user names others):
- Backend:
~/code/soraban-api - Frontend:
~/code/soraban-react-app
Required input
The skill takes a Linear issue ID (e.g. SOR-25066).
- If the user passed an ID (in the message, a Linear URL, or
SOR-\d+), use it. - If none was passed, stop and ask for it. Do not guess, search Slack, or pick a recent issue.
- Do not proceed until you have an ID.
Always start in Plan mode
Before any investigation, ticket drafting, or Linear writes:
- If the session is not already in Plan mode, switch to Plan mode (
SwitchMode→plan). Explain that this skill always plans first. - Stay in Plan mode through research and the implementation plan.
- Do not create Linear issues, edit code, or run mutating commands until the user accepts the plan.
- After the user accepts, execute: create the subtickets only (no product code unless they ask).
Workflow (Plan mode)
1. Load the Linear issue
Fetch the issue (description, comments, attachments, related issues, project, team, labels, priority). Read enough to know the product intent; do not invent requirements that are not in the issue or code.
2. Investigate both codebases
Read-only. Map the smallest set of files that must change.
- API: controllers, serializers, models, routes, request specs that already own this surface.
- UI: pages, filters, providers, API clients, types, specs for the same surface.
- Note existing filter/query patterns so the new contract matches them.
Ask the user only when a choice changes the plan (filter semantics, which UX paths, scope). Prefer 1–2 questions with sensible defaults.
3. Fix the API contract first
Design the request/response (or query params) the frontend will call as if the API already shipped. Both tickets must use this exact contract so API and UI can ship in parallel.
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.
- 10d ago First seen · 87 lines · 82 tokens per session scan A 3bf8386c5785
linear-implementation-subtickets is a skill published in the GitHub repository tommyvo/useful-prompts (3 stars, last pushed 12d ago), licensed Unlicense. It adds 82 tokens to every session and 810 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.
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.
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.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.