Token导航 LogoToken导航TokenDH.com
研究检索操作浏览器github未标认证来源可访问clear审计提醒

ai-agentsAI 特工

Agent Skill

ai-agents 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

2,899

周安装

122

GitHub Stars

59

下载量

1,015
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

3

许可证

MIT

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:ai-agents(AI 特工)
来源仓库:https://github.com/vasilyu1983/ai-agents-public
仓库路径:skills/ai-agents
安装命令:
npx skills add https://github.com/vasilyu1983/ai-agents-public --skill ai-agents
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。不同来源提供的安装方式可能略有差异;本站展示可直接复制的安装命令,安装前请核对来源页面。

skills.shnpx skills
npx skills add https://github.com/vasilyu1983/ai-agents-public --skill ai-agents

简介

用于查找、检索和筛选相关信息。适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

  • 适合根据关键词或任务场景快速定位候选结果。
  • 通过 npx 命令从指定仓库安装,需确认权限与维护状态。
  • 注意可能触发联网、命令执行或文件读写操作。
  • ai-agents 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

SKILL.md

AI Agents Development — Production Skill Hub

Modern Best Practices (March 2026): deterministic control flow, bounded tools, auditable state, MCP-based tool integration, handoff-first orchestration, multi-layer guardrails, OpenTelemetry tracing, and human-in-the-loop controls (OWASP LLM Top 10: https://owasp.org/www-project-top-10-for-large-language-model-applications/).

This skill provides production-ready operational patterns for designing, building, evaluating, and deploying AI agents. It centralizes procedures, checklists, decision rules, and templates used across RAG agents, tool-using agents, OS agents, and multi-agent systems.

No theory. No narrative. Only operational steps and templates.


When to Use This Skill

Codex should activate this skill whenever the user asks for:

  • Designing an agent (LLM-based, tool-based, OS-based, or multi-agent).
  • Scoping capability maturity and rollout risk for new agent behaviors.
  • Creating action loops, plans, workflows, or delegation logic.
  • Writing tool definitions, MCP tools, schemas, or validation logic.
  • Generating RAG pipelines, retrieval modules, or context injection.
  • Building memory systems (session, long-term, episodic, task).
  • Creating evaluation harnesses, observability plans, or safety gates.
  • Preparing CI/CD, rollout, deployment, or production operational specs.
  • Producing any template in /references/ or /assets/.
  • Implementing MCP servers or integrating Model Context Protocol.
  • Setting up agent handoffs and orchestration patterns.
  • Configuring multi-layer guardrails and safety controls.
  • Evaluating whether to build an agent (build vs not decision).
  • Calculating agent ROI, token costs, or cost/benefit analysis.
  • Assessing hallucination risk and mitigation strategies.
  • Deciding when to kill an agent project (kill triggers).
  • For prompt scaffolds, retrieval tuning, or security depth, see Scope Boundaries below.

Scope Boundaries (Use These Skills for Depth)

Default Workflow (Production)


Quick Reference

Agent TypeCore Control FlowInterfacesMCP/A2AWhen to Use
Workflow Agent (FSM/DAG)Explicit state transitionsState store, tool allowlistMCPDeterministic, auditable flows
Tool-Using AgentRoute → call tool → observeTool schemas, retries/timeoutsMCPExternal actions (APIs, DB, files)
RAG AgentRetrieve → answer → citeRetriever, citations, ACLsMCPKnowledge-grounded responses
Planner/ExecutorPlan → execute steps with capsPlanner prompts, step budgetMCP (+A2A)Multi-step problems with bounded autonomy
Multi-Agent (Orchestrated)Delegate → merge → validateHandoff contracts, eval gatesA2ASpecialization with explicit handoffs
OS AgentObserve UI → act → verifySandbox, UI groundingMCPDesktop/browser control under strict guardrails
Code/SWE AgentBranch → edit → test → PRRepo access, CI gatesMCPCoding tasks with review/merge controls

Framework Selection (March 2026)

Tier 1 — Production-Grade

FrameworkArchitectureBest ForLanguagesEase
LangGraphGraph-based, statefulEnterprise, compliance, auditabilityPython, JSMedium
Claude Agent SDKEvent-driven, tool-centricAnthropic ecosystem, Computer Use, MCP-nativePython, TSEasy
OpenAI Agents SDKTool-centric, lightweightFast prototyping, OpenAI ecosystemPythonEasy
Google ADKCode-first, multi-languageGemini/Vertex AI, polyglot teamsPython, TS, Go, JavaMedium
Pydantic AIType-safe, graph FSMProduction Python, type safety, MCP+A2A nativePythonMedium
MS Agent FrameworkKernel + multi-agentEnterprise Azure,.NET/Java teamsPython,.NET, JavaMedium

Tier 2 — Specialized

FrameworkArchitectureBest ForLanguagesEase
LlamaIndexEvent-driven workflowsRAG-native agents, retrieval-heavyPython, TSMedium
CrewAIRole-based crewsTeam workflows, content generationPythonEasiest
MastraVercel AI SDK-basedTypeScript/Next.js teamsTypeScriptEasy
SmolAgentsCode-first, minimalistLightweight, fewer LLM callsPythonEasy
AgnoFastAPI-native runtimeProduction Python, 100+ integrationsPythonEasy
AWS Bedrock AgentsManaged infrastructureEnterprise AWS, knowledge basesPythonEasy

Tier 3 — Niche

FrameworkNiche
HaystackEnterprise RAG+agents pipeline (Airbus, NVIDIA)
DSPyDeclarative optimization — compiles programs into prompts/weights

See references/modern-best-practices.md for detailed comparison and selection guide.

Framework Deep Dives


Decision Tree: Choosing Agent Architecture

What does the agent need to do?
    ├─ Answer questions from knowledge base?
    │   ├─ Simple lookup? → RAG Agent (LangChain/LlamaIndex + vector DB)
    │   └─ Complex multi-step? → Agentic RAG (iterative retrieval + reasoning)
    │
    ├─ Perform external actions (APIs, tools, functions)?
    │   ├─ 1-3 tools, linear flow? → Tool-Using Agent (LangGraph + MCP)
    │   └─ Complex workflows, branching? → Planning Agent (ReAct/Plan-Execute)
    │
    ├─ Write/modify code autonomously?
    │   ├─ Single file edits? → Tool-Using Agent with code tools
    │   └─ Multi-file, issue resolution? → Code/SWE Agent (HyperAgent pattern)
    │
    ├─ Delegate tasks to specialists?
    │   ├─ Fixed workflow? → Multi-Agent Sequential (A → B → C)
    │   ├─ Manager-Worker? → Multi-Agent Hierarchical (Manager + Workers)
    │   └─ Dynamic routing? → Multi-Agent Group Chat (collaborative)
    │
    ├─ Control desktop/browser?
    │   └─ OS Agent (Anthropic Computer Use + MCP for system access)
    │
    └─ Hybrid (combination of above)?
        └─ Planning Agent that coordinates:
            - Tool-using for actions (MCP)
            - RAG for knowledge (MCP)
            - Multi-agent for delegation (A2A)
            - Code agents for implementation

Protocol Selection:

  • Use MCP for: Tool access, data retrieval, single-agent integration
  • Use A2A for: Agent-to-agent handoffs, multi-agent coordination, task delegation

Framework Selection (after choosing architecture):

Which framework?
    ├─ MVP/Prototyping?
    │   ├─ Python → OpenAI Agents SDK or CrewAI
    │   └─ TypeScript → Mastra or Claude Agent SDK
    │
    ├─ Production →
    │   ├─ Auditability/compliance? → LangGraph
    │   ├─ Type safety + MCP/A2A native? → Pydantic AI
    │   ├─ Anthropic models + Computer Use? → Claude Agent SDK
    │   ├─ Google Cloud / Gemini? → Google ADK
    │   ├─ Azure / .NET / Java? → MS Agent Framework
    │   ├─ AWS managed? → Bedrock Agents
    │   └─ RAG-heavy? → LlamaIndex Workflows
    │
    ├─ Minimalist / Research →
    │   ├─ Fewest LLM calls? → SmolAgents
    │   └─ Optimize prompts automatically? → DSPy
    │
    └─ Enterprise pipeline → Haystack

Core Concepts (Vendor-Agnostic)

Control Flow Options

  • Reactive: direct tool routing per user request (fast, brittle if unbounded).
  • Workflow (FSM/DAG): explicit states and transitions (default for deterministic production).
  • Planner/Executor: plan with strict budgets, then execute step-by-step (use when branching is unavoidable).
  • Orchestrated multi-agent: separate roles with validated handoffs (use when specialization is required).

Memory Types (Tradeoffs)

  • Short-term (session): cheap, ephemeral; best for conversational continuity.
  • Episodic (task): scoped to a case/ticket; supports audit and replay.
  • Long-term (profile/knowledge): high risk; requires consent, retention limits, and provenance.

Failure Handling (Production Defaults)

  • Classify errors: retriable vs fatal vs needs-human.
  • Bound retries: max attempts, backoff, jitter; avoid retry storms.
  • Fallbacks: degraded mode, smaller model, cached answers, or safe refusal.

Do / Avoid

Do

  • Do keep state explicit and serializable (replayable runs).
  • Do enforce tool allowlists, scopes, and idempotency for side effects.
  • Do log traces/metrics for model calls and tool calls (OpenTelemetry GenAI semantic conventions: https://opentelemetry.io/docs/specs/semconv/gen-ai/).

Avoid

  • Avoid runaway autonomy (unbounded loops or step counts).
  • Avoid hidden state (implicit memory that cannot be audited).
  • Avoid untrusted tool outputs without validation/sanitization.

Navigation: Economics & Decision Framework

Should You Build an Agent?

- 10-second test (volume, cost, error tolerance) - Red flags and immediate disqualifiers - Alternatives to agents (usually better) - Full decision tree with stage gates - Kill triggers during development and post-launch - Pre-build validation checklist

Agent ROI & Token Economics

- Token pricing by model (January 2026) - Cost per task by agent type - ROI calculation formula and tiers - Hallucination cost framework and mitigation ROI - Investment decision matrix - Monthly tracking dashboard


Navigation: AI Engine Layers

Five-layer architecture for production agent systems. Start with the overview, then drill into layer-specific patterns.

Action Graph → covered by references/operational-patterns.md + references/agent-operations-best-practices.md Data Agent → covered by ../ai-rag/SKILL.md + references/rag-patterns.md

Navigation: Core Concepts & Patterns

Governance & Maturity

- Capability maturity levels (L0-L4) - Identity & policy enforcement - Fleet control and registry management - Deprecation rules and kill switches

Modern Best Practices

- Model Context Protocol (MCP) - Agent-to-Agent Protocol (A2A) - Agentic RAG (Dynamic Retrieval) - Multi-layer guardrails - LangGraph over LangChain - OpenTelemetry for agents

Context Management

- Progressive disclosure - Session management - Memory provenance - Retrieval timing - Multimodal context

Core Operational Patterns

- Agent loop pattern (PLAN → ACT → OBSERVE → UPDATE) - OS agent action loop - RAG pipeline pattern - Tool specification - Memory system pattern - Multi-agent workflow - Safety & guardrails - Observability - Evaluation patterns - Deployment & CI/CD


Navigation: Protocol Implementation


Navigation: Agent Capabilities

Skill Packaging & Sharing

Framework-Specific Patterns

  • Pydantic AI Patterns - references/pydantic-ai-patterns.md Type-safe agents, MCP toolsets (Stdio/SSE/StreamableHTTP), A2A via to_a2a(), pydantic-graph FSM, durable execution, TestModel testing

Navigation: Production Operations


Navigation: Templates (Copy-Paste Ready)

Checklists

Core Agent Templates

RAG Templates

Tool Templates

Multi-Agent Templates

Service Layer Templates


External Sources Metadata

  • Curated References - data/sources.json Authoritative sources spanning standards, protocols, and production agent frameworks

Shared Utilities (Centralized patterns — extract, don't duplicate)


Trend Awareness Protocol

IMPORTANT: When users ask framework recommendations or "what's best for X" questions, use WebSearch to verify current landscape before answering. If unavailable, use data/sources.json and state what was verified vs assumed.

Trigger: framework comparisons, "best for [use case]", "is X still relevant?", "latest in AI agents", MCP server availability.

Report: current landscape, emerging trends, deprecated patterns, recommendation with rationale.


Related Skills

This skill integrates with complementary skills:

Core Dependencies

  • ../ai-llm/ - LLM patterns, prompt engineering, and model selection for agents
  • ../ai-rag/ - Deep RAG implementation: chunking, embedding, reranking
  • ../ai-prompt-engineering/ - System prompt design, few-shot patterns, reasoning strategies

Production & Operations

Supporting Patterns

Usage pattern: Start here for agent architecture, then reference specialized skills for deep implementation details.


Usage Notes

  • Modern Standards: Default to MCP for tools, agentic RAG for retrieval, handoff-first for multi-agent
  • Lightweight SKILL.md: Use this file for quick reference and navigation
  • Drill-down resources: Reference detailed resources for implementation guidance
  • Copy-paste templates: Use templates when the user asks for structured artifacts
  • External sources: Reference data/sources.json for authoritative documentation links
  • No theory: Never include theoretical explanations; only operational steps

AI-Native SDLC Template

Fact-Checking

  • Use web search/web fetch to verify current external facts, versions, pricing, deadlines, regulations, or platform behavior before final answers.
  • Prefer primary sources; report source links and dates for volatile information.
  • If web access is unavailable, state the limitation and mark guidance as unverified.

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

04

需要参考平台分布和安装热度时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Claude Code

29.82%
按下载量换算303

Cursor

22.81%
按下载量换算232

Gemini CLI

18.62%
按下载量换算189

Antigravity

11.96%
按下载量换算121

OpenCode

8.08%
按下载量换算82

github-copilot

3.84%
按下载量换算39

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

操作浏览器

该 Skill 可能涉及浏览器控制能力,使用时可能读取或操作网页内容,需要在受控环境中确认权限边界。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果,不能写成本站确认安全。

来源信息

继续浏览同类 Skills