Importing from agency-agents

agency-agents is a collection of 144+ specialized AI agent personas organized into 12 professional divisions (engineering, design, marketing, sales, finance, and more). The @tervos/adapter-agency-agents package converts any selection of these agents into a governed Tervos organization.

Clone the Repository

git clone https://github.com/msitarzewski/agency-agents

Import All Agents

Import the entire repository — all 144+ agents across all 12 divisions:

tervos import --from agency-agents ./agency-agents

This produces a single TERVOS.yaml with all agents. The org is flat (no reporting hierarchy) — add reports_to and can_delegate_to manually after import.

Import Specific Divisions

Use --divisions to select only the divisions you need:

tervos import --from agency-agents ./agency-agents \
  --divisions engineering,design

Multiple divisions, comma-separated. Division names match the directory names in the repo (engineering, design, marketing, sales, product, testing, finance, game-development, spatial-computing, specialized, academic, paid-media).

Import a Single Division Directory

You can also point directly at a division directory:

tervos import --from agency-agents ./agency-agents/engineering

Control Output Path

tervos import --from agency-agents ./agency-agents/engineering \
  --output ./my-eng-org/TERVOS.yaml

What Gets Imported

agency-agents field	TERVOS.yaml
`name` frontmatter	Agent `role` and agent key (kebab-cased)
`description` frontmatter	Agent `description`
`vibe` frontmatter (fallback)	Agent `description` (when `description` is blank)
`## Core Mission` bullets	Agent `capabilities` array
Directory name	Used for key deduplication only

Agent Defaults

Every imported agent receives:

Setting	Default	How to Override
`model`	`claude-sonnet-4-20250514`	Edit `TERVOS.yaml`
`budget_monthly_usd`	`100`	Edit `TERVOS.yaml`
`autonomy_level`	`supervised` (org-level)	Edit `TERVOS.yaml`
`reports_to`	Not set (flat org)	Add manually

After Import

Validate:

tervos validate

Review the generated TERVOS.yaml. With 144 agents imported, you’ll want to:

Delete agents you don’t need
Define the reporting hierarchy (reports_to, can_delegate_to)
Set realistic budget_monthly_usd values
Add projects and tasks
Adjust autonomy_level per agent if appropriate

A typical workflow imports only the divisions relevant to your use case rather than all 144 agents.

Example: Engineering + Design Studio

tervos import --from agency-agents ./agency-agents \
  --divisions engineering,design \
  --output studio/TERVOS.yaml

Then open studio/TERVOS.yaml and wire up the hierarchy. For example, make the tech-lead the manager of engineering agents and the design-lead the manager of design agents, with a ceo at the top.