agent-design

Design and review LLM agents covering tool design, loops, memory, guardrails, and multi-agent orchestration.

15|3|Updated Jul 9, 2026
One-click install
npx skills add https://github.com/thefear078/cursor-kit-for-ai --skill agent-design-thefear078
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agent-design
Source: https://github.com/thefear078/cursor-kit-for-ai/tree/main/plugins/ai/skills/agent-design
Command: npx skills add https://github.com/thefear078/cursor-kit-for-ai --skill agent-design-thefear078

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? LLM agents fail in predictable ways — infinite loops, tool misuse, runaway costs, and prompt-injection-driven actions. This Skill provides a structured design and review playbook that addresses these failure modes up front, helping you decide whether a task needs an agent at all and how to constrain it when it does. ## Core Features & Use Cases - Autonomy Escalation Ladder: Decide between a single LLM call, a fixed chain, an agent, or multi-agent orchestration before writing any code. - Tool & Loop Design Rules: Guidelines for orthogonal tool sets, description-as-prompt authoring, hard iteration/token/time caps, loop detection, and explicit terminal states. - Guardrails & Evaluation Checklists: Injection canary tests, code-level gating of destructive actions, per-run tracing, and eval suites with task fixtures. - Use Case: When your support agent keeps retrying the same failing tool call and burning API budget, use this Skill's loop-containment and review checklist to add caps, loop detection, and explicit failure states. ## Quick Start Ask the AI to review your existing agent implementation against the agent-design checklist and identify missing loop caps, ungated destructive tools, and injection vulnerabilities.

Frequently Asked Questions about agent-design

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I stop an LLM agent from looping infinitely?▼

Set all three hard caps per run: max iterations, max tokens or spend, and a wall-clock timeout. Add loop detection that flags when the same tool is called with identical arguments twice, and define explicit terminal states for success, failure, and needs-human.

How many tools should an LLM agent have?▼

Five to ten well-named, orthogonal tools outperform thirty overlapping ones, since choice paralysis measurably increases error rates. Tool descriptions act as prompts, so state when to use each tool, when not to, and what it returns.

How do I protect an agent from prompt injection attacks?▼

Treat everything the agent reads as untrusted input. Use per-task tool allowlists, gate irreversible actions like send or delete behind human confirmation in code, apply least-privilege credentials, and run an injection canary test verifying malicious instructions are reported, not obeyed.

When should I use multi-agent orchestration instead of one agent?▼

Use multi-agent only when a single context window cannot hold the roles or when roles need different tools and models. Prefer an orchestrator-worker pattern with typed input/output contracts between agents, and log per-hop token costs from day one.