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/n8n-io/n8n/linear-issue-triagergit clone --depth 1 https://github.com/n8n-io/n8nWhat 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.00047 | $0.01374 |
| Opus 5 | $0.00023 | $0.00687 |
| Sonnet 5 | $0.00009 | $0.00275 |
| Haiku 4.5 | $0.00005 | $0.00137 |
Grade A, and why
linear-issue-triager 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 yesterday.
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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- yesterday First seen · 125 lines · 47 tokens per session scan A 4c0ddb912e26
linear-issue-triager is an agent published in the GitHub repository n8n-io/n8n (202,853 stars, last pushed 2d ago), with no licence file. It adds 47 tokens to every session and 1,374 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-30.
Other agents, from other repositories
component-wrappers
How to build a ByteChef design-system component as a thin wrapper around a shadcn/ui primitive. Reference exemplars, already merged, live at.
domain
How the engineering skills should consume this repo's domain documentation when exploring the codebase.
issue-tracker
Issues and PRDs for this repo live as GitHub issues on bytechefhq/bytechef. Use the gh CLI for all operations, and always pass --repo bytechefhq/bytechef — this clone has multiple GitHub remotes (origin → your fork ivicac/bytechef, upstream → bytechefhq/bytechef), so relying on gh's auto-detection can file issues…
triage-labels
The skills speak in terms of five canonical triage roles. This file maps those roles to the actual label strings used in this repo's issue tracker (bytechefhq/bytechef).
n8n-skills
Install n8n-io/skills and let your agent use them safely — the MCP guard keeps Code-node source in the repo.
offline-loop
Several verbs are fully offline — no credentials, no network, no live n8n — which makes them safe for agents to run without supervision.