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 mthines/agent-skills --skill batch-linear-ticketsgit clone --depth 1 https://github.com/mthines/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/mthines/agent-skills/batch-linear-tickets)<a href="https://agentmods.dev/skills/mthines/agent-skills/batch-linear-tickets"><img src="https://agentmods.dev/badge/skills/mthines/agent-skills/batch-linear-tickets.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 157 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Excessive Agency · line 473 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00146 | $0.05530 |
| Opus 5 | $0.00073 | $0.02765 |
| Sonnet 5 | $0.00029 | $0.01106 |
| Haiku 4.5 | $0.00015 | $0.00553 |
Grade A, and why
batch-linear-tickets 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 7d 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 — 477 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Batch Linear Ticket Resolver
Orchestrate parallel analysis and resolution of multiple Linear tickets — bug fixes and feature work. This skill owns batch-level concerns: per-ticket type classification, parallel fan-out of the right analysis tools, cross-ticket correlation, the user-facing approval gate, and Linear writeback.
Per-ticket investigation lives in linear-ticket-investigator. Per-ticket bug root-cause
analysis is dispatched to the rca-investigator agent — it runs holistic-analysis (fix) +
confidence (analysis) in an isolated context per ticket, so N bug analyses run in
parallel and none of their verbose walkthroughs land in this orchestrator's window. Per-ticket
planning lives in aw-planner. Per-ticket implementation lives in aw-executor. This skill wires
them together for batch operation.
Architecture
Phase 1: Per-Ticket Analysis → per ticket: classify type → investigator → (video-analyser if video flagged) → (rca-investigator if bug, carries confidence) | confidence(plan) if feature
Phase 2: Cross-Ticket Correlation → detect shared root causes, file conflicts, duplicates
Phase 3: Approval Gate → user picks tickets to ship
Phase 4: Parallel Execution → fan out aw-planner + aw-executor for approved tickets
Phase 5: Results & Linear Updates → status table + per-ticket PR comments
Phase 1's analysis runs once per ticket. Phase 4 dispatches aw-planner directly using the
analysis from Phase 1.
Prerequisites
| Dependency | Purpose | Required? |
|---|---|---|
Linear MCP (mcp__claude_ai_Linear__* or mcp__linear-server__*) |
Read tickets + labels, post PR comments | Yes |
linear-ticket-investigator agent |
Per-ticket evidence extraction | Yes |
rca-investigator agent (agents/rca-investigator.md) |
Per-ticket bug root-cause analysis — isolated + parallel; carries confidence(analysis) in its Root-Cause Record |
Yes (for bug tickets) |
holistic-analysis skill |
Run transitively inside rca-investigator; in-context fallback if the agent is unavailable |
Yes (for bug tickets) |
confidence skill |
Feature-ticket gate scoring (bug score comes from rca-investigator) |
Yes |
video-analyser skill |
Analyse a video / screen-recording attachment flagged on a ticket (Step 1b.5) | Optional — skips silently if absent or no video flagged |
aw-planner + aw-executor agents (from autonomous-workflow) |
Phase 4 dispatch | Yes |
gh CLI |
PR creation by aw-executor |
Yes |
gw CLI |
Worktree management (planner) | Recommended |
lorekit-memory skill (LoreKit memory.* tools) |
batch-lessons self-improvement loop (read Phase 1, write Phase 5) |
Optional — loop is a silent no-op if memory.* is not connected |
| Project domain-navigator skill | Investigation accuracy in monorepos | Optional — see Customization |
What ships with it
6 files 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.
- 7d ago First seen · 477 lines · 146 tokens per session scan A 88e330445453
batch-linear-tickets is a skill published in the GitHub repository mthines/agent-skills (12 stars, last pushed 2d ago), licensed MIT. It adds 146 tokens to every session and 5,530 once invoked, about $0.0007 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
stakeholder-communication-and-status-updates
Guides writing narrative-style stakeholder status updates and strategy memos instead of bullet-point decks, grounded in Amazon's 6-page narrative memo discipline. Use when the user asks to "write a status update," "draft a weekly update for stakeholders," "write a project update email," "prepare a 6-pager," "turn…
planning-and-task-breakdown
Breaks an existing spec or clear requirement into a dependency-ordered, sized task list with checkpoints and parallelization notes. Use when a task feels too large to start, when scope needs estimating, or when work can be split across parallel agents/sessions. For a single lightweight plan document for one request…
spec-driven-development
Writes a structured, human-reviewed specification before any code, deriving implementation from that written contract rather than from a vague request. Use when starting a new project or feature with no spec yet, when requirements are ambiguous or only exist as an idea, or before an architectural decision on a change…
feature-prioritization-frameworks
Guides prioritizing a backlog of features or requests using RICE scoring (Reach x Impact x Confidence / Effort) as the primary quantitative method, with MoSCoW (Must/Should/Could/Won't) for stakeholder negotiation and the Kano model for classifying features by satisfaction-curve shape. Use when the user asks to…
roadmapping-and-tradeoff-communication
Guides building Now/Next/Later, outcome-based roadmaps and communicating tradeoff decisions to stakeholders who push for a specific feature with a hard date. Use when the user asks to "build a roadmap," "create a Now/Next/Later roadmap," "turn this feature list into an outcome roadmap," "respond to a stakeholder…
writing-product-requirements
Guides writing product requirements as a PR-FAQ (press release plus frequently-asked-questions) using Amazon's working-backwards methodology, or as a lighter PRD when a PR-FAQ is overkill. Use when the user asks to "write a PR-FAQ", "write product requirements", "draft a PRD", "work backwards from the customer"…