@passioncode-ai/fabric-agent-adapter weekly downloads statistics
By passioncode-ai · npm · Claude Code
Create Fabric-compatible agents, run them as always-alive local services with dashboards (fabric-service/0.1), and adapt existing projects to the Fabric Agent Contract. This package is the installer CLI.
@passioncode-ai/fabric-agent-adapter has 2,596 recorded weekly downloads on npm.
About @passioncode-ai/fabric-agent-adapter
Fabric Agent Adapter
Fabric Agent Adapter makes any agent Fabric-compatible. Fabric is PassionCode.ai's product, the CEO AI agent: you talk to Fabric, and it chooses, binds and runs the agents that do the work. This adapter is how an agent becomes one Fabric can bind — four Agent Skills, Python and Node reference kits and a live conformance probe for the Fabric Agent Contract. It also works on its own: the skills, kits and probe need no Fabric install.
The skills are adapting-projects-to-fabric, creating-fabric-agents,
building-fabric-services and working-with-fabric.
working-with-fabric is for the other side: a coding agent (Claude Code, Codex, Kimi Code, Kilo, Hermes) opened in
a terminal that works in a project through Fabric. It finds Fabric (hub.json, its pid), has the machine's
lifecycle broker start it when it is down, registers fabric-mcp once with no secret, calls fabric_whoami
first, reads the project board (com.status, com.list, com.read_ack only what was read) and asks other
Projects only through com.submit, asks who is working on what and claims its task before it starts
(fabric_work_list, fabric_work_claim, Fabric 0.4.0), links tasks to backlog rows instead of copying them, and
releases at the end (fabric_work_release). scripts/fabric_session.py status prints where Fabric stands and one
next action:
python3 plugins/fabric-agent-adapter/skills/working-with-fabric/scripts/fabric_session.py status
In Claude Code the plugin adds four session hooks: SessionStart (at startup and /clear, never on compact or
resume) puts that preamble into the session when the MCP server fabric is registered and Fabric runs; when Fabric
is down it adds one line (skip fabric_whoami, start Fabric through the broker if the task needs it), and only in a
project that uses Fabric; Stop records each turn's facts (HEAD, files changed, lines added and removed, never content)
and the board's unread count; UserPromptSubmit adds one line only when that count rose; SessionEnd releases what the
session left claimed. Stop, UserPromptSubmit and SessionEnd act only when the running Fabric advertises
session-hooks/1. All are silent in a session Fabric launched, never block the session, read no token and always
exit 0. fabric_session.py watch-mail waits for board mail under a background watcher, and install-host-hooks --host codex|kimi|hermes|opencode|openclaw|pi installs each host's native context bridge (dry run unless --apply).
Codex receives structured SessionStart JSON; Hermes, OpenCode, OpenClaw and Pi use native plugin APIs.
See the native host matrix
for activation, reload and verification limits. The
hooks reference lists what
they need from Fabric; the board reference
is the board-first workflow.
building-fabric-services makes an agent a long-lived local service with a dashboard
that is always alive, runs as one copy, keeps its state through a reinstall and appears
in Fabric Dashboards by itself — the fabric-service/0.1 extension. It also makes an online agent
or dashboard — an https origin on a platform — a Fabric service (the remote placement, DEC-0019): the same
four routes behind the token, a __Host- session cookie, and one descriptor on the operator's computer;
scripts/sample-remote-service.mjs is the complete example. It ships Python and
Node reference kits (scripts/fabric_service.py, scripts/fabric-service.mjs), a
complete scripts/sample_service.py, and scripts/check_service.py, a live probe. A service that answers
requests other Projects post to its Project on Fabric's project board uses the board responder
(scripts/fabric_hub.py and scripts/fabric_board.py, Node fabric-hub.mjs and fabric-board.mjs): the
board.respond grant, enroll, claim, accept the exact digest, complete, a checkpoint before every step, and restarts
that reconcile or take accepted work back by a transfer (the board reference):
python3 plugins/fabric-agent-adapter/skills/building-fabric-services/scripts/check_service.py example-agent
```…
Description from the npm listing.
- fabric
- agent
- compatibility
- mcp
- a2a
- local-runner
- provider
- conformance
- claude-code
- skill
- local-service
- dashboard
- launchd
README badge
Show your rank in a README or on your website. The badge updates automatically.
Charts
Images: 30d · 1y · all time · 1600×900 dark
Adoption over time
7/30/90-day growth
Ranking history
Listing placement
Listing placement
Filled points are observed values; hollow points come from Internet Archive snapshots of the listing page. Dashed segments span periods with no observations — values between points are not interpolated.
Each band is one page of 20. Weekly downloads on a linear scale. Placement is projected from weekly downloads, so it can differ from the marketplace's own sort order. Hover a dot to see the listing.
Recent observations
Full history (1)Similar npm Claude Code plugins
All 20 @passioncode-ai/fabric-agent-adapter alternativesData source
Weekly downloads (trailing 7 complete days) come from the official npm downloads API. Downloads include CI and mirrors and are not equivalent to installs or users. npm publishes no ratings.
Listing: https://www.npmjs.com/package/@passioncode-ai/fabric-agent-adapter. First seen Oct 20, 2026; last successful collection Oct 20, 2026. See the methodology.