Agent docs
What a coding agent needs to build a plugin on Library Hub.
Every page here is Markdown at its own address. The same files ship inside the API package, matched to the version you install. People reading along want the Developer docs.
Give your agent this
Paste these lines into your plugin's AGENTS.md. Agents read that file every session; without the pointer, most never look inside node_modules.
## Library Hub
Before writing code that calls Library Hub, read
node_modules/@insurgently/library-hub-api/AGENTS.md.
It matches the installed version; prefer it to what you remember.The files
Short pages, each about one thing. An agent reads AGENTS.md first and follows its links.
AGENTS.mdSix rules for a plugin that calls Library Hub, and where everything else is.agents/AGENTS.md- ChangelogChanges to Library Hub's API, by version.agents/CHANGELOG.md
README.mdTypes and a few small helpers for reading books from Library Hub in your own Obsidian plugin.agents/README.mdllms.txtThe index: one line per file.llms-full.txtis all of them in one file.agents/llms.txt
Where they live
One set of files, written in the repo, copied to two places at release. Read the package copy when you can: it is the version you have.
- In the API package
node_modules/@insurgently/library-hub-api/:AGENTS.md,CHANGELOG.mdandREADME.md. Matched to the installed version, and there offline.- On this site
- The latest release. Every page has a
.mdtwin at the same address, which an agent also gets by asking for Markdown, and a Copy as Markdown button.llms.txtandllms-full.txtsit beside them. - In the repo
- Where the files are written. The
AGENTS.mdat the repo's root is for agents working on Library Hub itself;api/AGENTS.mdis the one for callers.
How they stay current
- Each page here starts with the date it was built and its source in the repo.
- The pages are the package's own files, copied at release, so the site and the package can't disagree.