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-investigate-orggit 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-investigate-org)<a href="https://agentmods.dev/skills/openonion/connectonion/rem-investigate-org"><img src="https://agentmods.dev/badge/skills/openonion/connectonion/rem-investigate-org/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-investigate-org"><img src="https://agentmods.dev/badge/skills/openonion/connectonion/rem-investigate-org.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.00027 | $0.00449 |
| Opus 5.5 | $0.00011 | $0.00180 |
| Sonnet 5.5 | $0.00005 | $0.00090 |
| Haiku 4.5 | $0.00003 | $0.00045 |
Grade A, and why
rem-investigate-org 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 — 37 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Investigating an organisation
- Project documents that name the subject are the owner's record: cite them as such; a contact detail only from them is not the person's own.
- The material includes mail on this page's domains and, when another domain page shares a canonical contact candidate, their dated primary correspondence. A shared page or display name is a lead, not identity proof. Verify the person and company from the messages before drawing cross-domain conclusions; keep uncertain address/domain ownership explicit. Do not merge legal entities. Existing notebook pages are context, not independent evidence.
- Read the material for what is agreed with the entity: terms, dates, signed or unsigned documents, who decides. What is true of one person belongs on that person's page.
People herelinks existing people pages; never copy their contents. A person who writes from the domain but has no page: name them, do not create a page.Termsholds the numbers (rates, dates, notice periods) with the mail or attachment that states them; search attachments for them first.- Compare offers and replies by date and exact terms. An accepted credits/tier offer does not establish acceptance of a distinct free-month offer, provisioning or completed setup. A later request on another topic does not close a thread.
- Lead
Our relationshipwith the current supported result and next uncertainty, before the introductory history. Preserve ambiguous scheduling language; do not infer a broken link or who supplied it. A shared subject is not a verified thread. - A vendor that only ever sends, or the user's own domain, is not a relationship;
say so in
Uncertaintiesrather than fillingOur relationship.
What to produce
Follow rem-page-org exactly, every section present, in order.
- Keep Facts dates scoped to confirmed target-domain correspondence when cross-domain identity remains unverified. Put candidate-domain dates in explicitly qualified related context instead.
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 Changed · +2 lines 4e9ae359e86e
- 5d ago Changed · -2 lines 7d919eb4a907
- 13d ago Changed · +14 lines bbb4542e3047
- 15d ago First seen · 23 lines · 27 tokens per session scan A 1f7f14ff0fd9
rem-investigate-org is a skill published in the GitHub repository openonion/connectonion (1,497 stars, last pushed today), licensed Apache-2.0. It adds 27 tokens to every session and 449 once invoked, about $0.0001 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-01.
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.
fda-database
Query openFDA API for drugs, devices, adverse events, recalls, regulatory submissions (510k, PMA), substance identification (UNII), for FDA regulatory data analysis and safety research.
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…