ConnectOnion is an open-source, template-first toolkit for building, debugging, deploying, and operating AI agents. Developers use its command-line tools and Python runtime to create agents, add tools, connect services, deploy them, and make them callable by other agents, while the catalogue entries are related agents, skills, and instructions.
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 skills add openonion/connectonion --skill co-lineargit clone --depth 1 https://github.com/openonion/connectonionWrote 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/skills/openonion/connectonion/co-linear)<a href="https://agentmods.dev/skills/openonion/connectonion/co-linear"><img src="https://agentmods.dev/badge/skills/openonion/connectonion/co-linear/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/openonion/connectonion/co-linear"><img src="https://agentmods.dev/badge/skills/openonion/connectonion/co-linear.svg" alt="Reviewed on agentmods" width="80" 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.00069 | $0.00749 |
| Opus 5.5 | $0.00028 | $0.00300 |
| Sonnet 5.5 | $0.00014 | $0.00150 |
| Haiku 4.5 | $0.00007 | $0.00075 |
Grade A, and why
co-linear 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 15d 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
co linear
co linear acts in the user's Linear workspace as the user, with their
personal API key. Syntax lives in help, not here: run co linear --help, then
co linear <command> --help before the first use of a command.
Read the output, not just the exit code. Every failure exits 1 and ends
with one Next: line; run that line, it is the fix. A write without --yes
exits 0 after only a preview: nothing changed until you rerun it with --yes.
Before anything
Run co linear check. If it says the key is missing, tell the user to create
one in Linear (Settings → Security & access → Personal API keys) and run the
co env set LINEAR_API_KEY ... command it prints. Never ask them to paste the
key into the chat.
My open issues (standup)
co linear issues --mine— open issues only, most recently updated first.- For anything the user asks about,
co linear issue <id from that list>. - Report from what the commands printed: id, title, state. Do not guess a
status that is not in the output; done work needs
--state Done.
File a bug from a report
- Find the team:
co linear teams. If the user did not say which, ask. - Search first so you do not file a duplicate:
co linear search "<key words>". If a match exists, show it and ask whether to comment on it instead. - Write a title that names the symptom, and a description with steps,
expected and actual behaviour, and where the report came from. Pass a long
description on stdin with
--description -. - Labels must exist:
co linear labels --team <key>. Do not invent one. - Run
co linear create ...without--yes, read the preview, then rerun the printed command with--yeswhen the user asked you to file it. - Answer with the id from
Created <id>and its link.
Close with a comment
co linear issue <id>— confirm it is the issue the user means.co linear comment <id> "<what was done, with the PR or commit>" --yes.co linear states --team <team key from the issue>— pick the completed state by its type (completed), not by guessing the word "Done".co linear update <id> --state "<that name>" --yes.- Verify with
co linear issue <id>: the state line must show it.
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.
- 15d ago First seen · 59 lines · 69 tokens per session scan A e053a6b16236
co-linear is a skill published in the GitHub repository openonion/connectonion (1,497 stars, last pushed today), licensed Apache-2.0. It adds 69 tokens to every session and 749 once invoked, about $0.0003 per session on Opus 5.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-10-02.
Other skills, from other repositories
company-employee
The protocol every employee of a PenguinHarness organization follows — read the handbook first, act on [orgtrigger] work runs, schedule tickets from the desk session and do the work in ticket sessions, block instead of idling, ask the board in the all-hands channel before anything heavy, costly, irreversible or…
company-ceo
Run a PenguinHarness organization as its CEO — turn the mission into a ticket tree, hire HR and finance first, partition the shared workspace, schedule the calendar, open a channel per stream, review tickets and report to the board in the all-hands channel.
company-hr
Run HR for a PenguinHarness organization — guarantee every employee has an enabled calendar event, hire and offboard employees (channels included), evaluate and improve them (with the default-rsi-toolkit plugin's agent-optimization skill), and keep the handbook's role conventions current.
company-mirror
Run a PenguinHarness organization that mirrors a real company — one digital twin per real colleague, each twin's desk bound to that colleague's chat bot, twins answering what the handbook already knows and relaying the rest to one another instead of hiring, scheduling and filing tickets.
company-setup
Create a company-mode organization together with the user — collect its id, name, mission, shared workspace, model and CEO budget one question at a time, confirm the whole thing in one summary, then run penguin org create and hand the user over to company mode.
agentlas-operations
A set of operating procedures for running Agentlas, a system for coordinating agents, reusable workforces, automation graphs, and shared agent resources. It covers candidate selection, graph creation, asset discovery, and memory rules.