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.
Install:
pip install spec-agents-core(PyPI); wheels and sdists are also attached to each GitHub Release (agent-fabric-vX.Y.Z).
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.6.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| spec_agents_core-0.6.0.tar.gz | 102.7 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| spec_agents_core-0.6.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 220.5 kB
Release files / spec_agents_core-0.6.0.tar.gz
| Download URL | spec_agents_core-0.6.0.tar.gz |
|---|---|
| Size | 102.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4f29ff80ef622a7c14162eb8c5d3e8d6defa06ab1c06f2d3c964fbd00a755a4a
|
|
BLAKE2b-256 checksum How to use checksums |
086ca3077ebc3f1df9bf6d15a86e7051929b716343eca47462b09f768a46caed
|
| 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 logRelease files / spec_agents_core-0.6.0-py3-none-any.whl
| Download URL | spec_agents_core-0.6.0-py3-none-any.whl |
|---|---|
| Size | 117.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f675c8260ccc47ccf04737037b10ff547cd5b2980dd30f86ea9f013c0f9e1b2e
|
|
BLAKE2b-256 checksum How to use checksums |
e86d2786e786ed15f2f055f97780142db06d00a8dc35cb1c08d9481a4a9ee94e
|
| 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