Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/nodnarbnitram/claude-code-extensionsnpx agentmods add commands/nodnarbnitram/claude-code-extensions/create-linear-prWrote 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/commands/nodnarbnitram/claude-code-extensions/create-linear-pr)<a href="https://agentmods.dev/commands/nodnarbnitram/claude-code-extensions/create-linear-pr"><img src="https://agentmods.dev/badge/commands/nodnarbnitram/claude-code-extensions/create-linear-pr/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/commands/nodnarbnitram/claude-code-extensions/create-linear-pr"><img src="https://agentmods.dev/badge/commands/nodnarbnitram/claude-code-extensions/create-linear-pr.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.00020 | $0.00912 |
| Opus 5.5 | $0.00008 | $0.00365 |
| Sonnet 5.5 | $0.00004 | $0.00182 |
| Haiku 4.5 | $0.00002 | $0.00091 |
Grade A, and why
create-linear-pr 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Linear PR Workflow
Create a Linear ticket, branch from it, commit changes, and open a pull request.
Activate the linear skill first and use its wrapper scripts for all Linear operations. Do not call another Linear CLI directly from this workflow.
Context
- Current git status: !
git status --short - Current branch: !
git branch --show-current - Staged changes: !
git diff --cached --stat - Unstaged changes: !
git diff --stat
Arguments
$1- Team identifier (e.g.,ICE-T)$2- Optional ticket title. If not provided, derive from the changes.
If team is missing, ask the user for it.
Prerequisites
- Changes should already be made to files (staged or unstaged)
- The
linearskill must be available and its wrapper scripts must run successfully ghCLI must be authenticated
Steps
Track these steps as TODOs and complete them one by one.
-
Validate arguments - Ensure
$1(team) is provided.- If team is missing, ask the user for it.
-
Review changes - Analyze the context above to understand what will be committed.
- If no changes exist (no staged or unstaged files), stop and inform the user.
- Summarize the changes for the user.
- If
$2(title) not provided, derive a concise title from the changes.
-
Create Linear ticket - Use the
linearskill wrapper script:uv run .claude/skills/linear/scripts/create-ticket.py "<title from $2 or derived>" --team $1 --description "<auto-generated description>" --json- Generate a meaningful description based on the changes being committed.
- Extract
identifier,branchName, andurlfrom the JSON response.
-
Create branch - Create and checkout the branch:
git checkout -b <branchName from Linear response> -
Stage and commit - Stage relevant changes and commit:
git add <relevant files> git commit -m "$(cat <<'EOF' <TICKET-ID>: <title> <detailed description of changes> EOF )"- Always use HEREDOC for commit messages.
- Include the ticket ID prefix.
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 · 113 lines · 20 tokens per session scan A e9b0482c67f2
create-linear-pr is a command published in the GitHub repository nodnarbnitram/claude-code-extensions (16 stars, last pushed 6mo ago), licensed MIT. It adds 20 tokens to every session and 912 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 commands, from other repositories
gsd:quick
Execute a quick task with GSD guarantees (atomic commits, state tracking) but skip optional agents.
standup
Review my git commits from the past workday and generate a standup summary.
gsd:remove-phase
Remove a future phase from roadmap and renumber subsequent phases.
company-repo
Gestionar el repositorio Company Savia: crear, conectar, estado, sincronizar. El repositorio compartido de la empresa para conocimiento, mensajería y estado.
weekly-summary
Generate weekly work summary from git activity.
afp
Prioritise feature - assigns ID, moves to backlog (shortcut for feature-prioritise).