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-syncgit clone --depth 1 https://github.com/Elnora-AI/elnora-linearWhat 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.00019 | $0.00307 |
| Opus 5 | $0.00010 | $0.00153 |
| Sonnet 5 | $0.00004 | $0.00061 |
| Haiku 4.5 | $0.00002 | $0.00031 |
Grade A, and why
linear-sync 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 2d 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 Sync
Refresh the reference files the rest of elnora-linear reads — teams, projects, users, workflow states. Run this on first install and any time your Linear workspace changes (new team, renamed project, etc.).
Run
The fast path: refresh everything auto-discoverable from the Linear API.
elnora-linear sync all
Pick one target:
elnora-linear sync teams
elnora-linear sync projects
elnora-linear sync users
elnora-linear sync workflows
Validate references:
elnora-linear sync verify
Reports each reference as user-file (populated) or placeholder (default, empty).
Import an existing config bundle:
elnora-linear sync import --from /path/to/bundle.json
Where it writes
In precedence order:
--references-dir <path>flagLINEAR_REFERENCES_DIRenv var~/.config/elnora-linear/(auto-created if needed)
Never writes to the bundled defaults in the installed package — those stay clean.
Don't
- Don't run
sync allrepeatedly in a loop — it issues N×teams API calls - Don't commit the populated reference files to a public repo — they're user-specific data
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.
- 2d ago First seen · 55 lines · 19 tokens per session scan A 8e16f053fabd
linear-sync is a command published in the GitHub repository Elnora-AI/elnora-linear (7 stars, last pushed 4d ago), licensed Apache-2.0. It adds 19 tokens to every session and 307 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.
trekker:task-agent
Autonomous agent that finds ready work and completes it.
trekker:history
View audit log of changes to understand what happened in past sessions.
trekker:list
List tasks with optional filters.
trekker:create
Create a new task interactively.