Defenter 代理
v0.0.96
io.github.Defenter-AI/defenter-proxy
为 AI 编码智能体与 MCP 工具提供实时语义安全防护。
“Coding” 共 1,282 个结果
v0.0.96
io.github.Defenter-AI/defenter-proxy
为 AI 编码智能体与 MCP 工具提供实时语义安全防护。
v0.1.0
io.github.n0zer0d4y/athena-protocol
为编码智能体充当 AI 技术主管,负责方案校验与改动影响分析。
v3.0.0
ai.smithery/ref-tools-ref-tools-mcp
为 AI 编码工具提供省 token 的通道。
v3.0.1
tools.ref/ref-tools-mcp
为编码智能体在公开与私有文档上进行省 token 的高效检索。
v0.3.20
io.github.OtherVibes/mcp-as-a-judge
MCP as a Judge:通过显式 LLM 评估来强化 AI 编程助手的行为型 MCP。
v3.0.1
io.github.ref-tools/ref-tools-mcp
面向编码智能体的公开与私有文档高 token 效率搜索。
v1.3.1
io.github.kevint-cerebras/cerebras-code-mcp
面向 Cerebras 的 Model Context Protocol(MCP)服务器,让 AI 优先的 IDE 中编码更快。
v0.1.1
md.install/try
把使用指南做成 MCP server,教编程 agent 使用你的软件(库、API 等)。
skillsmp.ruvnet-ruflo-skill-md
Ruflo 是面向 AI 编码 agent(Claude Code、Cursor、Codex、Copilot、Gemini、Amp 及另外 12 家)的多 agent 编排平台。当用户希望:(1)在项目中安装/初始化 ruflo;(2)运行采用分层协同的多 agent swarm;(3)使用 ruflo 的 314+ MCP 工具处理记忆、路由、钩子、sub-agent 或工作流;(4)查看 ruflo 状态/版本/doctor 健康检查;(5)为任务挑选合适的 ruflo 插件(共 30+)时使用本 skill。
skillsmp.nidhinjs-prompt-master-skill-md
为 AI 工具生成优化后的提示词。仅在用户明确要求为某个具体 AI 工具(LLM、Cursor、Midjourney、图像 AI、视频 AI、编码 agent 等)撰写、修复、改进或改写提示词时激活。不响应一般对话、编码任务、文档撰写或其他非提示词工程工作。
io.github.garrytan/gstack/setup-gbrain
为当前编码 agent 配置 gbrain:安装 CLI、初始化本地 PGLite 或 Supabase brain、注册 MCP、逐远端记录信任策略。(gstack)
io.github.openai/codex/openai-docs
用于 Codex 模型/定价、定时任务、skills、设置、安装、排障、定制、自动化与自我知识——包括指代 Codex 的“you”“your”“this app”“this coding agent”——以及 OpenAI API/产品与 ChatGPT Work 的问题。也用于模型选型/迁移、prompt 撰写、SDK、Responses、Realtime、agents、evals 以及 Chat/Work/Codex 的对比。仅提到 Codex 的普通应用/软件任务不适用。
io.github.DietrichGebert/ponytail/ponytail
强制采用真正可行的最懒方案:最简、最短、最少。模仿一位见惯一切资深工程师的姿态:先质疑任务是否根本不必存在(YAGNI),优先标准库而非自写代码、平台原生能力而非引依赖、一行而非五十行。支持强度档位:lite、full(默认)、ultra。适用于任何编码任务:编写、新增、重构、修复、审查、设计代码以及选择库或依赖。当用户说 ponytail、be lazy、lazy mode、最简方案、minimal solution、YAGNI、do less、shortest path,或抱怨过度设计、膨胀、模板代码、不必要的依赖时也应使用。不用于非编码请求(通识、文章、翻译、摘要、菜谱)。
io.github.metabase/metabase/typescript-review
依据 Metabase 编码标准审查 TypeScript/JavaScript 代码变更,检查风格违规与代码质量问题。在审查包含 TS/JS 代码的 PR 或 diff 时使用。
io.github.affaan-m/ECC/brownfield-retrospective
Run the ECC engineering process retroactively against an existing project slice. Audit current state, reconstruct past decisions, produce a four-axis gap register (thinking, coding practice, missing features, technology selection), then execute fixes forward through the plan-TDD-review pipeline. Use when adopting ECC mid-project, taking over an inherited codebase, or asking what was missed and what would have been built differently from day one.
io.github.affaan-m/ECC/token-card
Render a token-usage stat card from local Claude Code, Codex, Gemini CLI, and OpenCode session logs and commit it into the repository as a file. Use when someone wants a current usage figure in a README, or asks for a shareable card of their coding-agent activity.
io.github.metabase/metabase/typescript-write
按 Metabase 编码标准与最佳实践编写 TypeScript 和 JavaScript 代码。在开发或重构 TS/JS 代码时使用。
io.github.mattpocock/skills/code-review
从某个基准点(commit、分支、标签或 merge-base)出发,沿两个维度审查变更:规范(代码是否遵循本仓库成文的编码规范?)与规格(代码是否符合来源 issue/规格的要求?)。两组审查由并行子代理执行并对照汇报。当用户想审查分支、PR、进行中的变更,或要求“review since X”时使用。
io.github.coollabsio/coolify/infer-conventions
Use this skill to analyze how a Laravel application is actually written and record its conventions as shared rules. Trigger when the user wants to detect, infer, document, or standardize project conventions or coding style, set up or grow `.ai/rules`, resolve mixed or conflicting patterns (e.g. "are we using Form Requests or inline validation?"), or onboard agents and teammates to "how we do things here". Covers: a systematic sweep of ~49 Laravel convention dimensions (validation, models, architecture, testing, frontend, database, console), open-ended house-pattern discovery, conflict reporting, and recording rules scoped to the right paths via the Boost `record-rule` MCP tool. Only run this skill when the user explicitly asks for it; never start a sweep as part of another task. Do not use for one-off code review, enforcing formatting a linter already handles, or editing `.ai/rules` files by hand.
io.github.affaan-m/ECC/inherit-legacy-style
Prevent AI style drift on legacy projects by scanning the codebase for implicit conventions, resolving conflicts with the operator one at a time, and writing an enforceable .ai-style-rules.md (Golden Files, naming rules, DONTs) plus an optional CLAUDE.md hook. Use when onboarding an AI agent onto a hand-written legacy codebase or extracting a project's unwritten coding rules.
io.github.affaan-m/ECC/agent-eval
Head-to-head comparison of coding agents (Claude Code, Aider, Codex, etc.) on custom tasks with pass rate, cost, time, and consistency metrics. Use when choosing between coding agents, or when a change to an agent setup needs measured pass rate, cost, and time rather than an impression.
io.github.langchain-ai/deepagents/safety
Check secret handling, staged changes and push targets, destructive Git operations, Docker image hygiene, and new dependencies before consequential coding actions. Use for commits, pushes, container builds or publishes, dependency additions, and explicit safety reviews.
io.github.affaan-m/ECC/eval-harness
面向 Claude Code 会话的正式评估框架,落实评估驱动开发(EDD)原则。当 Claude Code 工作流在获得信任或被修改前需要正式评估时使用。
io.github.affaan-m/ECC/search-first
先检索再编码的工作流。在动手编写自定义代码之前,先搜索已有的工具、库和模式。会调用 researcher 代理。