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 Openly-Useful/linear-project-skills --skill linear-reconcile-project-historygit clone --depth 1 https://github.com/Openly-Useful/linear-project-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/openly-useful/linear-project-skills/linear-reconcile-project-history)<a href="https://agentmods.dev/skills/openly-useful/linear-project-skills/linear-reconcile-project-history"><img src="https://agentmods.dev/badge/skills/openly-useful/linear-project-skills/linear-reconcile-project-history/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/openly-useful/linear-project-skills/linear-reconcile-project-history"><img src="https://agentmods.dev/badge/skills/openly-useful/linear-project-skills/linear-reconcile-project-history.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.00086 | $0.00826 |
| Opus 5 | $0.00043 | $0.00413 |
| Sonnet 5 | $0.00017 | $0.00165 |
| Haiku 4.5 | $0.00009 | $0.00083 |
Grade A, and why
linear-reconcile-project-history 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 11d 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Linear Reconcile Project History
Perform a read-first sweep, preserve identity and relations, and keep historical evidence visibly non-active.
Resolve the destination
- Read the installed Linear workflow skill when available.
- Search projects by exact name, ID, code, repository URL, and known aliases.
- Read candidate project descriptions, teams, labels, resources, milestones, and issues.
- Select one destination only when the evidence is unique. If none exists, hand off to
$linear-bootstrap-scoped-project. If multiple candidates remain, request the destination choice before any write. - Freeze a scope allowlist: destination project ID, allowed product aliases, repository URLs, work-stream IDs, project-code labels, source containers, and time bounds.
Discover related work
Search workspace-wide for:
- exact project-code labels or source markers;
- canonical repository, pull-request, and document URLs;
- exact work-stream IDs and stable external issue IDs;
- product aliases combined with matching objective or component evidence;
- unassigned or misfiled issues whose descriptions identify the canonical project.
Also inspect allowlisted local, GitHub, and legacy project sources read-only. Do not treat a fuzzy title match alone as related work.
Read references/matching-and-history-contract.md before classifying or mutating candidates.
Classify and plan
Classify each candidate as:
move-existing: an existing Linear issue that is provably part of the destination project;historical-capture: legacy evidence not represented by an existing Linear issue;already-correct: already linked and classified properly;duplicate-or-conflict: requires reconciliation without another issue;ambiguous: report only;unrelated: exclude.
Present a compact mutation plan with exact IDs and evidence. Restrict writes to high-confidence move-existing and deterministic historical-capture items.
What ships with it
2 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.
- 11d ago First seen · 70 lines · 86 tokens per session scan A 14dfb049eed7
linear-reconcile-project-history is a skill published in the GitHub repository Openly-Useful/linear-project-skills (0 stars, last pushed 19d ago), licensed MIT. It adds 86 tokens to every session and 826 once invoked, about $0.0004 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-create-meet-space
Create a Google Meet meeting space and share the join link.
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…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
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…
magpie-security-issue-import-from-md
Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.
remove
Remove a deployed framework or addon from the current workspace.