Good fit

You are likely a good fit if your team:

Ships agents that call tools through MCP, OpenAPI, OpenAI Agents SDK, Anthropic Messages API, Google ADK, LangChain/LangGraph, CrewAI, Codex plugins, n8n workflows, or OpenAI Agents API artifacts.
Has tools that refund, email, cancel, deploy, modify records, read sensitive data, or change infrastructure.
Wants advisory PR evidence before moving to stricter CI behavior.
Can share sanitized findings, workflow constraints, or integration feedback with Three Moons Lab.

Probably not a fit (yet)

You are probably not a fit if you need a hosted policy engine, runtime gateway, compliance certification, or private-data upload flow today. Agents Shipgate is currently a local-first open-source scanner and GitHub Action; the longer roadmap on the about page covers more of those slots over time.

What you get

Help mapping an existing agent repository to shipgate.yaml.
A first Tool-Use Readiness Report for one agent or tool surface.
Guidance on advisory CI, baselines, suppressions, and strict-mode rollout.
Early influence on check semantics, report shape, framework adapters, and agent-facing workflows.

What Three Moons Lab asks for

A concrete agent / tool-surface use case.
Feedback on whether the findings are actionable for platform, security, and release reviewers.
Permission to use anonymized lessons in docs or category writing, only when explicitly approved.

Contact

Email help@threemoonslab.com with the subject Agents Shipgate design partner review. Include:

Agent framework (OpenAI Agents SDK, Anthropic, LangChain, CrewAI, Google ADK, MCP-only, etc.).
Tool-source types (MCP exports, OpenAPI specs, SDK code, Codex plugins, n8n workflows).
Current CI system (GitHub Actions, GitLab CI, CircleCI, other).
Workflow preference (local CLI, GitHub Action, or both).
What you'd like to evaluate first.