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 agentmods add skills/nel-neru/libraium/source-command-format-syncnpx skills add nel-neru/LibrAIum --skill source-command-format-syncgit clone --depth 1 https://github.com/nel-neru/LibrAIumWhat 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 | $0.00025 | $0.00828 |
| Opus 5 | $0.00013 | $0.00414 |
| Sonnet 5 | $0.00005 | $0.00166 |
| Haiku 4.5 | $0.00003 | $0.00083 |
Grade A, and why
source-command-format-sync 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 yesterday.
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 — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
source-command-format-sync
Use this skill when the user asks to run the migrated source command format-sync.
Command Template
The LibrAIum data format is deliberately dual-implemented: the Rust core (desktop app) and the Node MCP server each parse, validate, and serialize the same files. After ANY change to the entry format, slugify, URL normalization, duplicate detection, or category master shape, run this synchronization procedure.
1. Identify what changed and mirror it
Walk this mapping and make the counterpart change on the other side:
| Concern | Rust | Node |
|---|---|---|
Frontmatter schema, field defaults (status: active, source: manual, stars: 0, optional-field omission) |
src-tauri/src/models.rs (EntryMeta) |
mcp-server/lib/store.js (parseEntry consumers, summarize defaults) |
Frontmatter split/parse/serialize (BOM handling, --- fences, body trimming, trailing newline) |
src-tauri/src/frontmatter.rs |
mcp-server/lib/store.js (splitFrontmatter, parseEntry, serializeEntry) |
slugify (allowed charset [a-z0-9-_.], / → -, lowercase, trim -) |
src-tauri/src/store.rs (slugify) |
mcp-server/lib/store.js (slugify) |
GitHub URL normalization (http/https/bare/git@ forms, .git, trailing /, /tree/...) |
src-tauri/src/store.rs (normalize_github_url) |
mcp-server/lib/store.js (normalizeGithubUrl) |
Duplicate detection (case-insensitive full_name) and entry id (<category>/<slug>) |
src-tauri/src/store.rs (find_duplicate, list_entries) |
mcp-server/lib/store.js (findDuplicate, listEntries, saveNewEntry) |
Both sides must accept, reject, and produce identical results. Where the change touches parsing, check the reject cases too (missing opening ---, unterminated frontmatter) — error behavior must match even if error text differs.
2. Add a fixture for the new shape
Add a fixture covering the new format shape to tests/fixtures/format/. Follow the naming pattern already used there (valid inputs that must round-trip, and invalid inputs both sides must reject). The conformance runner picks fixtures up automatically. Also extend the unit tests nearest the change (frontmatter::tests / store::tests in Rust) if the fixture alone can't express it.
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.
- yesterday First seen · 50 lines · 25 tokens per session scan A 8ee0588b3023
source-command-format-sync is a skill published in the GitHub repository nel-neru/LibrAIum (0 stars, last pushed 5d ago), licensed MIT. It adds 25 tokens to every session and 828 once invoked, about $0.0001 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-08-31.
Other skills, from other repositories
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.
okf-harness-bootstrap
This unified entrypoint routes setup and workspace maintenance without making the user choose a mode.
khaos-brain-open-ui
Open the local Khaos Brain desktop card browser for human review. Use when the user asks to open, show, view, inspect, or create a human-facing entry for the Khaos Brain UI, desktop app, card browser, or Windows shortcut. Do not use this for AI KB retrieval or feedback; use the predictive KB retrieval workflow for…
local-kb-retrieve
Retrieve relevant entries from the local predictive knowledge base as a lightweight preflight for repository work. Use route-first retrieval: infer the task direction, then search by domain path and cross-index before relying on flat keyword matching. In Codex, prefer a scout sidecar before non-trivial work and a…
kb-organization-maintenance
Run the repository-managed Khaos Brain organization maintenance cycle. Use only when a user or automation explicitly asks to inspect, review, or maintain a validated organization KB repository and this machine has opted into organization maintenance; this is the organization exchange cycle, not ordinary local KB Sleep.
kb-sleep-maintenance
Run the repository-managed automatic local maintenance cycle. Use only for explicit local maintenance or the scheduled KB Sleep automation, not ordinary retrieval or active-task write-back.