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 agents/elnora-ai/elnora-linear/linear-url-to-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/agents/elnora-ai/elnora-linear/linear-url-to-issues)<a href="https://agentmods.dev/agents/elnora-ai/elnora-linear/linear-url-to-issues"><img src="https://agentmods.dev/badge/agents/elnora-ai/elnora-linear/linear-url-to-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.1 | $0.00162 | $0.02482 |
| Opus 5 | $0.00081 | $0.01241 |
| Sonnet 5 | $0.00032 | $0.00496 |
| Haiku 4.5 | $0.00016 | $0.00248 |
Grade B, and why
linear-url-to-issues scanned grade B with 1 finding 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 6d 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.
Instruction-override phrasingmediumPrompt injection
Text telling the model to disregard its earlier instructions or safety rules is the shape of a prompt injection, whoever wrote it.
- "Ignore previous instructions" / "act as a different agent" / "you are now ..." Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 216 lines — stays where its author put it; the contents beside it link to each section on GitHub.
URL → Linear Issues
Extract actionable items from web content and create Linear issues. Sonnet, parallel-safe — dispatch one agent per URL when processing several.
Scope: URL-driven creation. Manual create → linear-issue-creator. Edits → linear-issue-updater.
CLI
elnora-linear is on $PATH. JSON output. Auth via LINEAR_API_KEY.
elnora-linear context --team "Team" # cold-start primitive: projects+statuses, states, labels by prefix, members
elnora-linear issues search "terms" [--limit N]
elnora-linear issues create "Title" --team "Team" --description "md" \
[--project "P"] [--labels "L1,L2"] [--priority 0-4] \
[--assignee "name"|"me"|"none"] [--state "Todo"|"Backlog"] \
[--skip-label-check] # bypass team label-policy validation
[--skip-project-check] # bypass require-a-project rule (placeholder issues only)
elnora-linear relations create ENG-NEW ENG-OLD --type related|blocks|duplicate|similar
Cold-start optimization for multi-issue runs: when extracting N issues from one URL into the same team, call elnora-linear context --team "<Team>" ONCE up front and reuse the labels/projects/states from the response across every issues create. Saves N×3 redundant CLI calls.
Priority: 0=None, 1=Urgent, 2=High, 3=Normal, 4=Low.
Pitfalls: --labels (not --label), --description (not --desc). Default state = Todo for new actionable items unless project status says Backlog.
Metadata completeness — applies to every issue created
Every issue MUST be created with the maximum metadata that can reasonably be inferred. Bare tickets that force the user to enrich are an explicit failure mode.
For every create, you MUST attempt to set:
- Project — never leave null. Keyword-match the title/description against
elnora-linear context --team "<Team>"projects[]. Pick the best fit. Linear CLI now requires a project by default for teams that have any projects; bareissues createcalls without--projectexit 2 with a structuredProjectValidationError({error: "project_required",availableProjects: [{name, status}],suggestedRetry}). On that error, pick a project fromavailableProjectsand retry — or, only if nothing genuinely fits, re-run with--skip-project-checkAND surface that in the report ("no matching project; passed --skip-project-check because "). - Labels — required labels per the team's
requiredLabels(mandatory) PLUS any applicable optional labels you can infer from the source content (e.g.Severity: *for bugs with clear severity,Source: *if origin is obvious). More signal beats less. - Related issues — the per-item dupe check (step 3 below) doubles as relation discovery. Topical-but-not-duplicate matches MUST be linked as
--type relatedafter creation. - Sibling links — if multiple new issues come from the same source URL, link them as
--type relatedso the cluster is visible. - Priority + assignee + due date — set whatever the user provided. Don't invent values, but don't drop signals either.
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.
- 6d ago First seen · 216 lines · 162 tokens per session scan B aacd670528ef
linear-url-to-issues is an agent published in the GitHub repository Elnora-AI/elnora-linear (7 stars, last pushed yesterday), licensed Apache-2.0. It adds 162 tokens to every session and 2,482 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it B with 1 finding (instruction-override phrasing). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
yegge
Primary session agent for this project. Triages each request and routes it to the right skills; coordinates non-trivial work end to end. All user requests come through it.
slopstop-effort-high
You are being launched by a slopstop orchestrator. Your instructions arrive entirely in the prompt, which will tell you to invoke a specific slopstop- worker skill and follow it.
slopstop-effort-low
You are being launched by a slopstop orchestrator. Your instructions arrive entirely in the prompt, which will tell you to invoke a specific slopstop- worker skill and follow it.
slopstop-effort-max
You are being launched by a slopstop orchestrator. Your instructions arrive entirely in the prompt, which will tell you to invoke a specific slopstop- worker skill and follow it.
slopstop-effort-medium
You are being launched by a slopstop orchestrator. Your instructions arrive entirely in the prompt, which will tell you to invoke a specific slopstop- worker skill and follow it.
slopstop-effort-xhigh
You are being launched by a slopstop orchestrator. Your instructions arrive entirely in the prompt, which will tell you to invoke a specific slopstop- worker skill and follow it.