Skip to main content

spec-agents-core (agent_fabric)

Domain-agnostic core for spec-driven pipelines and hierarchical agents. Components, pipelines and agents are declared in Markdown with YAML frontmatter (SKILL.md, AGENT.md, fabric.md); the frontmatter is a contract validated by Pydantic and the body is guidance injected into prompts on demand. LLMs plan, delegate, repair and interpret — they never compute: every result comes from deterministic Component.compute() code run by the PipelineExecutor.

Status: pre-release. Until the first PyPI release, install a wheel from the GitHub Releases or use uv sync --all-packages in a checkout; the pip install lines below are the PyPI names.

Names

PyPI distribution spec-agents-core
Import name agent_fabric
Directory in the monorepo packages/agent-fabric
Release tag / PR scope agent-fabric-vX.Y.Z / agent-fabric

The distribution is named spec-agents-core because the shorter names are taken on PyPI; the import name and the entry point do not change.

Install

pip install spec-agents-core                  # core: pydantic, numpy, pyyaml, rich (import name: agent_fabric)
pip install "spec-agents-core[tabular]"       # + pandas (dataframe artifact types)
pip install "spec-agents-core[all]"           # + PydanticAI, DSPy, CrewAI, LangChain adapters

Domain packs (statistics, lakehouse, coworker, text-pack) register themselves through the agent_fabric.domains entry point.

Use

agent-fabric catalog --skills path/to/skills     # list components and pipelines
agent-fabric agents path/to/config               # render and validate an agent tree
agent-fabric lint --agents path/to/config --strict
agent-fabric run path/to/config "task" --input name=file.txt
from agent_fabric import build_registry
from agent_fabric.agents import AgentFabric, AgentsConfig

fabric = AgentFabric(build_registry(discover=True), AgentsConfig.load("config"))
report = fabric.run("question", {"data": df}, session_id="s1")

Optional frameworks are imported lazily; models are referenced by LiteLLM alias only. See the repository docs for the architecture, the error model and how to add components, pipelines and agents.

Metadata

Release files for spec-agents-core 0.5.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for spec-agents-core 0.5.1
File Size Uploaded
spec_agents_core-0.5.1.tar.gz 101.9 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for spec-agents-core 0.5.1
File Interpreter ABI Platform
spec_agents_core-0.5.1-py3-none-any.whl Python 3 none any Details

Total release size: 219.4 kB

Release files / spec_agents_core-0.5.1.tar.gz

Download URL spec_agents_core-0.5.1.tar.gz
Size 101.9 kB
Tags Source
SHA-256 checksum
How to use checksums
6aef2815cb421ff357ca38f36c7b39fc2330f11cd32e1b3c1224cb12f37cf81c
BLAKE2b-256 checksum
How to use checksums
9331bd1392059eb74e6e958db45b85e97fca7984e96a4bd4847b68c22a90ec51
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 2, 2026.

Transparency log

Release files / spec_agents_core-0.5.1-py3-none-any.whl

Download URL spec_agents_core-0.5.1-py3-none-any.whl
Size 117.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
c7df5c5d003f73a8e51b9b373ee05258dcacee4b76cfd41e4a1b7687bff53ef6
BLAKE2b-256 checksum
How to use checksums
503551821c5aa34ccb1c18c32435509ab94bf3c0e19854bf293397a9e0cf5f48
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 2, 2026.

Transparency log

Release history Release notifications | RSS feed

0.8.0

2 release files

0.7.0

2 release files

0.6.0

2 release files

This release

0.5.1 This release

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page