Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add sturlese/stigmergy --skill librariangit clone --depth 1 https://github.com/sturlese/stigmergyWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/sturlese/stigmergy/librarian)<a href="https://agentmods.dev/skills/sturlese/stigmergy/librarian"><img src="https://agentmods.dev/badge/skills/sturlese/stigmergy/librarian/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/sturlese/stigmergy/librarian"><img src="https://agentmods.dev/badge/skills/sturlese/stigmergy/librarian.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00016 | $0.02486 |
| Opus 5.5 | $0.00006 | $0.00994 |
| Sonnet 5.5 | $0.00003 | $0.00497 |
| Haiku 4.5 | $0.00002 | $0.00249 |
Grade A, and why
librarian scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 16d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
The source is not reproduced here
Licensed AGPL-3.0
The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 16d ago Changed · +74 lines bc96c834dc37
- 1mo ago Changed · -72 lines 9559f3336825
- 1mo ago Changed · +18 lines 99952bd046dc
- 1mo ago Changed · -14 lines · -2 tokens per session 08bedb63aee2
- 1mo ago Changed · +78 lines b34bf1b18579
- 1mo ago First seen · 128 lines · 18 tokens per session scan A b9dbd0162db7
librarian is a skill published in the GitHub repository sturlese/stigmergy (0 stars, last pushed 2d ago), licensed AGPL-3.0. It adds 16 tokens to every session and 2,486 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
kb-memory
Local-first agent memory and knowledge service (RAG) installed from PyPI. Use when a task needs to store or recall long-term user preferences, project decisions, facts, documents or web pages, when different projects need separate memories, or when the user mentions "kb memory", "kb", or a local MCP memory service.…
kb-log
A skill for recording important technical decisions and debugging lessons in a team knowledge base or a local ledger file.
kb-brief
A project-start briefing that searches a team's knowledge base for past pitfalls, decisions, recent changes, and people familiar with the work. It is intended for new tasks, issues, and bug fixes.
kb-wrap
A procedure for transferring recorded project decisions and lessons from a local ledger into a team knowledge base, then clearing the processed entries.
link-memory
Use after important user-approved decisions, when durable context should be proposed or reviewed, and for explicit Link memory lifecycle work: remember, recall, review, update, archive, restore, forget, or explain local memories through the CLI without requiring MCP.
link-retrieve
Use before answering work that may depend on user memory, project history, source-backed notes, or prior decisions; retrieve compact Link context through the CLI without loading the whole wiki or requiring MCP.