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 rem-musegit 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/rem-muse)<a href="https://agentmods.dev/skills/openonion/connectonion/rem-muse"><img src="https://agentmods.dev/badge/skills/openonion/connectonion/rem-muse/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/rem-muse"><img src="https://agentmods.dev/badge/skills/openonion/connectonion/rem-muse.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.00039 | $0.02162 |
| Opus 5.5 | $0.00016 | $0.00865 |
| Sonnet 5.5 | $0.00008 | $0.00432 |
| Haiku 4.5 | $0.00004 | $0.00216 |
Grade A, and why
rem-muse 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 today.
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 — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Muse on one page
Input: a written page, its cited originals, the open leads from enrich, the
questions earlier runs left, and the pages it links to.
Follow the page kind's rem-page-* rules and rem-investigate's quote and
evidence rules unchanged. Contact details keep the label enrich gave them; a
number the subject publishes on their own site stays theirs, [personal],
even when a company page lists it too.
Muse is thinking, not searching. Everything you need is already in the originals; what is missing is the right question. Asking a precise question matters more than answering it. Go slowly. One sharp insight is worth more than ten new facts.
Muse runs as one conversation. Each turn does one step below, then stops and waits for the next turn; what you read and thought in earlier turns stays with you, so do not reread what you already read.
Turn 1 — ask, then choose
Read the page, then every cited original whole. Do not edit the page.
Write at least twenty questions this material raises. A good question:
- is specific: names the person, the date, the number, the source ("Why did replies stop after the 2026-08-20 price change [6]?"), not "what is the relationship like?";
- is answerable from originals, or says exactly what record would answer it;
- matters to the user: its answer would change what the user does next, what they believe about this person or project, or how they deal with them.
Ask from several angles:
- Stakes: what does the user want from this, and they from the user? What is lost if nothing happens?
- Change: what is different now from the first contact? When did it turn, and what happened just before?
- Pattern: what keeps recurring — who chases, who delays, what topics, what conditions? Is it really a pattern (three or more cases) or one incident?
- Contradiction: where do two sources, or the page and a source, disagree? What did someone say and then not do?
- Silence: what was asked and never answered? What should have happened by now and did not?
- Connection: who else is in these threads, which project or organisation is this really about, which other page holds the other half?
- Why: why did the user decide what they decided; what principle shows?
- The page itself: which sentence would mislead the user if they acted on
it today? Which open thread is actually closed? Is another page the same
person or project (same name, an address or handle that the material ties to
them)? Is each current
Insightbullet, and the lead, still true and still the most important thing — or left over from an earlier, thinner page?
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.
- today First seen · 170 lines · 39 tokens per session scan A cb569d93f84b
rem-muse is a skill published in the GitHub repository openonion/connectonion (1,497 stars, last pushed today), licensed Apache-2.0. It adds 39 tokens to every session and 2,162 once invoked, about $0.0002 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-17.
Other skills, from other repositories
agentscope-java
Expert Java developer skill for AgentScope Java framework - a reactive, message-driven multi-agent system built on Project Reactor. Use when working with reactive programming, LLM integration, agent orchestration, multi-agent systems, or when the user mentions AgentScope, ReActAgent, Mono/Flux, Project Reactor, or…
apply-patch
Apply multi-file or tricky edits atomically with git apply instead of many fragile editfile calls. Use when changing several files at once or when editfile fails to match.
git-checkpoint
Use git as a safety net - create a checkpoint commit before risky or large changes and roll back cleanly if a change makes things worse. Use before multi-file refactors.
pptagent
Create and revise editable PowerPoint presentations from a brief using HTML slide sources, rendering, and visual review. Use when the requested deliverable is a PPTX deck. The host authors the slides; text-only hosts can use an external visual reviewer.
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…
a2ui
Make a reply easier to read and act on with rich blocks inside ordinary Markdown — a choice the user picks from, a form that collects several answers, a procedure as steps with warnings in place, a callout, a Mermaid diagram, a weather card, a live clock or countdown, and a dashboard of gauges for a system snapshot, a…