Quickstart

From empty repo to installable pack in 6 steps.

AFPS is a CLI, a package format, and a registry. This walkthrough takes you from afps init to afps install.

01

Initialize a project

Scaffolds .afps/ with a manifest, rules, workflows, schemas, tests, and a receipts log.

afps init
afps doctor
02

Author your first pack

A pack is the unit of distribution. It bundles rules, workflows, schemas, tests, and activation metadata.

afps pack new agentic-privileged-saas-access-flow
cd packs/agentic-privileged-saas-access-flow
03

Lint and review

Static checks for manifest validity, activation coverage, and schema references. The reviewer scores the pack against the conformance rubric.

afps lint
afps review --threshold 0.85
04

Run scenario evals

Compare baseline agent behavior to behavior after the pack is installed. The gate fails if uplift is below the configured threshold.

afps eval run --baseline --with-pack
afps eval report --format md > EVAL.md
05

Publish

Signs the bundle, generates a scorecard, and pushes to a registry.

afps publish --registry registry.afps.dev
06

Install in an agent

Any AFPS-aware agent runtime can resolve, verify, and activate the pack based on its triggers.

afps install agentic-privileged-saas-access-flow

Next

Read the flagship pack for a real-world example, or browse the registry.