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 MintedKenny/skills --skill linear-issuesgit clone --depth 1 https://github.com/MintedKenny/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/mintedkenny/skills/linear-issues)<a href="https://agentmods.dev/skills/mintedkenny/skills/linear-issues"><img src="https://agentmods.dev/badge/skills/mintedkenny/skills/linear-issues/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/mintedkenny/skills/linear-issues"><img src="https://agentmods.dev/badge/skills/mintedkenny/skills/linear-issues.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.00035 | $0.00966 |
| Opus 5.5 | $0.00014 | $0.00386 |
| Sonnet 5.5 | $0.00007 | $0.00193 |
| Haiku 4.5 | $0.00003 | $0.00097 |
Grade A, and why
linear-issues 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Draft Linear issue proposals
Decompose the findings just provided into well-scoped Linear issue drafts. Do not create issues when this skill runs. Stop after presenting the drafts and ask the user whether to file them.
Decomposition (one issue = one PR)
Each issue should correspond to one PR's worth of work. Always prefer fewer, larger PRs over many related smaller ones — splitting related work across PRs creates churn, review overhead, and merge ordering pain.
- Default: group aggressively. Combine findings into one issue whenever they touch the same area, share context, or would be easier to land together than separately.
- Only split when the work genuinely cannot share a PR — e.g., distinct subsystems with no overlap, different reviewers required, or one piece truly blocks the rest and needs to land first.
- Before creating multiple issues, ask: "Would landing these as one PR be simpler than coordinating two?" If yes, merge them.
- A larger issue is fine. Scope is bounded by one cohesive PR, not by issue size.
Per issue
- Describe the problem and its impact, not the solution. Investigation happens when the issue is picked up.
- Provide all relevant background so a fresh workspace can execute without re-discovering context.
- No implementation prescriptions — describe desired behavior, not the path to it.
- For triage-derived issues, preserve uncertainty: frame the task as investigation plus desired behavior unless the root cause is already proven.
Body template
## Context
What problem this solves or why this change is needed. Include symptoms, reproduction, or motivation — not implementation details.
## Task
What needs to change, at the level of desired behavior.
## Expected Outcome
What success looks like from the user's or system's perspective. Describe the end state, not the steps to get there.
## Notes
Constraints, things to avoid, or related context.
Defaults
Set sensible defaults for your Linear workspace:
What ships with it
1 file 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 · 78 lines · 35 tokens per session scan A 9830187cb27c
linear-issues is a skill published in the GitHub repository MintedKenny/skills (2 stars, last pushed 5mo ago), licensed MIT. It adds 35 tokens to every session and 966 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-08-31.
linear-issues compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| linear-issuesMintedKenny/skills | Skill | 2 | 5mo ago | MIT | A | 35 | Codex |
| imagegenopenai/codex | Skill | 134k | today | Apache-2.0 | A | 113 | Codex |
| local-ai-agentsmicrosoft/ai-agents-for-beginners | Skill | 79k | yesterday | MIT | A | 200 | Claude Code, Codex |
| playwright-climicrosoft/playwright | Skill | 100k | yesterday | Apache-2.0 | A | 19 | Claude Code |
| browser-automationopenclaw/openclaw | Skill | 394k | today | MIT | A | 36 | Claude Code |
| systematic-debuggingobra/superpowers | Skill | 314k | 4d ago | MIT | A | 21 | Claude Code |
| next-cache-components-adoptionvercel/next.js | Skill | 143k | today | MIT | A | 95 | Claude Code |