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 skills/openonion/connectonion/commitnpx skills add openonion/connectonion --skill commitgit clone --depth 1 https://github.com/openonion/connectonionWhat 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.00026 | $0.00341 |
| Opus 5 | $0.00013 | $0.00170 |
| Sonnet 5 | $0.00005 | $0.00068 |
| Haiku 4.5 | $0.00003 | $0.00034 |
Grade A, and why
commit 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.
What it actually says
Git Commit Skill
Create a well-formatted git commit for staged changes.
Instructions
-
Gather information (run in parallel):
git status- See what's staged and unstagedgit diff --staged- See exactly what will be committedgit log --oneline -5- See recent commit message style
-
Analyze changes:
- What was changed? (files, functions, features)
- Why was it changed? (bug fix, new feature, refactor)
- Follow the repository's commit message style
-
Draft commit message:
- First line: concise summary under 50 chars
- Focus on "why" not "what"
- Match existing commit style
-
Execute commit:
- Stage relevant files if needed:
git add <files> - Commit with a normal non-interactive
git commit -mcommand - Verify with
git status
- Stage relevant files if needed:
The skill supplies procedure, not permission. Git writes and commits must pass the agent's normal approval policy.
Safety Rules
- Do NOT commit .env or credential files
- Do NOT use
--amendunless explicitly asked - Do NOT push unless explicitly asked
- If commit fails, create a NEW commit (don't amend)
Example
git status
git diff --staged
git commit -m "Fix authentication timeout"
git status
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 · 50 lines · 26 tokens per session scan A 751b6f47c6b0
commit is a skill published in the GitHub repository openonion/connectonion (1,480 stars, last pushed 2d ago), licensed Apache-2.0. It adds 26 tokens to every session and 341 once invoked, about $0.0001 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 skills, from other repositories
a2ui-renderer
Render A2UI (Agent-to-UI declarative surfaces) in CopilotKit v2. Enable the runtime via CopilotRuntime({ a2ui: {...} }), then enable the provider via . Auto-activates via /info — do NOT manually pass renderActivityMessages. createA2UIMessageRenderer ships from @copilotkit/react-core/v2; low-level primitives…
copilotkit-develop
Use when building AI-powered features with CopilotKit v2 -- adding chat interfaces, registering frontend tools, sharing application context with agents, handling agent interrupts, and working with the CopilotKit runtime.
copilotkit-upgrade
Use when migrating a CopilotKit v1 application to v2 -- updating package imports, replacing deprecated hooks and components, switching from GraphQL runtime to AG-UI protocol runtime, and resolving breaking API changes.
artifact-deploy
One-click deploy a user's pre-built app/artifact into their OWN AWS account and get a global public HTTPS link (Vercel-like), with a default TTL and promote-to-persistent. Use when the user says "deploy this", "ship this demo", "give me a public link", "share this externally", or "deploy to AWS".
peekaboo
Capture and automate macOS UI with the Peekaboo CLI.
web-verify
Look at your OWN front-end change before claiming it works -- navigate the loopback URL of a dev server or pod you started, screenshot the surface you changed, read the image to judge it, and embed it in chat. Three capture backends: playwright-cli (the session the dashboard Browser panel shows), the agent-browser CLI…