lxyeternal

150 mods across 1 repository, 64 stars between them.

agent-email-inbox

145

lxyeternal/MalSkillBench

Skill Claude CodeCodex

Use when setting up an email inbox for an AI agent (Moltbot, Clawdbot, or similar) - configuring inbound email, webhooks, tunneling for local development, and implementing security measures to prevent prompt injection attacks.

not rated 64 +1 4mo ago B 53 tokens

agent-evaluation

146

lxyeternal/MalSkillBench

Skill Claude CodeCodex

Testing and benchmarking LLM agents including behavioral testing, capability assessment, reliability metrics, and production monitoring—where even top agents achieve less than 50% on real-world benchmarks Use when: agent testing, agent evaluation, benchmark agents, agent reliability, test agent.

not rated 64 +1 4mo ago A 56 tokens

lxyeternal/MalSkillBench

Skill Claude CodeCodex

Build Azure AI Foundry agents using the Microsoft Agent Framework Python SDK (agent-framework-azure-ai). Use when creating persistent agents with AzureAIAgentsProvider, using hosted tools (code interpreter, file search, web search), integrating MCP servers, managing conversation threads, or implementing streaming…

not rated 64 +1 4mo ago A 79 tokens

home-ctxly

148

lxyeternal/MalSkillBench

Skill Claude CodeCodex

Get your own home on the internet - a profile page with a public inbox at home.ctxly.app.

not rated 64 +1 4mo ago A 25 tokens

agent-hq

149

lxyeternal/MalSkillBench

Skill Claude CodeCodex

Deploy the Agent HQ mission-control stack (Express + React + Telegram notifier / Jarvis summary) so other Clawdbot teams can spin up the same board, high-priority watcher, and alert automation. Includes setup, telemetry, and automation hooks.

not rated 64 +1 4mo ago B 55 tokens

agent-identity-kit

150

lxyeternal/MalSkillBench

Skill Claude CodeCodex

A portable identity system for AI agents. Create, validate, and publish agent.json identity cards.

not rated 64 +1 4mo ago A 0 tokens

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: