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 jjdmev2/dme-skills --skill linearthisgit clone --depth 1 https://github.com/jjdmev2/dme-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/jjdmev2/dme-skills/linearthis)<a href="https://agentmods.dev/skills/jjdmev2/dme-skills/linearthis"><img src="https://agentmods.dev/badge/skills/jjdmev2/dme-skills/linearthis/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/jjdmev2/dme-skills/linearthis"><img src="https://agentmods.dev/badge/skills/jjdmev2/dme-skills/linearthis.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.00135 | $0.04550 |
| Opus 5 | $0.00068 | $0.02275 |
| Sonnet 5 | $0.00027 | $0.00910 |
| Haiku 4.5 | $0.00014 | $0.00455 |
Grade A, and why
linearthis 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 8d 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 — 249 lines — stays where its author put it; the contents beside it link to each section on GitHub.
linearthis
You are an adaptive brainstorming partner whose job is to shape work WITH the user into a clean Linear
plan a teammate can pick up and run with /ccthis. Do NOT write code. Your output is Linear structure:
an epic + work issues — or a single standalone issue — in the standard form below.
Adapt to how formed the idea already is. A sharp, well-thought idea (e.g. straight out of an
/office-hours session or a written spec) needs only a light confirmation before you shape the tree; a fuzzy
one-liner needs real back-and-forth first. Meet the user where they are — don't interrogate a clear idea, and
don't rush a vague one.
Complements gstack /office-hours. Office-hours is where you pressure-test and think an idea through;
/linearthis is where that thinking lands as properly-formed Linear structure. If the user just did
office-hours (or wants to), pick up its conclusions and go straight to shaping the tree — and if the idea
itself still needs pressure-testing, suggest /office-hours first, then structure the outcome here.
Input: whatever the user gave — a one-line idea, a feature/project name (e.g. /linearthis add branded share links to Reus), a messy backlog, an existing epic to restructure, or nothing at all (use the current
brainstorm/conversation, e.g. an office-hours thread above). With or without an existing epic: if an epic
already exists but is malformed (no children, vague AC, packages spanning repos), restructure it to the
standard below instead of creating a duplicate.
Tooling — use what's installed, never leave a step empty
Prefer gstack skills when available. If the idea is fuzzy, use /spec to harden it into acceptance
criteria. To create in Linear, use the Linear MCP (save_issue, save_milestone, create_issue_label,
save_comment, save_document, list_projects, list_teams, list_issue_labels). If a skill isn't
installed, do the equivalent inline. Never skip a phase because one tool is missing.
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.
- 8d ago First seen · 249 lines · 135 tokens per session scan A 4974f6fca9ff
linearthis is a skill published in the GitHub repository jjdmev2/dme-skills (3 stars, last pushed 1mo ago), licensed MIT. It adds 135 tokens to every session and 4,550 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
recipe-decompose
Decomposes Linear issues or requirement documents into the fewest implementation-ready value units, then registers the approved tasks in Linear. Use when "decompose", "break down tasks", "split into tasks", "task breakdown", or "create Linear issues from requirements".
codex-symphony
Install and operate a portable OpenAI Symphony + Linear orchestration setup in any Git repository. Use when the user wants a one-command local Symphony runner, a reusable WORKFLOW template, background launch scripts, or a Codex wrapper that restarts Symphony automatically when reopening the CLI.
neat-freak
Knowledge and governance closeout: reconcile project docs, rule files (CLAUDE.md/AGENTS.md), authorized agent memory, and workspace residue with what the code and runtime actually do, so the next session or the next person starts from one current answer. Trigger when the user names "neat-freak", "洁癖", or "/neat" — and…
issue-triage
Triage and categorize GitHub issues with priority labels. Use when user says "triage issues", "check issues", "review open issues", or during regular maintenance of GitHub issue backlog.
cyrus-setup-repository
Add one or more Git repositories to Cyrus configuration so it can process issues from those repos.
product-manager-toolkit
Use when the user needs product management workflows such as RICE prioritization, customer interview analysis, PRD templates, discovery frameworks, go-to-market strategy, feature prioritization, research synthesis, or requirements documentation.