The Octopus Library
+2026-04-07 — 6 packages adopted
+ + +The Octopus is a librarian that speaks npm. Name a package; it fetches the docs into ~/.napkin/docs/ where napkin can find them — searchable alongside vault notes, available when reading or writing code. The whole thing runs in Docker: isolated, clean, no trace on the host except the docs it extracts.
This is the library's current inventory. The irony is deliberate: open-props is catalogued here, and its CSS variables style this entire page — including this sentence.
A tool for writing better scripts. Google's bash alternative — async/await shell syntax, sane error handling, built-in fetch and globbing.
+ +Used in ~/os/ — beat.sh, build-digest, and the octopus explore scripts themselves.
Supercharged CSS variables. Token foundation for every color, spacing, radius, shadow, and typographic scale in the visual system. Zero JS required.
+ +Foundation of agentic-semantic-web. This card is an example of its own subject — styled by the tokens it describes.
+A markdown parser built for speed. Converts .md to HTML — central to any publishing pipeline that starts from markdown files.
+ +Garden publishing, napkin's render pipeline, and any tool that needs markdown → HTML in the build chain.
+Model Context Protocol inspector. Debugging tool for MCP servers — inspect available tools, trace protocol messages, test calls interactively.
+ +MCP ecosystem tooling — for building or debugging MCP server and client integrations in the A-team stack.
+MCP server for filesystem access. Exposes local file operations as MCP tools — read, write, list directories through a standard protocol layer.
+ +A-team infrastructure — gives any MCP-capable agent access to the local filesystem through a standard interface.
+AI-native system for spec-driven development. Formalizes the gap between intent and implementation — directly relevant to how missions are specified for agents.
+ +Commons mission architecture and the A-team workflow — how work gets formally specified before it gets executed.
++ +
octopus explore <npm-pkg> → octopus read <name> → octopus adopt <name>
+ +To add a package: drop a name in vault#30 or leave it in ~/inbox/. One session to explore, one commit to adopt. The library grows by request or by need — whichever comes first.