What is a Cursor agent in AgenticKit?

A named role file (tech-lead, api-engineer, seo-specialist) that the session adopts. In Cursor it lives in .cursor/agents/. In Claude Code it is a real subagent in .claude/agents/ with its own tool and model grant. It is not Cursor's built-in Agent product.

Why 46 agents instead of one?

Writer, reviewer, and security cannot be the same desk. Marketing cannot share a context window with a migration. The split is the product.

How do I invoke an agent?

Run a command such as /ship or /launch, which adopts roles in order, or start a chat and tell Cursor to act as that named agent after reading its skills.

Do I need the marketing agents?

Only if you are launching, positioning, or publishing. Install the engineering kit alone if this month is code.

Can tech-lead write production code?

No. The tech-lead playbook forbids it. Planning and implementation in one role is how unstructured Cursor chats fail.

46 Cursor & Claude Code Agents for Engineering and Marketing

Custom agents vs the built-in Agent

“Cursor agents” in Google usually means the product: Agent mode, cloud agents, parallel worktrees. This page is the other meaning: specialist files a session can adopt so it stops being a generic pair programmer.

If you want the harness, use Cursor. If you want a tech lead that is not allowed to merge its own code, that is tech-lead.

Engineering team

28 roles: architecture, API, Postgres, React, security, tests, infra, data, mobile. /ship adopts them in order. code-reviewer and security-auditor are separate desks from the writer.

Marketing team

18 roles: growth, launch, copy, positioning, SEO, content, email, brand, competitive, research, Reddit, social. /launch is the coordinator. seo-specialist owns titles, schema, and clusters, the work this site is doing.

Agent relationships

Every agent lists skills it must read and commands that invoke it. Example: seo-specialist → on-page SEO skill, pillar-cluster skill, /seo-audit, /blog-post.

See the graph on any agent page, or type a feature into the Agent Chain tool.

Agent workflows

/ship does not fork 34 processes. It tells one session to adopt each specialist, emit a phase header, read that agent's skills, and stop on a failed gate. Marketing stays in a different chat unless you installed both kits and still started a new thread.

Featured agents

Technical Lead & System Architect (tech-lead)Oversees architecture, enforces code conventions, and coordinates agent workflows.
Technical & On-Page SEO Lead (seo-specialist)Optimizes page structure, schema markup, keyword clusters, and rank factors.
Product Launch Coordinator (launch-coordinator)Manages Product Hunt, Hacker News, X/Twitter, and launch day timelines.
API Integration Specialist (api-engineer)Builds bulletproof REST/GraphQL endpoints with Zod validation and types.
Direct Response Copywriter (copywriter)Writes high-converting landing page copy, headlines, value props, and CTAs.
App Security Auditor (security-auditor)Scans for OWASP Top 10 vulnerabilities, XSS, CSRF, injection, and auth leaks.