/ professional agent infrastructure

Appearance

Get started
/ professional agent infrastructureStarGet started

PROAGENTS / v0.16.1 / OPEN SOURCE — MIT

Give your coding agent a profession.

ProAgents equips the agent you already use with a Professional Agent Profile — expertise, methods, rules, tools and verification, versioned in an open JSON registry and compiled into your harness.

Equip a profileBrowse the registry

01 RUNS WITH ANY HARNESS

One profession.
Every harness.

A coding agent can write code. A professional agent knows how the work should be done — on whichever harness your team already runs.

ProAgents compiles one canonical profile into each environment's native mechanisms — skills, rules, hooks, MCP — and reports what a harness cannot enforce. New harness? Recompile, don't rewrite.

9 native targets · generic-cli covers everything else

02 PROFILE / JSON REGISTRY

What a profession
is made of.

A profile is a folder of modular JSON sections behind one manifest.json. The same paths feed loaders, validators, adapters and CI.

manifest.json

{
  "identity": "./identity.json",
  "handoffs": ["./handoffs/*"],
  "rules": ["./rules/*"],
  "verification": "./verification.json"
}

paths hydrated / prose not parsed

Full schema in Profile schema · scaffold one with proagent profile create

03 THE EQUATION

One profile.
Every harness.

The canonical profile compiles into the harness your team already runs. Same profession, native mechanisms — limitations reported, never hidden.

CANONICAL PROFILEsecurity-engineerregistry / profile.v1 — one JSON source of truth
AGENT HARNESS
Claude Code
the environment your team already runs
PROFESSIONAL AGENT
proagent
same agent — now with a profession
proagent equip security-engineer --target claude-codeone command compiles the profile into the selected harness

04 CREWS / MULTI-AGENT

Many professionals.
One workflow.

A crew wires profile-backed workers into a handoff graph — each member keeps its profession, its scoped permissions and its own verification before done.

security-audit-crew 4 workers · 5 handoffs · installable as one unit

  1. Audit Scoutsystems-architectread: repo · write: none
  2. Threat Modelersecurity-engineerread: repo · write: none
  3. Code Security Auditorsecurity-engineerread: repo · write: none
  4. Privacy Auditorprivacy-engineerread: repo · write: none

+ approval gates where it matters: the release-train's deploy step requires a human go.

proagent crew install pr-review-gate2 workers — Read-only review gate for pull requestsproagent crew install security-audit-crew4 workers — Threat-model-driven security auditproagent crew install release-train-crew4 workers — QA sign-off → release → gated deployproagent crew install data-platform-crew4 workers — Schema, pipeline and quality ownershipproagent crew install web-quality-crew4 workers — Performance and accessibility passes

Every member compiles for your harness. Browse all crews

05 VALIDATION / EVIDENCE

A professional
leaves evidence.

No black box. Deterministic checks gate install, publish and resolution so a broken profession cannot quietly enter the system.

proagent profile validate manifest.json

✓ manifest resolved

✓ 10 sections hydrated

✓ enforcement targets mapped

✓ verification requirements present

codescopecatches
PA030profilemanifest section path is missing
PA035profilerule has no enforceable target
PA043crewproduction write lacks an approval gate
PA047crewmember file mismatches its manifest

06 COMMUNITY / LAUNCH

Launch week on
Product Hunt.

ProAgents is live on Product Hunt. A vote takes ten seconds; a founder review lasts longer — tell us which profession your agent should learn next.

07 START HERE

Give the work
a standard.

Install the CLI, pick a profession, and keep the harness your team already trusts. The compiler does the porting — verification does the proof.

25professions8crews9harness targetsMITopen source

profile compiled / verification required

Read the quickstartCLI reference