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-cleanupgit 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-cleanup)<a href="https://agentmods.dev/commands/elnora-ai/elnora-linear/linear-cleanup"><img src="https://agentmods.dev/badge/commands/elnora-ai/elnora-linear/linear-cleanup.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.00030 | $0.00850 |
| Opus 5 | $0.00015 | $0.00425 |
| Sonnet 5 | $0.00006 | $0.00170 |
| Haiku 4.5 | $0.00003 | $0.00085 |
Grade A, and why
linear-cleanup 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 4d 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Linear cleanup
Audit Linear issues in {{scope}} and propose fixes. Walks six checks, summarizes findings, and asks per-category before any mutation. All elnora-linear mutations default to dry-run — explicit --yes is required to commit.
The six checks
1. Missing required labels
elnora-linear issues list --team "<scope>" --limit 100 --output json \
| jq '.[] | select((.labels // []) | map(.name) | any(startswith("Type:")) | not)'
For each issue missing the team's required label prefixes (see references/label-policy.json or elnora-linear teams get <key>), suggest labels from title/description keywords. Repeat the startswith check for every required prefix on the team (Layer:, Source:, etc.).
2. Stale issues (no activity 30+ days)
elnora-linear cleanup --team "<scope>" --inactive-days 30 --action comment --output text
Dry-run by default. Offer: comment / close / cancel / skip. Apply chosen action with --yes.
3. Potential duplicates
elnora-linear issues list --team "<scope>" --limit 200 --output json
For each pair of issues with >70% title similarity, surface them as candidates. Suggest elnora-linear relations create --type duplicate-of or merge.
4. Wrong state
elnora-linear projects list --team "<scope>" --output json
elnora-linear issues list --team "<scope>" --limit 200 --output json
Cross-check each issue's state against its project's status (a Completed project shouldn't have In Progress issues; a Backlog project shouldn't have In Progress issues). Flag mismatches.
5. Orphaned issues (no project)
elnora-linear issues list --team "<scope>" --limit 200 --output json \
| jq '.[] | select(.project == null)'
For each orphan, suggest the most likely project based on title/description vs elnora-linear projects list --output json.
6. Unactionable issues
elnora-linear issues list --team "<scope>" --limit 200 --output json
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.
- 4d ago First seen · 81 lines · 30 tokens per session scan A b99362b7023d
linear-cleanup is a command published in the GitHub repository Elnora-AI/elnora-linear (7 stars, last pushed 3d ago), licensed Apache-2.0. It adds 30 tokens to every session and 850 once invoked, about $0.0002 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).
octo-plan
Intelligent plan builder - creates strategic execution plans (doesn't execute). Use /octo:embrace to execute plans.
octo-schedule
Manage scheduled workflow jobs for the Claude Octopus scheduler.
octo-scheduler
Manage the Claude Octopus scheduled workflow runner daemon.
discover
Run a full product discovery cycle — from outcome definition through opportunity mapping, prioritisation, and experiment design. Use when the team isn't sure what to build next, or before writing a PRD for a complex feature space.
whats-next
Show current project status and suggest next steps.