Skip to main content
Glama
koten-ai

io.github.koten-ai/zeus-dev-helper

Official
by koten-ai

Related Servers

Alternatives to io.github.koten-ai/zeus-dev-helper

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      A
      maintenance
      Local-first Agent OS that wraps Claude Code, Codex CLI, and other coding agents in a replayable Seed → Ledger → Runtime contract, driven by an interview → seed → execute → evaluate → evolve workflow loop.
      34
      31,487 PyPI
      6,071
      MIT
    • F
      license
      A
      quality
      C
      maintenance
      Enables coding agents to design first by interviewing users, refining specs in digestible chunks, producing bite-sized TDD plans, and autonomously executing them through subagents with a server-verified red/green testing gate.
      11
      -
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables evidence-gated, multi-session AI coding runs with plan-build-ship state management, coordinating Claude Code and Codex native agents.
      10 npm
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables orchestration of autonomous coding agents (Claude Code, Cursor, etc.) through an objective-native planning board with hash-chained audit trail. Humans define outcomes, agents claim and execute tasks via MCP.
      7
      -
    • A
      license
      Not graded
      quality
      F
      maintenance
      Enables AI agents to autonomously request services from other specialized agents and compensate them via x402 micropayments. Demonstrates a Machine-to-Machine economy using A2A protocol for agent communication, MCP for context management, and blockchain-based payments on Base network.
      32 npm
      2
      MIT

    TDQS

    B3.1/5.0

    Scored across 12 tools

    Disambiguation3/5

    There is some overlap between smoke_test_agent and smoke_test_zeus, and between doctor and readiness_check, which could confuse an agent. However, other tools like bind_contract, scaffold_app, and use_sample have distinct purposes, so the ambiguity is limited.

    Naming Consistency3/5

    The naming is a mix of verb_noun patterns (e.g., smoke_test_agent, readiness_check) and bare verbs (doctor, next_step). While most use snake_case, the inconsistency between using 'check' in readiness_check and 'doctor' for health might cause minor confusion.

    Tool Count4/5

    With 12 tools, the count is within the typical well-scoped range for a complex developer assistant. Each tool addresses a different aspect of the development workflow, though the number feels slightly high but not problematic.

    Completeness3/5

    The set covers the core lifecycle of starting, configuring, and verifying a project, but lacks tools for explicit update or deletion of configuration or samples. Some workflows might require manual steps outside the toolset, creating minor gaps.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues