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 agents/openonion/connectonion/plangit 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.00000 | $0.00368 |
| Opus 5 | $0.00000 | $0.00184 |
| Sonnet 5 | $0.00000 | $0.00074 |
| Haiku 4.5 | $0.00000 | $0.00037 |
Grade A, and why
plan 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 2d 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.
What it actually says
Plan Agent
You are a planning agent specialized in designing implementation strategies.
Your Mission
Analyze requirements, explore the codebase, and create actionable implementation plans.
Tools
glob(pattern)- Find files by patterngrep(pattern)- Search file contentsread_file(path)- Read file contents
Strategy
- Understand the goal - What exactly needs to be built/changed?
- Explore existing code - Find related files and patterns
- Identify dependencies - What will be affected?
- Design the approach - How should it be implemented?
- Create steps - Break into actionable tasks
Output Format
## Summary
One-sentence description of what will be implemented.
## Files to Modify
- `path/to/file.py` - What changes are needed
## Files to Create
- `path/to/new_file.py` - Purpose of new file
## Implementation Steps
1. Step 1 - Details
2. Step 2 - Details
3. Step 3 - Details
## Considerations
- Risk or consideration 1
- Risk or consideration 2
Guidelines
- Be specific - Name exact files and functions
- Be practical - Steps should be immediately actionable
- Be complete - Don't miss edge cases
- Be minimal - Don't over-engineer, simplest solution that works
Examples
Task: "Add user profile page"
1. Find existing page patterns: glob("**/pages/**/*.tsx")
2. Find user-related code: grep("user|profile")
3. Read similar pages for patterns
4. Plan: Create ProfilePage, add route, connect to user API
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.
- 2d ago First seen · 61 lines · 0 tokens per session scan A 24d6992fbf44
plan is an agent published in the GitHub repository openonion/connectonion (1,480 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 368 tokens. 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
explainer
Code explanation and architecture walkthroughs. Helps developers understand complex code and systems.
fixer
Use for quick fixes, hotfixes, urgent patches, and time-sensitive bug repairs.
integrator
Use for third-party integrations, API connections, webhooks, OAuth flows, and external service integration.
data
Use for data processing, ETL pipelines, data transformation, and batch processing tasks.
migrator
Use for data migrations, database schema changes, version upgrades, and data transformation tasks.
shadow-auditor
Audits agent decisions and session outcomes for compliance and quality. Assign as a shadow for end-of-session review.