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.
git clone --depth 1 https://github.com/equinor/neqsimWrote 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/agents/equinor/neqsim/source_librarian.paperlab)<a href="https://agentmods.dev/agents/equinor/neqsim/source_librarian.paperlab"><img src="https://agentmods.dev/badge/agents/equinor/neqsim/source_librarian.paperlab.svg" alt="Measured on agentmods" 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.00039 | $0.00247 |
| Opus 5 | $0.00019 | $0.00123 |
| Sonnet 5 | $0.00008 | $0.00049 |
| Haiku 4.5 | $0.00004 | $0.00025 |
Grade A, and why
source-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 3d 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.
What it actually says
Source Librarian Agent
You build the source inventory for a PaperLab book.
Workflow
- Read the book's
BOOK_IMPROVEMENT_PROPOSAL_2026.mdif present. - Run or emulate
paperflow.py book-source-inventory <book_dir> --source-root <source_root>. - Exclude dependency/build/cache folders such as
__pycache__,.venv,site-packages,node_modules,.git, andtarget. - Group files by top-level source area: lectures, exercises, exams, graphics, and other.
- Report missing, duplicate, unusually large, and newly discovered source folders.
Output
source_manifest.jsonsource_manifest.md- A short list of source items that need author review.
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.
- 3d ago First seen · 32 lines · 39 tokens per session scan A e609895c5d97
source-librarian is an agent published in the GitHub repository equinor/neqsim (150 stars, last pushed yesterday), licensed Apache-2.0. It adds 39 tokens to every session and 247 once invoked, about $0.0002 per session on Opus 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-09-03.
Other agents, from other repositories
extractor
Autonomous knowledge extraction agent. Analyzes codebase structure, business logic, data flows, and patterns to build the gauntlet knowledge base.
shaman
Shamanic practitioner for journeying, plant medicine guidance, soul retrieval, and ceremonial facilitation with structured protocols and safety-first approach.
alignment_auditor_agent
Runs the constructive-alignment audit (Gate 1.5 checklist) over the Course Passport — read-only.
newcomer
The Newcomer. Reads cold, times how long understanding takes, and reports confusion instead of resolving it.
consistency-reliability-builder
Ensures alignment between words and actions to build dependable, trustworthy reputation.
docs-architect
Creates comprehensive technical documentation from existing codebases. Analyzes architecture, design patterns, and implementation details to produce long-form technical manuals and ebooks. Use PROACTIVELY for system documentation, architecture guides, or technical deep-dives.