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
      17,805 PyPI
      6,249
      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.
      17 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
      D
      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.
      200 npm
      2
      MIT

    TDQS

    B3.1/5.0

    Scored across 16 tools

    Disambiguation3/5

    Several tools overlap in verification/prereq/diagnostic space (readiness_check, smoke_test_zeus, smoke_test_agent, website_green, doctor, diagnose_error), and setup tools (set_prereq, load_process_login) can be confused. Descriptions explicitly clarify separations and non-goals, but the agent still needs careful reading to avoid misselection.

    Naming Consistency3/5

    Most names are snake_case, but the set mixes verb_noun patterns (start_project, use_sample, bind_contract) with noun phrases (readiness_check, sample_support_pack) and a single bare noun (doctor). It remains readable but not predictably patterned.

    Tool Count3/5

    With 16 tools, the set sits at the heavy end for a dev-helper server. Many tools earn their place across the lifecycle, but the count feels borderline and contributes to overlap among readiness, smoke, website, and diagnostic operations.

    Completeness4/5

    The surface covers prereq setup, login loading, sample creation, scaffolding, readiness, smoke tests, website checks, diagnostics, support, next-step coaching, surface recommendation, and contract binding. Minor gaps exist around cleanup/reset beyond start_project and explicit secret management, but core workflows are covered.

    Maintenance

    ActivityActive
    ResponsivenessNo issues