Skill Claude CodeCodex
Use when gathering information, researching topics, summarizing literature, or exploring ideas with primary sources. Read-only focus.
Build, stream, and monetize interactive AI agents with federated MCP tools and pay-per-request billing.
Skill Claude CodeCodex
Use when gathering information, researching topics, summarizing literature, or exploring ideas with primary sources. Read-only focus.
Skill Claude CodeCodex
Use when reviewing Teardrop Python dependencies for vulnerabilities, upgrade drift, changelog risk, and safer alternatives using the local audit script plus primary package metadata.
Skill Claude CodeCodex
Use when running a short human-in-the-loop Teardrop development cycle that needs scoped research, a concrete plan, implementation, and strict verification with high token efficiency.
Skill Claude CodeCodex
Use when upgrading, deprecating, or replacing Teardrop LLM router models, including pricingrules updates, benchmark catalogue changes, model sunset plans, and migration scaffolding for new provider releases.
Skill Claude CodeCodex
Use when the user wants query-driven, cited repository research for Teardrop security, roadmap, improvements, or competitive questions and a Git-tracked draft report.
Skill Claude CodeCodex
Use when reviewing code, research, or plans for bugs, inconsistencies, security issues, and quality.
Skill Claude CodeCodex
Use when implementing, refactoring, and writing high-quality code based on plans or research.
Skill Claude CodeCodex
Use for any work touching Teardrop billing (x402/credits/Stripe), pricing, marketplace (platform tools vs org tools), MCP gateway, A2A delegation, SSRF, or financial database migrations. Provides authoritative invariants and file map.
Skill Claude CodeCodex
Use after adding tools, changing planner behavior, adjusting pricing, or modifying model routing. Guides writing eval tasks, running baseline diffs, and enforcing regressions with Teardrop eval harness.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: