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 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/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/toolwright-adk/toolwright-monorepo/linear-status"><img src="https://agentmods.dev/badge/skills/toolwright-adk/toolwright-monorepo/linear-status.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.00054 | $0.00781 |
| Opus 5.5 | $0.00022 | $0.00312 |
| Sonnet 5.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 1mo 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.
- 1mo 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 7mo ago), licensed MIT. It adds 54 tokens to every session and 781 once invoked, about $0.0002 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.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
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.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…