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-improvenpx skills add nel-neru/LibrAIum --skill source-command-improvegit 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.00031 | $0.01166 |
| Opus 5 | $0.00015 | $0.00583 |
| Sonnet 5 | $0.00006 | $0.00233 |
| Haiku 4.5 | $0.00003 | $0.00117 |
Grade A, and why
source-command-improve 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
source-command-improve
Use this skill when the user asks to run the migrated source command improve.
Command Template
Run exactly one iteration of LibrAIum's improvement loop. One iteration = one focused improvement, verified and committed. Do not batch multiple unrelated improvements into a single iteration.
1. Load state
Read .Codex/improvement-backlog.md.
If it does not exist (first iteration): seed it by auditing the repo along these dimensions, then pick the top item and continue. Write concrete, single-commit-sized items — not vague themes.
- Robustness (Rust) —
unwrap()/expect()/panic paths insrc-tauri/src/, unhandled I/O errors, edge cases in store/search/github/gitops (empty data dir, malformed entry mid-library, concurrent refresh, git repo in weird states) - Robustness (MCP server) — input validation gaps, unhelpful error messages, behavior on corrupt/missing data files
- Test coverage — untested branches in Rust modules; the MCP server has only the smoke test — targeted unit tests for
lib/store.js/lib/suggest.js - Dual-format parity — adversarial edge cases (unicode slugs, CRLF, empty body, frontmatter-like body content, huge tags) → new fixtures in
tests/fixtures/format/proving both sides agree - Frontend (Svelte 5) — empty/loading/error states, race conditions on rapid navigation, keyboard access, feedback on slow network ops
- DX / docs — README accuracy, script failure messages, AGENTS.md drift
- CI — speed, cache hit rate, flakiness
Backlog format:
# Improvement Backlog
## Pending (ordered: highest value first)
- [ ] P1 <one-line item> — <why it matters, 1 sentence>
## Done
- [x] <item> — <commit hash> (<date>)
## Rejected
- <item> — <why not worth doing>
Priority order: P1 correctness & data-safety bugs → P2 missing tests for existing behavior → P3 error handling & user-facing failure messages → P4 dual-format hardening (new fixtures) → P5 docs/DX/CI polish.
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 · 85 lines · 31 tokens per session scan A d90e62bbb8ab
source-command-improve is a skill published in the GitHub repository nel-neru/LibrAIum (0 stars, last pushed 5d ago), licensed MIT. It adds 31 tokens to every session and 1,166 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-08-31.
Other skills, from other repositories
run-work
Execute a work unit end-to-end: sequence tasks by dependency, implement, test between tasks, commit, and track progress. Use to deliver a complete feature in one session. Invoked as /agiflow:run-work . Uses getworkunit, listtasks, updatetask, getworkunitprogress.
git-workflow
安全处理 Git 状态检查、提交信息、commit、分支、push、PR 和 rebase。用于用户要求检查改动、生成或创建提交、管理分支、推送、发起 PR 或整理历史时；严格区分每个动作的授权，并保护工作树中已有和无关的修改。.
git-commit
Git commit message generator that creates conventional commit messages based on code changes.
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.
version-control
Manage Git repositories and collaborative workflows — branching strategies, commit hygiene, conflict resolution, pull requests, hooks, and .gitignore management. Use when the user requests version control or provides relevant inputs for this workflow.
git-commits-and-prs
Load BEFORE creating a git commit or a GitHub pull request. Step-by-step protocol for drafting commit messages, staging safely, amend rules, and gh pr create choreography.