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-sync-project-workgit 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-sync-project-work)<a href="https://agentmods.dev/skills/openly-useful/linear-project-skills/linear-sync-project-work"><img src="https://agentmods.dev/badge/skills/openly-useful/linear-project-skills/linear-sync-project-work.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.1 | $0.00084 | $0.00663 |
| Opus 5 | $0.00042 | $0.00331 |
| Sonnet 5 | $0.00017 | $0.00133 |
| Haiku 4.5 | $0.00008 | $0.00066 |
Grade A, and why
linear-sync-project-work 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 7d 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Linear Sync Project Work
Synchronize material implementation evidence without turning routine activity into tracker noise.
Establish the scope anchor
Before any Linear write, resolve and read back:
- one canonical Linear project ID;
- its allowed team IDs and required project-code label;
- canonical repository and local root;
- active issue mapping, milestones, dependencies, and status definitions;
- project-specific completion and safety gates.
Derive the anchor from project metadata, repository handoff files, or explicit user input. If multiple projects match, stop and ask which is canonical. Do not update by product-name similarity alone.
Session workflow
- Read the installed Linear workflow skill when available.
- At work start, read the project and relevant scoped issues. Confirm each candidate issue belongs to the project and carries the required label.
- Map the requested implementation to the smallest existing issue whose objective and paths cover it.
- If no issue covers the work:
- search the project and team for semantic and source-marker duplicates;
- create a new issue only for a durable, independently actionable gap;
- assign the canonical project, allowed team, project-code label, milestone, and evidence-supported dependencies.
- During work, update Linear after material events only: validated design decisions, commits, pull requests, test or review results, confirmed blockers, scope changes, or completed definitions of done.
- Prefer append-only evidence comments for progress. Edit canonical issue fields only when the underlying title, objective, acceptance criteria, priority, milestone, dependency, or state truly changed.
- Read references/evidence-update-contract.md before changing status, declaring completion, or publishing a project status update.
- At work end, attach the freshest evidence, state what remains, update blockers and dependencies if needed, and read back all mutated records.
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.
- 7d ago First seen · 54 lines · 84 tokens per session scan A 47f3bd6660bf
linear-sync-project-work is a skill published in the GitHub repository Openly-Useful/linear-project-skills (0 stars, last pushed 15d ago), licensed MIT. It adds 84 tokens to every session and 663 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.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
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…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.