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-my-issuesgit 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-my-issues)<a href="https://agentmods.dev/commands/elnora-ai/elnora-linear/linear-my-issues"><img src="https://agentmods.dev/badge/commands/elnora-ai/elnora-linear/linear-my-issues.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.00015 | $0.00168 |
| Opus 5 | $0.00008 | $0.00084 |
| Sonnet 5 | $0.00003 | $0.00034 |
| Haiku 4.5 | $0.00002 | $0.00017 |
Grade A, and why
linear-my-issues 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 5d 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
My Linear Issues
List every Linear issue currently assigned to the viewer.
Run
elnora-linear my-issues --limit 50 --output json
Present
Group by state in this order: In Progress, Todo, Backlog, Done (last 7 days only), Canceled (hide unless asked). Within each state, sort by updatedAt descending. Show identifier, title, team, project.
If the list is empty, say so cleanly: "Nothing assigned." Don't fabricate.
Don't
- Don't include closed/cancelled issues older than 7 days — the user wants their active load
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.
- 5d ago First seen · 26 lines · 15 tokens per session scan A 9ac72132de52
linear-my-issues is a command published in the GitHub repository Elnora-AI/elnora-linear (7 stars, last pushed 3d ago), licensed Apache-2.0. It adds 15 tokens to every session and 168 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
update-docs
Review and update all project documentation to reflect the current codebase.
update-linear-schema
Update the Linear GraphQL schema and fix any resulting breakage.
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).
init
Install the formatters this repository needs, with every command visible before it runs.
brand-generate
Generate an on-brand document from a saved Brand Profile.
genshijin-compress
Markdown・テキストファイルを原始人形式へ安全圧縮.