Check tool output, track usage, change routing, or shape context. Install a maintained plugin by name—no Git or Go needed—then review its permissions and enable it in your local control plane.
Use an operator-bound local model for contextual checks before new tool output—including failed commands—reaches the primary provider. Your harness can ask for value-free categories and line numbers from the latest protection.
These are the manifest’s requests, not automatic grants. Review resource bindings and the exact built digest in the control plane.
usage_logger
See usage without saving prompts
Write one content-free JSONL record for each completed response, then let your harness read best-effort token totals for its verified session without exposing prompts or log contents.
These are the manifest’s requests, not automatic grants. Review resource bindings and the exact built digest in the control plane.
pii_guard
Block recognizable sensitive values without a model
Use deterministic checks for recognizable PII and secret shapes. It needs no model or network destination, and your harness can ask why the latest tool result was protected without receiving the sensitive value.
These are the manifest’s requests, not automatic grants. Review resource bindings and the exact built digest in the control plane.
cache_warmer
Keep one conversation's cache warm for a bounded gap
Opt a conversation into periodic refresh requests, with a deadline and break-even budget. Useful only for explicit cache markers whose lifetime refreshes on a read.
These are the manifest’s requests, not automatic grants. Review resource bindings and the exact built digest in the control plane.
compactor
Summarize selected historical tool results
Use an operator-bound model for eligible older tool output, only when the estimated benefit clears the cache-rewrite and summarizer-cost gate. Your harness can inspect the active limits without triggering a model call.
These are the manifest’s requests, not automatic grants. Review resource bindings and the exact built digest in the control plane.
decision_router
Route harder requests with explicit control
Compare configured model candidates, suggest a switch you can confirm, or apply an approved automatic escalation policy while keeping routing decisions visible.
These are the manifest’s requests, not automatic grants. Review resource bindings and the exact built digest in the control plane.
intent
Carry the reason for a tool call
Ask the model to include why it is making a tool call, strip the added field before the harness sees the streamed call, and make captured intent available to a compactor.
These are the manifest’s requests, not automatic grants. Review resource bindings and the exact built digest in the control plane.
keyword_compactor
Trim repeatable tool output without another model
Apply explicit deterministic or keyword policies to selected tool results. Useful for long searches and listings that can be rerun, while keeping source reads exact.
These are the manifest’s requests, not automatic grants. Review resource bindings and the exact built digest in the control plane.
schema_translator
Adapt map-shaped tool schemas
Convert supported open-map tool parameters into key/value arrays for providers that need a constrained schema, then reverse the recorded conversion on streamed tool calls.
These are the manifest’s requests, not automatic grants. Review resource bindings and the exact built digest in the control plane.
tool_governor
Choose the tools your model sees
Restrict or replace model-visible tool definitions. Your harness can also request a reversible, user-confirmed allowance for a tool your allowlist omits; explicit denies always apply, and execution approval still belongs to the harness.
Agent tools via MCP — Inspect restriction counts or request a confirmed tool allowance for this session. Explicit operator denies still apply; undo stays user-controlled.
These are the manifest’s requests, not automatic grants. Review resource bindings and the exact built digest in the control plane.
Make it your own.
Your plugin can live in your own repository. Move a harness-specific extension into a reusable plugin, then share it for a catalogue listing. For permissions, version pinning and source builds, see the installation guide. Connect MCP to let your agent discover plugin tools.
Registry API and release verification
GET https://torana.sh/registry/v1/index.json
The registry lists plugin source, manifest declarations and independently published release digests. Torana downloads release bundles from GitHub and checks them against these digests. Installation never grants permissions. How bundle verification works →
Torana