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 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/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/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="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to high
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 →
- high Data Exfiltration · line 292 Code or instructions that leak agent conversation context to external services, potentially exposing sensitive user interactions.Fix: Remove any code that sends prompts, responses, or session data externally. Preserve user privacy; never exfiltrate conversation content.
- high Data Exfiltration · line 397 Code or instructions that leak agent conversation context to external services, potentially exposing sensitive user interactions.Fix: Remove any code that sends prompts, responses, or session data externally. Preserve user privacy; never exfiltrate conversation content.
- high Data Exfiltration · line 483 Code or instructions that leak agent conversation context to external services, potentially exposing sensitive user interactions.Fix: Remove any code that sends prompts, responses, or session data externally. Preserve user privacy; never exfiltrate conversation content.
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.00042 | $0.05479 |
| Opus 5.5 | $0.00017 | $0.02192 |
| Sonnet 5.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 2mo 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 — 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.
- 2mo ago 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 5d ago), licensed MIT. It adds 42 tokens to every session and 5,479 once invoked, about $0.0002 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-03.
dig-into-linear-issue compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| dig-into-linear-issuevladolaru/claude-code-plugins | Skill | 8 | 5d ago | MIT | A | 42 | Claude Code |
| systematic-debuggingopen-metadata/OpenMetadata | Skill | 16k | today | Apache-2.0 | A | 37 | Claude Code |
| log-error-digestzebbern/claude-code-guide | Skill | 4.7k | today | MIT | A | 71 | Claude Code, Codex |
| incident-response-incident-responsermyndharis/antigravity-skills | Skill | 2.0k | 4d ago | MIT | A | 36 | Claude Code, Codex |
| cwv-optimizeradobe/skills | Skill | 324 | today | Apache-2.0 | A | 112 | Claude Code |
| ci-fixersipyourdrink-ltd/bernstein | Skill | 1.2k | today | Apache-2.0 | A | 15 | Claude Code, Codex |
| diagnosing-missing-recordingsPostHog/posthog | Skill | 41k | today | none | A | 76 | Claude Code, Codex |