You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Agent Master List — Prioritised for Launch Seeding
The canonical list of every agent discussed, prioritised into tiers by launch readiness, platform proof value, cluster potential, and audience reach.
Status: Working document | March 2026 Sources: GTM tactics (04, 07), Cold Start (11, marketing package 07), Experience as Product (14), Execution Timeline (12), new consumer/vertical agent list (March 2026)
Prioritisation Criteria
Factor
Weight
Why
Platform proof
Highest
Does it visibly demonstrate Ferite working?
Cluster potential
High
Can it call or be called by other agents?
Build speed
High
Can it be production-grade in days, not weeks?
Developer audience fit
High
Does it resonate with the launch-day audience?
Agent-to-agent economics
Medium
Does it generate A2A transactions?
Revenue potential
Medium
Would callers pay for this?
Breadth of audience
Lower at launch
Consumer appeal matters more in months 3–6
Tier 0 — Platform Meta-Agents (Ferite's Own GTM)
Purpose: Run Ferite's GTM on Ferite. Every agent here is proof, content, and showcase. When: Week -2 to Week 4 (build order below) Source: 07-dogfooding-agents.md
#
Agent
What it does
Build week
A2A role
1
Content Generator
Accepts topic + format + persona → returns draft
Week -1
Called by Orchestrator
2
Support First Responder
Searches docs/FAQ, returns answer, escalates if low confidence
Week -2
Standalone
3
Builder Scout
Scans Twitter/GitHub/Reddit for people building agents
Week 2
Feeds Outreach Personalizer
4
Outreach Personalizer
Takes prospect data → generates personalized email
Week 2
Receives from Builder Scout
5
Community Monitor
Watches communities for keywords → drafts responses
Coordinates agents in workflows (prospect → outreach → monitor)
Week 3
Calls multiple agents
Tier 1 — Launch Seed Agents (Live Before Day 1)
Purpose: The proving ground must feel alive when people arrive. These are the agents visitors see, try, and share. When: Week -3 to Week -1 Target: 30–50 agents across 5–6 clusters Sources: 04-launch-tactics.md, 12-gtm-execution-timeline.md, 14-gtm-experience-as-product.md
Cluster 1: Code Quality (Week -3)
#
Agent
What it does
A2A role
10
code-reviewer
Reviews code for bugs, style, best practices
Specialist — called by code-auditor
11
security-scanner
Scans code for security vulnerabilities
Specialist — called by code-auditor
12
test-writer
Generates unit test scenarios from code/docstrings
Specialist — called by code-auditor
13
doc-generator
Generates documentation from code
Specialist — called by code-auditor
14
dependency-checker
Analyses dependencies for vulnerabilities/updates
Specialist — called by code-auditor
15
code-auditor
Orchestrator — calls all 5 specialists, aggregates report
Orchestrator
Cluster 2: General Utility (Week -3)
#
Agent
What it does
A2A role
16
text-summarizer
Summarises any text to configurable length
Specialist
17
data-transformer
Converts between CSV, JSON, SQL, XML
Specialist
18
translation-service
Translates text between languages
Specialist
Cluster 3: Developer Tools (Week -2)
#
Agent
What it does
A2A role
19
regex-helper
Generates/explains/tests regular expressions
Standalone
20
api-tester
Tests API endpoints, validates responses
Standalone
21
log-analyzer
Parses error logs → likely cause + next checks
Specialist
22
json-validator
Validates JSON against schema
Standalone
Cluster 4: Writing Assistants (Week -2)
#
Agent
What it does
A2A role
23
grammar-checker
Checks grammar, spelling, punctuation
Specialist
24
tone-adjuster
Rewrites text to match a target tone
Specialist
25
headline-generator
Generates headline/title variations
Specialist
Pre-built Starters (Week -1)
Available via npx create-ferite-agent for builders who don't have an agent yet.
#
Agent
What it does
A2A role
26
json-transformer
Converts between data formats (starter variant)
Standalone
27
meeting-notes
Turns transcripts into action items
Standalone
Proving Ground Special
#
Agent
What it does
A2A role
28
ferite-guide
AI guide on the proving ground — explains what visitors are seeing
Standalone
Tier 2 — Week 1–4 Expansion
Purpose: Deepen existing clusters and seed the second major cluster (content processing). These agents add A2A transaction volume and demonstrate multi-step workflows. When: Weeks 1–4 post-launch
Specialised CSV → JSON conversion with type inference
Standalone
Engineering Productivity (from new list)
#
Agent
What it does
A2A role
36
Bug Repro Builder
Converts vague user reports into step-by-step repro
Standalone
37
Log Summarizer
Turns error logs into likely cause + next checks
Standalone (overlaps #21)
38
Release Notes Drafter
Converts merged PR titles into customer-readable notes
Standalone
39
Incident Comms Agent
Drafts status updates in the right cadence + tone
Standalone
40
API Integration Coach
Suggests correct endpoint sequence from a goal description
Standalone
41
Test Case Generator
Produces unit test scenarios from function docstrings/spec
Specialist (extends #12)
Tier 3 — Month 2–3 (Vertical Expansion)
Purpose: Expand beyond developer tooling into high-value verticals that developers and their companies need. These drive exchange revenue and prove breadth.
Customer Support & CX Cluster
#
Agent
What it does
Cluster role
42
Ticket Triage Agent
Classifies tickets, assigns priority + department + tags
Specialist
43
First-Response Draft Agent
Generates L1-quality reply with tone + empathy + next steps
Specialist
44
Clarifying-Questions Agent
Proposes minimum questions needed to unblock diagnosis
Specialist
45
De-escalation Coach
Rewrites replies to reduce conflict, align with policy
Specialist
46
Refund/Returns Policy Navigator
Turns policy docs into compliant, customer-friendly responses
Specialist
47
Support QA Grader
Scores agent replies against rubric (accuracy, tone, completeness)
Specialist
48
Macro Suggestion Agent
Recommends best canned response + tweaks for context
Specialist
49
Churn-Risk Detector
Flags cancellation intent language, suggests retention play
Specialist
Sales & SDR Cluster
#
Agent
What it does
Cluster role
50
Inbound Lead Qualifier
Extracts intent, budget signals, timeline → routes to correct motion
Specialist
51
Outbound Personalizer
Crafts 3–5 sentence email using prospect context pack
Specialist (overlaps #4)
52
Objection Handler Agent
Suggests rebuttals aligned to positioning
Specialist
53
Call Notes → CRM Fields
Turns call summary into structured fields + next steps
Specialist
54
Discovery Question Builder
Generates role-specific discovery questions from product brief
Specialist
55
Pricing Page Explainer
Answers "which plan do I need?" using pricing rules
Standalone
56
RFP Snippet Finder
Retrieves best-approved answers from RFP library
Specialist
Marketing & Content Ops Cluster
#
Agent
What it does
Cluster role
57
Blog Technical Reviewer
Checks for technical inconsistencies vs docs
Specialist
58
Landing Page Variant Agent
Generates 3 headline/value prop variants per persona
Specialist
59
Ad Copy Guardrailer
Rewrites ads to comply with brand voice + platform policy
Purpose: Expand the exchange beyond B2B/developer use cases. These agents demonstrate that Ferite is for any agent, not just code tools. Many are ideal for community builders to create and list.
Personal Productivity Cluster
#
Agent
What it does
Cluster role
86
Daily Planning Agent
Turns goals + calendar into realistic plan with time blocks
Orchestrator candidate
87
Inbox Triage Agent
Labels emails, drafts short replies, identifies "needs action"
Specialist
88
Meeting Prep Agent
Makes agenda + questions + 1-page brief from notes
Specialist
89
Note-to-Actions Agent
Extracts tasks, owners, deadlines from messy notes
Specialist
90
Focus Coach
Detects procrastination patterns, proposes one next tiny step
Aspirational total including community contributions by end of Month 1
Canonical target: 28 Ferite-built agents live before Day 1. 40–50 total with early external builders. 80+ by end of Month 1.
Notes
Agents marked "Standalone" are still valuable — they serve as entry points for builders and callers. Not every agent needs to be part of a cluster.
Overlapping agents (e.g., Outbound Personalizer in Sales overlaps with Outreach Personalizer in Tier 0) should be implemented once and listed in multiple contexts.
Consumer agents (Tier 4) are the strongest candidates for community-built supply. Ferite should provide templates and starters, not build them all.
The 135 agents on this list are not a build plan — they are the universe of agents discussed. The build plan is Tier 0 + Tier 1 + select Tier 2 orchestrators.
This document supersedes agent counts and lists in all previous GTM documents. When counts conflict, refer here.