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 rojim666/SztuCode --skill lineargit clone --depth 1 https://github.com/rojim666/SztuCodeWrote 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/rojim666/sztucode/linear)<a href="https://agentmods.dev/skills/rojim666/sztucode/linear"><img src="https://agentmods.dev/badge/skills/rojim666/sztucode/linear/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/rojim666/sztucode/linear"><img src="https://agentmods.dev/badge/skills/rojim666/sztucode/linear.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.00027 | $0.00931 |
| Opus 5.5 | $0.00011 | $0.00372 |
| Sonnet 5.5 | $0.00005 | $0.00186 |
| Haiku 4.5 | $0.00003 | $0.00093 |
Grade A, and why
linear 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- linear — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Linear
Overview
This skill provides a structured workflow for managing issues, projects & team workflows in Linear. It assumes the bundled Linear app is connected so the Linear tools are available for issues, projects, documentation, and team collaboration.
Prerequisites
- Linear tools must be connected and accessible via OAuth
- Confirm access to the relevant Linear workspace, teams, and projects
Required Workflow
Follow these steps in order. Do not skip steps.
Step 0: Connect the Linear app (if not already configured)
If Linear tools are unavailable, pause and ask the user to connect the Linear app:
- Enable the bundled Linear app for this plugin or session.
- Complete the Linear auth flow if Codex prompts for it.
- Restart Codex or the current session if the tools still do not appear.
After the app is connected, finish your answer and tell the user to retry so they can continue with Step 1.
Step 1
Clarify the user's goal and scope (e.g., issue triage, sprint planning, documentation audit, workload balance). Confirm team/project, priority, labels, cycle, and due dates as needed.
Step 2
Select the appropriate workflow (see Practical Workflows below) and identify the Linear tools you will need. Confirm required identifiers (issue ID, project ID, team key) before calling tools.
Step 3
Execute Linear tool calls in logical batches:
- Read first (list/get/search) to build context.
- Create or update next (issues, projects, labels, comments) with all required fields.
- For bulk operations, explain the grouping logic before applying changes.
Step 4
Summarize results, call out remaining gaps or blockers, and propose next actions (additional issues, label changes, assignments, or follow-up comments).
Available Tools
Issue Management: list_issues, get_issue, create_issue, update_issue, list_my_issues, list_issue_statuses, list_issue_labels, create_issue_label
Project & Team: list_projects, get_project, create_project, update_project, list_teams, get_team, list_users
What ships with it
4 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.
- 1mo ago First seen · 78 lines · 27 tokens per session scan A 8a409240f8f9
linear is a skill published in the GitHub repository rojim666/SztuCode (110 stars, last pushed yesterday), licensed MIT. It adds 27 tokens to every session and 931 once invoked, about $0.0001 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-30.
Other skills, from other repositories
file-a-task
File work into nohuman (taskadd) and check on it (taskstatus) via the nohuman MCP bridge, instead of doing the work inline.
handoffplan
Run /handoff to capture session data, then write a phased implementation plan that references it. Creates beads for tracking.
contract
A way to turn agreed design decisions into a formal software design document. The document gives coding agents or other implementers goals, decisions, rules, dependencies, non-goals, and open questions.
note
A lightweight decision log that appends settled decisions and references to a repository file. It records why a decision was made without copying the full source document.
standup-update
Generate a concise standup update from the user's recent work GitHub activity, including the previous work period and today. Use when the user asks what they worked on, requests a standup update, or invokes /standup.
retro
A post-run review process for a batch of coding tasks merged into the main branch. It collects repeated failures and turns them into proposed checks, review standards, or task templates.