extension-utilities is a companion repository of optional modules that can be merged into a composed Summoner SDK. Each module is self-contained, exposing a small public interface that can be added (or omitted) without changing the core runtime.
The intended workflow is:
- choose the utility modules you want (for example
visionary,curl_tools,gpt_guardrails) - add them to your SDK composition list (via
build.txt) - import them from the composed SDK like normal Python modules (for example
from summoner.visionary import ...)
These utilities are protocol-level in the sense that they help you operate agents through visualization, parsing, and budgeting support. They do not change the agent execution model or networking semantics implemented in summoner-core.
The extension-utilities repository follows the extension-template layout, which implies that each utility lives under tooling/<module>/.
During local development, import from tooling.*:
from tooling.visionary import ClientFlowVisualizerDuring SDK composition, the builder copies tooling/<module>/ into summoner/<module>/ and rewrites imports of the form from tooling.<module> ... into the public namespace:
from summoner.visionary import ClientFlowVisualizerNote
In the repository, the script install.sh setup boots a dev environment and installs summoner-core. It does not compose a new SDK.
Composition happens in an SDK project via build.txt.
For projects built using the summoner-sdk template, you can include a module by adding it to build.txt. Each entry specifies the extension repository and the module name to merge during SDK composition.
Minimal pattern:
https://github.com/Summoner-Network/extension-utilities.git:
<module_name>
Example:
https://github.com/Summoner-Network/extension-utilities.git:
visionary
curl_tools
gpt_guardrails
After composition, you import from the summoner.* namespace:
from summoner.curl_tools import CurlToolCompiler
from summoner.gpt_guardrails import count_chat_tokens
from summoner.visionary import ClientFlowVisualizerNote
Inside the extension-utilities repository itself, local tests may import modules directly from the repo layout (for example from tooling.curl_tools import ...). For normal SDK usage, always import from summoner.<module>.
- Visualization and state introspection tools for agent graphs and execution flow.
- Status: Stable.
- Link:
visionary
- Utilities for parsing and interpreting
curlcommands into structured protocol calls. - Status: In progress.
- Link:
curl_tools
- Cost control and safety utilities for managing LLM usage and execution constraints.
- Status: Experimental.
- Link:
gpt_guardrails
« Previous: Agent Extentions | Next: Developer & Contribution »