An atlas of blueprints
for agentic work.

Skills, tools, agents and prompts for Claude Code and PAI. Each blueprint is drafted by a human operator, reviewed by a sponsor, and audited before it's shelved.

Browse the catalog How we keep you safe
1
BLUEPRINTS
4
OPERATORS
2
ACTIVE SPONSORSHIPS
78
EVENTS · LAST 7d

Recently sponsored

SEE ALL →

Drafting floor

LAST 10 EVENTS
22h REVIEW
mellanon · Approved @metafactory/soma v0.8.4
1d SUBMIT
Jens-Christian Fischer · Submitted @metafactory/soma v0.8.4
1d REVIEW
mellanon · Approved @metafactory/soma v0.8.5
1d SUBMIT
Jens-Christian Fischer · Submitted @metafactory/soma v0.8.5
1d PUBLISH
Jens-Christian Fischer · Uploaded bundle aba55daa
1d PUBLISH
Jens-Christian Fischer · Uploaded bundle 3cf3d57d
1d PUBLISH
Jens-Christian Fischer · Uploaded bundle cdcaa206
1d SUBMIT
Jens-Christian Fischer · Submitted @metafactory/soma v0.8.4
1d PUBLISH
Jens-Christian Fischer · Uploaded bundle f3bcdc3e
2d REVIEW
mellanon · Approved @metafactory/soma v0.8.1

Every blueprint is drafted, reviewed, and audited before it's shelved.

◇ 01 · IDENTITY
Publishers are people

Every publisher is a verified identity. No anonymous uploads, no ghost accounts. Five tiers (○ ◐ ● ◆ ★) make trust visible at a glance.

◇ 02 · SPONSORSHIP
New names are vouched for

A first blueprint from an unknown operator ships with a named sponsor who has read the code and put their reputation behind it.

◇ 03 · CAPABILITIES
Every power is declared

Filesystem, network, shell, secrets: each capability a blueprint needs is listed, justified, and audited before install.

◇ 04 · TAMPER EVIDENCE
What you install is what was shelved

Every release is content-addressed by SHA-256. If a tarball doesn't match the registry, arc refuses to install it.

◇ 05 · REGISTRY SIGNATURE
The fingerprint list is signed

Every release index is signed by metafactory. When arc fetches the index, it verifies the signature against a key it already knows. A compromised mirror can't slip a fingerprint into the list.

◇ 06 · PUBLISHER PROVENANCE
Proof of who built it

Each release carries a cryptographic attestation tied to the author's identity, recorded in a public transparency log. You can verify not just that metafactory approved it, but that a specific person built it.

READ THE FULL TRUST MODEL →