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/vladolaru/claude-code-plugins/dig-into-linear-issuenpx skills add vladolaru/claude-code-plugins --skill dig-into-linear-issuegit clone --depth 1 https://github.com/vladolaru/claude-code-pluginsWrote 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/vladolaru/claude-code-plugins/dig-into-linear-issue)<a href="https://agentmods.dev/skills/vladolaru/claude-code-plugins/dig-into-linear-issue"><img src="https://agentmods.dev/badge/skills/vladolaru/claude-code-plugins/dig-into-linear-issue.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 | $0.00042 | $0.05479 |
| Opus 5 | $0.00021 | $0.02740 |
| Sonnet 5 | $0.00008 | $0.01096 |
| Haiku 4.5 | $0.00004 | $0.00548 |
Grade A, and why
dig-into-linear-issue 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 yesterday.
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 — 577 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dig Into Linear Issue
Overview
You are a thorough issue investigator. Your role is to verify issues before code changes happen.
Core principle: verify before you code - issues are frequently invalid, already fixed, duplicates, or different than described. Assume every issue needs verification until proven otherwise.
When to Use
- Asked to "work on", "fix", or "investigate" a Linear issue
- Given a Linear issue ID (e.g., WOOPLUG-1234) or URL
- Need to determine if an issue is still valid before implementing
Core Rules (in priority order)
- RULE 0: For bugs: Complete Root Cause Analysis before proposing any fix
- RULE 1: Fetch the actual issue yourself - never trust secondhand descriptions
- RULE 2: Check linked PRs before investigating - work may already be done
- RULE 3: Identify issue type first - bugs need validation; features don't
Prerequisites
| Tool | Purpose |
|---|---|
| Linear MCP server | Fetch Linear issue details, search issues, find PRs |
| chrome-devtools MCP | Browser-based investigation (for UI bugs) |
| Relevant build tools | Build assets before localhost testing |
Browser testing: Use browser-interaction skill for general browser testing, or woocommerce-browser-interaction for WooCommerce/WooPayments-specific workflows.
Team scope rule: Always filter searches by issue prefix (WOOPLUG-, WOOPMNT-, TRAPLAT-*) — different prefixes reference different repos.
Handling Tool Unavailability
Linear MCP server is required. Before starting, verify it is available by checking your tool list for mcp__linear-server__get_issue. If it is not available, STOP and ask the user:
Ask using the current host's input mechanism:
question: "The Linear MCP server is not available. This skill requires it to fetch issue details and comments. Please configure it and retry."
header: "Linear MCP required"
For other tools, assume available and adapt if they fail:
| Situation | Response |
|---|---|
| Browser MCP unavailable | Use code analysis path (4c) instead |
| Issue not found | Verify issue ID format; confirm with user |
What ships with it
3 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.
- yesterday First seen · 577 lines · 42 tokens per session scan A 47f1a02cd091
dig-into-linear-issue is a skill published in the GitHub repository vladolaru/claude-code-plugins (8 stars, last pushed yesterday), licensed MIT. It adds 42 tokens to every session and 5,479 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-09-03.
Other skills, from other repositories
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…
flow-next-tracker-sync
Project a flow-next spec to a tracker issue (Linear, GitHub, GitLab, Jira) and reconcile two-way. Use when asked to sync to a tracker. NOT plan-sync.
loop
Full execution protocol for MODE: LOOP — the compound-engineering loop: brainstorm → plan → build → review → improve, iterating under defense-in-depth stop conditions with generator/critic separation, durable resumable state, and mandatory compounding learning capture. Loaded on demand by the architect when the loop…
subagent-delegation
Canonical protocol for delegating GSD work to native Antigravity subagents — when to delegate, how to invoke, workspace isolation modes, and the inline fallback for older IDE versions.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.