#a2a
46 resources
Results
- pr-writing-review
Extract and analyze writing improvements from GitHub PR review comments.
- session-investigator
Investigate fast-agent session and history files to diagnose issues.
- cli-contexts
Manage context engineering configurations, RTK filter sets, and conversation sessions from the CLI.
- cli-cost-usage
View cost breakdowns, token usage, and call logs from the CLI.
- cli-eval
Create and run evaluation suites, watch live benchmark progress, view scorecards, compare model performance, and integrate eval runs with…
- cli-policy-audit
Inspect audit logs, manage access policies, view telemetry data, and review request history from the CLI.
- cli-serve
Start, stop, and restart the OmniRoute server from the CLI.
- cli-setup
Run initial setup, configure global CLI settings, manage environment variables, check for updates, and configure autostart via the CLI…
- cli-skill-collector
Detect installed CLI coding tools (Claude Code, Codex, Cursor, Copilot, Cline and more), search GitHub for matching agent skills, and…
- omni-agents-a2a
Interact with OmniRoute via JSON-RPC 2.0 agent-to-agent protocol.
- omni-auth
Manage API key authentication and session tokens.
- omni-combos-routing
Create and manage routing combos with 19 strategies (priority, weighted, round-robin, Auto-combo, and more).
- omni-compression
Configure RTK (command output), Caveman (prose), and stacked compression modes.
- omni-inference
The core OpenAI-compatible inference endpoints: chat completions, embeddings, images, audio (TTS/STT), moderations, rerank, and the…
- omni-mcp
Connect to the OmniRoute MCP server (107 tools, 3 transports: SSE/stdio/HTTP).
- omni-providers
Manage provider connections, API keys, OAuth flows, and connection tests via the REST API.
- omni-resilience
Monitor provider health, circuit-breaker states, p50/p95/p99 latency metrics, and budget guard alerts.
- omni-usage-logs
Access detailed call logs and usage analytics.
- omni-version-manager
Install, start, stop, restart, and update embedded services (9Router, CLIProxyAPI).
- cli-backup-sync
Backup and restore OmniRoute data from the CLI.
- cli-providers
Manage provider connections from the CLI: list available/configured providers, add, test, test-all, validate, rotate API keys, and view…
- config-codex-cli
Step-by-step agent workflow to configure the OpenAI Codex CLI on any machine (Linux, macOS, Windows) to use OmniRoute as an…
- omni-settings
Read and update global application settings: system prompts, thinking budget, IP filters, payload rules, combo defaults, and require-login…
- registry-broker
Search and chat with AI agents across the Universal Agentic Registry via the Hashgraph Online Registry Broker API.
- draw-image
Generate an image from a text prompt using an OpenAI-compatible image generation API (gpt-image-1-mini or compatible).
- omni-cli-tools
Manage CLI tool integrations exposed via the API.
- cli-plugins-skills
Manage Omni Skills (list, install, test, remove), plugins (create, configure), and persistent memory (search, add, clear) from the CLI
- cli-resilience
Inspect and manage circuit-breaker states, connection cooldowns, quota limits, and backoff levels from the CLI.
- omni-sync-cloud
Synchronise OmniRoute configuration, provider connections, and settings to/from cloud storage.
- agentlas-packaging
1. Inspect the existing source: prompt, repo, ZIP, runtime folder, skill, command, or generated agent package. 2. Classify it as single-agent, team-builder, or mixed/unclear. 3. Run contracts/builder-interview-research-gate.md when the so
- agentlas-security-scan
Plan §6.2: stage 1 is static rule screening, stage 2 is a judgment made by the user's own LLM session (BYOK).
- hephaestus-build
1. Treat this as the public Codex build surface. Do not expose or ask the user to invoke the older internal support skill names. 2. Resolve the trusted engine root before reading any build contract:
- hephaestus-network
The active host LLM staffs the task.
- hephaestus-upload
Hephaestus Upload (Cloud or Agentlas Hub)
- routing-card-authoring
Routing Card Field Spec — what goes in every field, and where it lands
- agentlas-operations
Agentlas 시스템 운용 절차 — hep-network 편성, hep-graph 자동화, cargo/Agent Cloud·marketplace 활용, workforce 로스터 재사용, 메모리 계약.
- mode-classification
Use before routing a /meta-agent request to choose single-agent-creator, team-builder, or agentlas-packager from the user's wording and…
- team-builder-packaging
1. Start with the orchestrator/HQ. 2. Run contracts/builder-interview-research-gate.md before writing the roster: ask an 8-12 question first batch, research official sources, similar agent repositories or comparables, academic/professiona
- clarify-question-loop
Ask only questions that change the generated package, runtime adapter, safety boundary, or public/private release decision.
- agentlas
Single entry point for every Agentlas command: /agentlas network, /agentlas build, /agentlas storm, /agentlas graph, /agentlas one,…
- agentlas-auto-activation
Use when adding or auditing local runtime behavior that turns a project folder into an Agentlas-aware workspace with
- hep-storm
Run a force-robust Stormbreaker loop — route to real agents, execute a verified pipeline to completion
- self-evolving-single-agent
1. Keep the package as one worker unless the user asks for a team. 2. Run contracts/builder-interview-research-gate.md before generation: ask an 8-12 question first batch, research official sources, similar agent repositories or comparabl
- code-agent
General-purpose coding agent that reads, writes, and edits code, and searches codebases
- hephaestus-graph
Saved graphs live in the local Agentlas database shared with Agentlas Desktop.
- hep-graph
Build an Agentlas automation by describing it, list saved ones, or request a run
