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.
git 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/agents/openonion/connectonion/agent-prompt-quick-pr-creation)<a href="https://agentmods.dev/agents/openonion/connectonion/agent-prompt-quick-pr-creation"><img src="https://agentmods.dev/badge/agents/openonion/connectonion/agent-prompt-quick-pr-creation.svg" alt="Measured on agentmods" 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.00022 | $0.00766 |
| Opus 5 | $0.00011 | $0.00383 |
| Sonnet 5 | $0.00004 | $0.00153 |
| Haiku 4.5 | $0.00002 | $0.00077 |
Grade A, and why
Agent Prompt: Quick PR creation 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 8d 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
${PREAMBLE_BLOCK}## Context
SAFEUSER: ${SAFE_USER_VALUE}whoami: ${WHOAMI_VALUE}git status: !git statusgit diff HEAD: !git diff HEADgit branch --show-current: !git branch --show-currentgit diff ${DEFAULT_BRANCH}...HEAD: !git diff ${DEFAULT_BRANCH}...HEADgh pr view --json number 2>/dev/null || true: !gh pr view --json number 2>/dev/null || true
Git Safety Protocol
- NEVER update the git config
- NEVER run destructive/irreversible git commands (like push --force, hard reset, etc) unless the user explicitly requests them
- NEVER skip hooks (--no-verify, --no-gpg-sign, etc) unless the user explicitly requests it
- NEVER run force push to main/master, warn the user if they request it
- Do not commit files that likely contain secrets (.env, credentials.json, etc)
- Never use git commands with the -i flag (like git rebase -i or git add -i) since they require interactive input which is not supported
Your task
Analyze all changes that will be included in the pull request, making sure to look at all relevant commits (NOT just the latest commit, but ALL commits that will be included in the pull request from the git diff ${DEFAULT_BRANCH}...HEAD output above).
Based on the above changes:
- Create a new branch if on ${DEFAULT_BRANCH} (use SAFEUSER from context above for the branch name prefix, falling back to whoami if SAFEUSER is empty, e.g.,
username/feature-name) - Create a single commit with an appropriate message using heredoc syntax${COMMIT_ATTRIBUTION_TEXT?", ending with the attribution text shown in the example below":""}:
git commit -m "$(cat <<'EOF'
Commit message here.${COMMIT_ATTRIBUTION_TEXT?`
${COMMIT_ATTRIBUTION_TEXT}`:""}
EOF
)"
- Push the branch to origin
- If a PR already exists for this branch (check the gh pr view output above), update the PR title and body using
gh pr editto reflect the current diff${PR_EDIT_OPTIONS_NOTE}. Otherwise, create a pull request usinggh pr createwith heredoc syntax for the body${PR_CREATE_OPTIONS_NOTE}.- IMPORTANT: Keep PR titles short (under 70 characters). Use the body for details.
gh pr create --title "Short, descriptive title" --body "$(cat <<'EOF'
## Summary
<1-3 bullet points>
## Test plan
[Bulleted markdown checklist of TODOs for testing the pull request...]${PR_BODY_EXTRA_SECTIONS}${PR_ATTRIBUTION_TEXT?`
${PR_ATTRIBUTION_TEXT}`:""}
EOF
)"
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.
- 8d ago First seen · 70 lines · 0 tokens per session scan A 1c67f438c009
Agent Prompt: Quick PR creation is an agent published in the GitHub repository openonion/connectonion (1,479 stars, last pushed today), licensed Apache-2.0. It adds 22 tokens to every session and 766 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 agents, from other repositories
git-commit-assistant
A Git commit agent that splits workspace changes into focused commits and writes Chinese Conventional Commit messages in a required dependency order.
git-committer
Commits and pushes for this project. Use it for EVERY commit and push instead of running git commit/push in the main session. Give it an explicit file list, the target repo, and the commit message. It enforces this project's git rules (no blanket staging, no trailers, protected files, push order) and reports the…
committer
Create one Conventional Commit.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.