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-bootstrapgit 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-bootstrap)<a href="https://agentmods.dev/skills/toolwright-adk/toolwright-monorepo/linear-bootstrap"><img src="https://agentmods.dev/badge/skills/toolwright-adk/toolwright-monorepo/linear-bootstrap/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-bootstrap"><img src="https://agentmods.dev/badge/skills/toolwright-adk/toolwright-monorepo/linear-bootstrap.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.00076 | $0.01291 |
| Opus 5.5 | $0.00030 | $0.00516 |
| Sonnet 5.5 | $0.00015 | $0.00258 |
| Haiku 4.5 | $0.00008 | $0.00129 |
Grade B, and why
linear-bootstrap scanned grade B with 1 finding 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.
Reads MCP configurationmediumAgent snooping
mcp.json carries server URLs and auth tokens; reading it lets a mod discover and abuse other integrations.
> 2. Verify the server is configured in `.mcp.json` with valid `LINEAR_API_KEY`, `LLM_API_KEY`, `LLM_BASE_URL`, and `LLM_MODEL` How it starts
The opening of the file, as written. The whole thing — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bootstrap a Linear Project
Create a fully structured Linear project — milestones, epics, issues, labels, and dependency chains — from a plain-English description.
Workflow
0. Verify prerequisites
Before starting, confirm the linear-bootstrap MCP tools are available by checking that mcp__linear-bootstrap__list-teams is callable. Attempt to list teams.
If the tool is not found or the call fails:
The linear-bootstrap MCP server is not running. To fix this:
- Check
/pluginfor MCP server errors- Verify the server is configured in
.mcp.jsonwith validLINEAR_API_KEY,LLM_API_KEY,LLM_BASE_URL, andLLM_MODEL- Try restarting Claude Code
- Test manually:
npx @toolwright-adk/linear-bootstrap(orbunxif npx is broken)
Stop here if the server is unavailable — do not attempt to proceed without it.
1. Identify the team
Use the team list from the prerequisite check. If there is only one team, use it. If there are multiple, ask the user which team to target.
The server automatically reads your team's existing labels, workflow states, and active projects before generating a plan. No extra step needed.
2. Gather the project description
Use the description from $ARGUMENTS if provided. Otherwise, ask the user what project they want to create.
Determine the project type from the description:
- feature — new user-facing functionality (default if unclear)
- infrastructure — internal tooling, platform work, DevOps
- api — public or internal API development
- migration — moving between systems, data migrations
Determine the complexity:
- small — a focused effort, 1-2 milestones, a few epics
- medium — a typical project, 2-4 milestones (default if unclear)
- large — a major initiative, 4-6 milestones, many epics
3. Generate and review the plan
Generate a project plan using the description, team, project type, and complexity. You will receive a plan reference and a summary with counts of milestones, epics, issues, and estimated points.
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 · 133 lines · 76 tokens per session scan B ebc009dd3c8b
linear-bootstrap is a skill published in the GitHub repository toolwright-adk/toolwright-monorepo (1 stars, last pushed 7mo ago), licensed MIT. It adds 76 tokens to every session and 1,291 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads mcp configuration). 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…