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 commands/elnora-ai/elnora-linear/linear-bulkgit clone --depth 1 https://github.com/Elnora-AI/elnora-linearWrote 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/elnora-ai/elnora-linear/linear-bulk)<a href="https://agentmods.dev/commands/elnora-ai/elnora-linear/linear-bulk"><img src="https://agentmods.dev/badge/commands/elnora-ai/elnora-linear/linear-bulk.svg" alt="Measured on agentmods" 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 | $0.00020 | $0.00418 |
| Opus 5 | $0.00010 | $0.00209 |
| Sonnet 5 | $0.00004 | $0.00084 |
| Haiku 4.5 | $0.00002 | $0.00042 |
Grade A, and why
linear-bulk 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 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.
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.
What it actually says
Linear Bulk Update
Apply one change to every Linear issue matching a filter. Default is dry-run — the plan is shown but nothing mutates until the user confirms with --yes.
Workflow
-
Parse the user's request into filter + mutation pieces. Example: "move all ENG team Todos with the 'security' label to In Progress" → filter
--team ENG --state Todo+ mutation--set-state "In Progress". -
Run the dry-run first — always:
elnora-linear bulk \ --team <key> [--state <name>] [--assignee <name>] [--query <text>] \ [--set-state <name>] [--add-comment "<text>"] \ --output textThis prints what would change without touching anything.
-
Show the user the plan. Use
AskUserQuestionto confirm. Options:- "Apply all" → re-run with
--yes - "Cancel" → stop
- "Adjust filter" → tweak and re-dry-run
- "Apply all" → re-run with
-
Apply with
--yesonly after explicit confirmation.
Safety
bulkREQUIRES at least one of--set-stateor--add-comment— the command itself errors otherwise- Issues already in the target state are skipped (with a
SKIPPEDreason in the plan) - The default
--limitis 100; raise it explicitly if the user wants to touch more
Don't
- Don't add
--yesto the first invocation. Always dry-run first - Don't auto-confirm. The user clicks Approve
- Don't combine filters the user didn't ask for
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 · 43 lines · 20 tokens per session scan A de04eda25263
linear-bulk is a command published in the GitHub repository Elnora-AI/elnora-linear (7 stars, last pushed 5d ago), licensed Apache-2.0. It adds 20 tokens to every session and 418 once invoked, about $0.0001 per session on Opus 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 commands, from other repositories
beads-onboard
Run the interactive beads-onboard interview in the current project to generate beads conventions (AGENTS.md translation matrix, labels.md, reference.md, starter formula, pre-seeded bd remember entries).
feature
Ciclo completo de desarrollo: producto, arquitectura, desarrollo, QA, docs, entrega.
sync-github
Ejecuta SonIA Sync: refleja el tablero local en GitHub Issues usando gh CLI.
status
The state of play, computed fresh: branch, dirty files, the active sprint, open work, index freshness.
v-orchestrate
Materialize a Compound V execution manifest from a plan (or an accepted fast-path pre-eval). Applies the routing policy and writes manifest.yaml plus an initial state.json into docs/superpowers/execution/ / — without dispatching. Binds every pre-eval-backed run. Use this to inspect or edit the manifest before…
specmanager-build
Build one phase of a SpecManager feature's plan via the builder subagent. Stops at the phase boundary; never advances.