What is linear_ticket_design_brief?

A command for posting a structured design and scoping brief to a Linear ticket. Linear is a tool for managing issues and project work.

It is for reading a ticket and its comments, preparing a grounded brief, and posting that brief and its questions back to Linear.

It turns an existing ticket into a focused set of design considerations and questions before implementation begins. It stops when the ticket reference is missing or unclear instead of guessing.

linear_ticket_design_brief — Command by allisoneer/agentic

Install

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.

Clone the repo

git clone --depth 1 https://github.com/allisoneer/agentic_auxilary

Made for: Claude Code, OpenCode.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/allisoneer/agentic_auxilary/linear_ticket_design_brief/github.svg)](https://agentmods.dev/commands/allisoneer/agentic_auxilary/linear_ticket_design_brief)

Your own site

<a href="https://agentmods.dev/commands/allisoneer/agentic_auxilary/linear_ticket_design_brief"><img src="https://agentmods.dev/badge/commands/allisoneer/agentic_auxilary/linear_ticket_design_brief/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/allisoneer/agentic_auxilary/linear_ticket_design_brief"><img src="https://agentmods.dev/badge/commands/allisoneer/agentic_auxilary/linear_ticket_design_brief.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 16 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,845 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00016	$0.01845
Opus 5.5	$0.00006	$0.00738
Sonnet 5.5	$0.00003	$0.00369
Haiku 4.5	$0.00002	$0.00185

Measured 1mo ago against content hash 89966c5bc25d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

linear_ticket_design_brief 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 1mo 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.

.opencode/command/linear_ticket_design_brief.md · 169 lines

How it starts

The opening of the file, as written. The whole thing — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.

<workflow_contract>

Follow all 6 steps in order.
Use todowrite in Step 2 and keep exactly one todo in_progress at a time.
Treat <userMessage> as loose natural language with no first-pass flags or modifiers.
Require exactly one Linear ticket reference; ask and stop if it is missing or ambiguous.
Full ticket read means linear_read_issue plus repeated linear_get_issue_comments until has_more=false; stop fetching comments immediately after has_more=false and do not call again.
Before any synthesis or Linear posting, delegate full ticket intake, corpus export, and artifact-grounding handoff to one bounded Linear-capable child session. That delegated intake/export must:
- filename: linear-{lowercase-key}-ticket.md
- body includes Ticket corpus schema: linear-ticket-corpus@v1 + snapshot timestamp + explicit snapshot disclaimer
- include full ticket description plus full comment history with authorship and timestamps when available
- write the artifact itself and run thoughts_sync immediately afterward
- return enough grounded ticket identifiers plus the saved artifact path for the orchestrator to continue
This command is strictly Linear comment-only: post exactly one final Linear comment with linear_add_comment, and do not mutate Linear issue fields or perform any other external workflow mutations such as creating plans, implementing code, committing, pushing, or creating/updating PRs.
Duplicate runs may append fresh comments and create fresh design/scoping brief artifacts; the ticket corpus artifact should be refreshed by overwriting the stable linear-{lowercase-key}-ticket.md file.
Bounded research is allowed only when needed to avoid guessing.
Hard stop immediately after posting the Linear comment and returning the compact summary. </workflow_contract>

<step_1>

Step 1: Resolve Exactly One Ticket Reference

Parse <userMessage> as loose natural language.
Accept any of these as sufficient ticket references:
- a Linear issue key such as ENG-123
- a Linear issue URL
- another identifiable Linear issue reference that a bounded Linear child session can resolve responsibly
If no Linear ticket reference is present, ask the user for one and stop.
If multiple plausible tickets are referenced and one is not clearly primary, ask one concise clarification question and stop.

</step_1>

<step_2>

Read the full file on GitHub · 169 lines

Changes

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.

1mo ago First seen · 169 lines · 16 tokens per session scan A 89966c5bc25d

Subscribe to this mod's changes

linear_ticket_design_brief is a command published in the GitHub repository allisoneer/agentic_auxilary (79 stars, last pushed 6d ago), licensed MIT. It adds 16 tokens to every session and 1,845 once invoked, about $0.0001 per session on Opus 5.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-09-08.

Project management

template

Manage issue templates for streamlined issue creation.

gastownhall/beads · 0 tokens

fest-show

Show festival progression (in-progress tasks, roadmap, and dependency view).

Obedience-Corp/festival · 17 tokens

add-note

Add an internal or external note to a ConnectWise PSA ticket.

WYRE-AI/msp-claude-plugins · 12 tokens

dispatcher

Use when you want the orchestrator to pick the next repo to work on across your whole portfolio — it enumerates candidate repos below the confinement root, resolves free/busy from each repo's session.lock lease, ranks the FREE ones by backlog priority × staleness × readiness, recommends the single most worthwhile one…

Kanevry/session-orchestrator · 185 tokens

sync-linear

Sync current work with Linear ticket status.

bybren-llc/safe-agentic-workflow · 0 tokens

plc-project-status

Read .claude/skills/plc-project-status/SKILL.md and execute its official procedure. Target: $ARGUMENTS.

miyatti777/ai-plc · 14 tokens