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/afk-surf/openbridge/linearnpx skills add AFK-surf/OpenBridge --skill lineargit clone --depth 1 https://github.com/AFK-surf/OpenBridgeWhat 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.00040 | $0.03170 |
| Opus 5 | $0.00020 | $0.01585 |
| Sonnet 5 | $0.00008 | $0.00634 |
| Haiku 4.5 | $0.00004 | $0.00317 |
Grade B, and why
linear 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 3d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
6. Restrict permissions on any file containing the token. Store a backup in `/home/sprite/.config/linear/env.sh` exporting `LINEAR_API_KEY`, chmod 600. Avoid printing `linear auth token` unless the user explicitly needs How it starts
The opening of the file, as written. The whole thing — 269 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Linear
Use this skill whenever the task involves Linear and the linear CLI is available or should be made available. Prefer CLI workflows for listing, creating, viewing, and updating Linear records when the requested task can be completed without the browser UI.
These notes are grounded against @schpet/linear-cli. The latest published version is 2.0.0; flag names differ from 1.9.1 in the auth subcommand. Always run linear auth login --help before attempting non-interactive auth, as flag names vary between versions.
Typical Goals
- Check existing issues before creating duplicates.
- Create issues with clear titles, descriptions, team assignment, labels, projects, priorities, or assignees when requested.
- View, update, comment on, assign, transition, or close issues.
- List teams, labels, and projects to resolve names, keys, and IDs.
- Configure reusable CLI authentication on a persistent VM.
- Use the Linear web UI only when the CLI lacks a needed operation or setup requires a personal API key.
Operating Principles
- Inspect
linear --helpand subcommand help when command syntax is uncertain; CLI versions can differ. - Prefer structured or explicit output flags when supported by the installed CLI. In
1.9.1,linear issue view --jsonandlinear label list --jsonsupport JSON;linear issue listdoes not. - Prefer managed OAuth over browser/API-key setup. When Linear credentials are missing, expired, or insufficient, use
RequestOAuthAuthorizationto connect the user's Linear account, then pass the saved credential toExec.credential_env. - Check existing issues before creating a new one unless the user explicitly asks to create a new issue.
- Do not claim an issue was found, created, or updated until a
linearcommand succeeds and returns an identifier or URL. - If auth or permissions fail, report the concrete blocker and the command that exposed it.
- Avoid relying on browser login alone as proof of CLI access; verify with real CLI reads.
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.
- 3d ago First seen · 269 lines · 40 tokens per session scan B 6f11c8c995ba
linear is a skill published in the GitHub repository AFK-surf/OpenBridge (424 stars, last pushed 2mo ago), licensed MIT. It adds 40 tokens to every session and 3,170 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…