Fleet Kit
Modular Python toolkit extracted from the SuperInstance fleet workspace. Import what you need — one tool, one function, no heavy framework.
from fleet_kit.plato import PlatoClient
from fleet_kit.consensus import check_consensus
from fleet_kit.models import ask
Install
pip install fleet-kit
Or clone and install locally:
git clone https://github.com/SuperInstance/fleet-kit.git
cd fleet-kit
pip install -e .
Tools
| Module | Export | What it does |
|---|---|---|
plato |
PlatoClient |
HMAC-signed read/write to PLATO room server (:8847) |
services |
TileGate, RoomManager, run_server |
PLATO room server, tile decomposition, quality gates |
consensus |
HolonomyMatrix, check_consensus |
Zero-holonomy consensus, tile cardinality tracking |
models |
FleetModelClient, ModelRouter |
Route LLM calls to z.ai / DeepSeek / Seed |
matrix |
MatrixClient |
Fleet Matrix bridge — rooms, whispers, sync |
crab |
Crab, Crabs |
Agent shell — register, heartbeat, skill injection |
construct |
build_agent, deploy_pipeline |
Agent lifecycle — build, tag, deploy, teardown |
plugins |
scan_manifests, PluginRuntime |
Plugin system — discover, load, run plugins |
keeper |
KeeperClient |
Agent registry — register, discover, status |
audits |
RepoAuditor |
Zero-shot repo audit — clone, analyze, score, file to PLATO |
badges |
inject_badge, scan_missing_badges |
CI badge manager — add badges to repo READMEs |
indexer |
generate_index |
Fleet INDEX.md generator — catalog services, dependencies |
utils |
load_key, sign_data |
Shared helpers — credential vault, HMAC, JSON ops |
Architecture
fleet_kit/
├── __init__.py # Unified export of all symbols
├── plato.py # PLATO client — read, write, submit tiles
├── services.py # PLATO server — run, manage rooms
├── consensus.py # Zero-holonomy + Pythagorean48
├── models.py # LLM routing — 3 tiers
├── matrix.py # Matrix bridge — fleet comms
├── crab.py # Agent shell — agent lifecycle
├── construct.py # Agent construction pipeline
├── plugins.py # Plugin runtime
├── keeper.py # Keeper client — fleet registry
├── audits.py # Repo audit tools
├── badges.py # CI badge injection
├── indexer.py # Infrastructure INDEX.md generator
└── utils.py # Shared utilities
Adding a New Tool
- Create
fleet_kit/your_tool.pywith a single class or function - Add the export to
fleet_kit/__init__.py - Write tests in
tests/test_your_tool.py - Open a PR
Tools should be:
- Zero external deps — stdlib only where possible
- Self-documenting — each public symbol has a docstring
- Tested — at minimum a smoke test and a unit test
License
MIT — SuperInstance Contributors
Metadata
Release files for fleet-kit 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| fleet_kit-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for fleet_kit-0.1.0-py3-none-any.whl |
Release files / fleet_kit-0.1.0-py3-none-any.whl
| Download URL | fleet_kit-0.1.0-py3-none-any.whl |
|---|---|
| Size | 30.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
01f449703ebc8250e33dc0838f355ce911c8847e2a04cb02c433c4a0aaa624d2
|
|
BLAKE2b-256 checksum How to use checksums |
b3ac713591e4a4cf7443b64076928dbf5cf92c4975994dbf8d871ffcc2b0d888
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.10.12
|
Security for fleet-kit 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.