TL;DR
OpenSquilla cuts agent LLM costs from $6 to $0.68 with almost no quality loss. The core trick: a local small model acts as a judge—simple tasks go to cheap models, only complex tasks hit top-tier models.
---
Key Numbers 📊
| Dimension | Value | |------|------| | License | Apache 2.0 | | Current version | 0.3.1 | | GitHub Stars | ~2000+ | | Supported models | 20+ providers | | Cost reduction | ~90% | | Routing decision latency | Zero token cost (runs locally) |
---
SquillaRouter: The Local Judge
A LightGBM + ONNX classifier takes input length, language, code, keywords, and semantic embeddings, and outputs a T0–T3 difficulty rating.
Key point: the judge runs entirely locally—prompts never leave your machine to ask a big model whether the task is hard.
Benchmark: across 25 tasks, pure Claude Opus 4.7 scored 0.9255 at $6.20; OpenSquilla's mixed routing scored 0.9251 at $0.68.
A 0.0004 score difference, 89% cost savings. The math speaks for itself.
---
Four-Layer Memory: The Agent's Long-Term Experience
- Working memory: current conversation context
- Short-term memory: recent summaries
- Long-term memory: Markdown notes
- Archive memory: SQLite full-text search + semantic recall
- Complex skills get skipped by the AI
- Errors differ every time; sometimes results are fabricated
- Rules are clearly written but not followed in order
- Mixed workloads of high-frequency simple + low-frequency complex tasks (support agents: 80% FAQ + 20% technical)
- Budget-sensitive production environments (need Opus-level capability but can't afford full-rate calls)
- Multi-platform deployment (one agent serving Web, Slack, Discord, Feishu/Lark, etc.)
- Local-first security requirements (routing decisions and embeddings stay fully local, no data leaves the machine)
Context is automatically compressed when full and persisted across sessions. Incremental transmission avoids resending history, cutting repeated tokens by 90%.
---
MetaSkill: Fixing Unruly Agents
Anyone building agents knows these failures:
MetaSkill applies meta-level control over skills, guaranteeing execution order and completeness. It addresses both "won't run" and "won't behave" problems.
---
Three-Tier Security Sandbox
| Tier | Linux | macOS | Windows | |------|-------|-------|---------| | Standard | ✅ | ✅ | ✅ | | Strict | ✅ | rendering only | ❌ | | Locked | ✅ | not yet | ❌ |
Linux has full isolation via Bubblewrap; macOS/Windows support is still catching up.
---
Limitations ⚠️
1. Routing model depends on training data—entirely new task types may be misclassified 2. The 6→0.68 result is scenario-specific—gains shrink on all-complex workloads 3. Ecosystem maturity lags OpenClaw—fast-growing stars but few case studies 4. Windows/macOS sandboxing incomplete
---
Who Should Use It
Key Takeaways
1. Core value: local intelligent routing cuts cost to 1/9 with equivalent quality 2. Technical highlights: zero-token LightGBM routing, four-layer memory, MetaSkill execution enforcement 3. Best fit: scenarios where simple tasks make up 60%+ of traffic 4. Risks: cost figures based on a specific scenario; young ecosystem; cross-platform sandboxing incomplete
---
Sources: official GitHub repository, official docs, third-party reviews (CSDN/xmsumi.com) Research date: 2026-06-05