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 nel-neru/LibrAIum --skill source-command-utilizegit clone --depth 1 https://github.com/nel-neru/LibrAIumWrote 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/nel-neru/libraium/source-command-utilize)<a href="https://agentmods.dev/skills/nel-neru/libraium/source-command-utilize"><img src="https://agentmods.dev/badge/skills/nel-neru/libraium/source-command-utilize/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/nel-neru/libraium/source-command-utilize"><img src="https://agentmods.dev/badge/skills/nel-neru/libraium/source-command-utilize.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.00027 | $0.00790 |
| Opus 5.5 | $0.00011 | $0.00316 |
| Sonnet 5.5 | $0.00005 | $0.00158 |
| Haiku 4.5 | $0.00003 | $0.00079 |
Grade A, and why
source-command-utilize 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
source-command-utilize
Use this skill when the user asks to run the migrated source command utilize.
Command Template
Run exactly one iteration of LibrAIum's utilization loop. Where /improve hardens what exists, /utilize builds the mechanisms that make the library earn its keep: commands, agents, skills, scripts, MCP tools, docs. One iteration = one deliverable, proven useful, verified, committed.
P — Plan
Read .Codex/utilization-backlog.md and pick the highest-priority pending item that fits one focused session. If the top item is too big, split it and take the first piece. State what you picked and the utilization payoff you expect.
If the backlog is missing or Pending is empty: run a fresh ideation pass over these personas — new-project developer, maintainer/curator, Codex integration, batch automation (user-invoked only), publisher, decision support — and refill Pending with concrete, single-commit-sized items before picking. If ideation surfaces nothing that genuinely clears the value bar, write ## LOOP COMPLETE at the top of the backlog and stop honestly.
D — Do
Build the deliverable. Hard constraints (override anything the backlog says):
- FORBIDDEN future phases: X/Twitter auto-collection, semantic search / embeddings, project bootstrap generation (scaffolding). Lexical techniques only.
- Fully local & private. GitHub API (
gh) only inside explicitly user-invoked actions — never a daemon, never a scheduled network call. - No new runtime dependencies unless the item is impossible without one; justify in the commit message.
- Data-format changes touch BOTH implementations (
src-tauri/src/⇔mcp-server/lib/store.js) plus a conformance fixture — see/format-sync. - New entries follow the
entry-authoringskill; UI changes followDESIGN.md. - Match existing idiom; if commands/scripts/structure changed, update AGENTS.md and README in the same commit.
C — Check
Two gates, both required:
- The acceptance check from the backlog item — actually exercise the deliverable (run the command, invoke the script on real data, query the MCP tool) and show the observable result. A tool nobody ran is not done.
bash scripts/verify-all.sh— all stages green. Fix root causes, not tests. For non-trivial diffs, havelibraium-reviewerreview before committing.
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.
- 1mo ago First seen · 47 lines · 27 tokens per session scan A 850ac2e45c51
source-command-utilize is a skill published in the GitHub repository nel-neru/LibrAIum (0 stars, last pushed 28d ago), licensed MIT. It adds 27 tokens to every session and 790 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
vault
Search, read, write, and manage files in the Kept conversation vault. Use when the user asks about past conversations, wants to save notes, needs to find specific content, or wants to organize their vault.
shodh-memory
Persistent memory system for AI agents. Use this skill to remember context across conversations, recall relevant information, and build long-term knowledge. Activate when you need to store decisions, learnings, errors, or context that should persist beyond the current session.
enzyme-sqlite-source
Connect an unfamiliar SQLite database to Enzyme without changing the source data. Inspect the database, decide which query columns represent identity, people, time, content, and folders, show real examples for approval, save a workspace program in the Enzyme language, and verify init and refresh. Use for email…
enzyme
Use Enzyme in an already activated Obsidian, Markdown, or Hermes workspace for working-memory retrieval, source-grounded exploration, search by keyword and meaning, runtime note-writing, and refresh. If the workspace is not initialized, follow the first-time setup section before normal retrieval.
paparats-search
Use when answering a question about code in the user's indexed repositories — where something is implemented, how a flow works, who calls a function, or what a change would affect. Explains when to use Paparats semantic search and when a text search is the better tool.
alice-project-memory
Use Alice as the project-scoped memory and continuity layer. Load before build or review work, and whenever a decision or constraint is worth keeping.