Qfs
- Updated July 27, 2026
- qmu/qfs
qfs is a Rust CLI and embedded agent skill that exposes every backend through one pipe-SQL grammar so agents can DESCRIBE, PREVIEW, and COMMIT operations uniformly across services.
About
qfs is a Claude Code marketplace plugin bundling a Rust binary and an embedded agent skill for a unified pipe-SQL control plane. Agents learn one small grammar to query mail, drive, object storage, GitHub, Slack, SQL, and git through filesystem-shaped mounts with a safe PREVIEW-before-COMMIT workflow. Reach for it when agents must orchestrate many external services without mastering separate vendor SDKs.
- One pipe-SQL grammar for every backend
- DESCRIBE, PREVIEW, COMMIT agent loop
- Rust CLI, daemon, and embedded skill
- Closed core with open driver registries
Qfs by the numbers
- Data as of Jul 28, 2026 (Skillselion catalog sync)
/plugin marketplace add qmu/qfsAdd your badge
Show developers this marketplace is listed on Skillselion. Paste this into your README.
| Last updated | July 27, 2026 |
|---|---|
| Repository | qmu/qfs ↗ |
How can my agent interact with mail, GitHub, Slack, S3, and SQL without learning a different SDK for each service?
Queries mail, drive, GitHub, Slack, SQL, and more through one pipe-SQL grammar for agents.
Who is it for?
Developers building agent automations who want one grammar and one operating procedure across many external service backends.
Skip if: Simple apps that talk to a single database and never need cross-service agent orchestration.
What you get
Uniform query plans preview side-effect-free, then commit irreversible effects explicitly with policy-gated credentials stored per connection.
Plugins in this marketplace
1 plugin - install individually after you add the marketplace.
Recommended Marketplaces
FAQ
What is the agent operating procedure?
DESCRIBE the node, write a pipe-SQL statement, PREVIEW the plan, then COMMIT only when the effect is intended — identical across every backend.
How are credentials handled?
Run Qfs connection add with QFS_PASSPHRASE set; secrets are envelope-encrypted in the SQLite project DB and never appear inline in configs or logs.