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 agentmods add skills/toolwright-adk/toolwright-monorepo/linear-statusnpx skills add toolwright-adk/toolwright-monorepo --skill linear-statusgit clone --depth 1 https://github.com/toolwright-adk/toolwright-monorepoWrote 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/toolwright-adk/toolwright-monorepo/linear-status)<a href="https://agentmods.dev/skills/toolwright-adk/toolwright-monorepo/linear-status"><img src="https://agentmods.dev/badge/skills/toolwright-adk/toolwright-monorepo/linear-status.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 | $0.00054 | $0.00781 |
| Opus 5 | $0.00027 | $0.00391 |
| Sonnet 5 | $0.00011 | $0.00156 |
| Haiku 4.5 | $0.00005 | $0.00078 |
Grade A, and why
linear-status 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 4d 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Linear Project Status
Check project health and optionally post a status update to Linear.
Workflow
0. Verify prerequisites
Confirm both MCP tool sets are available:
mcp__linear__get_project(official Linear MCP)mcp__linear-bootstrap__introspect-workspace(linear-bootstrap MCP)
If the official Linear MCP is missing, you can still provide a limited report using linear-bootstrap's introspect-workspace. If linear-bootstrap is missing, you can still read project state — you just won't have team convention context.
Tell the user which tools are available and proceed with what you have.
1. Find the project
Use the project name or ID from $ARGUMENTS. If not provided, use mcp__linear__list_projects to show available projects and ask which one.
2. Gather project state
In parallel where possible:
mcp__linear__get_project— project overview, dates, statusmcp__linear__list_issuesfiltered by project — all issues with their statusesmcp__linear__list_milestones— milestone progressmcp__linear-bootstrap__introspect-workspace— team conventions (workflow states, cycle info)
3. Synthesize the report
Present a structured summary:
Progress:
- Overall completion (done issues / total issues)
- Per-milestone breakdown with % complete
- Current cycle progress (if cycles enabled)
Health indicators:
- Blocked issues (issues with unresolved dependencies)
- Stale issues (in-progress but no recent activity)
- High-priority unassigned issues
- Overdue milestones
Recent activity:
- Issues completed recently
- Issues moved to in-progress
4. Offer to post a status update
Ask: "Want me to post this as a status update to Linear?"
If yes, use mcp__linear__save_status_update with a concise version of the report.
Examples
User: /linear-status Checkout Redesign
Agent: ## Checkout Redesign — Status
**Progress:** 62% complete (31/50 issues done)
- ✅ M1: Payment Integration — 100% (8/8)
- 🔄 M2: Cart Overhaul — 75% (9/12)
- 🔄 M3: Checkout Flow — 47% (14/30)
**Health:**
- 2 blocked issues in M3 (waiting on API team)
- 1 high-priority unassigned: "Handle failed payment retry"
- M2 target date is tomorrow — 3 issues remaining
Want me to post this as a status update to Linear?
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.
- 4d ago First seen · 93 lines · 54 tokens per session scan A 7739abc87e92
linear-status is a skill published in the GitHub repository toolwright-adk/toolwright-monorepo (1 stars, last pushed 5mo ago), licensed MIT. It adds 54 tokens to every session and 781 once invoked, about $0.0003 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
agile-product-owner
../../../product-team/agile-product-owner/skills/agile-product-owner/SKILL.md.
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…
subagent-delegation
Canonical protocol for delegating GSD work to native Antigravity subagents — when to delegate, how to invoke, workspace isolation modes, and the inline fallback for older IDE versions.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
project-init
Scaffold an unconfigured directory into a configured pi project. Interactive, profile-driven: previews the planned writes, then writes AGENTS.md, .pi/settings.json and prompt files — optionally also a knowledge base, an openspec/ scaffold, and user-global /.pi/agent/settings.json. Use on a bare directory, or when the…