Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/nel-neru/LibrAIumnpx agentmods add skills/nel-neru/libraium/source-command-improveWrote 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-improve)<a href="https://agentmods.dev/skills/nel-neru/libraium/source-command-improve"><img src="https://agentmods.dev/badge/skills/nel-neru/libraium/source-command-improve/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-improve"><img src="https://agentmods.dev/badge/skills/nel-neru/libraium/source-command-improve.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.00031 | $0.01166 |
| Opus 5.5 | $0.00012 | $0.00466 |
| Sonnet 5.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 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 — 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.
- 1mo ago 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 28d ago), licensed MIT. It adds 31 tokens to every session and 1,166 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
git-workflow
Git workflow patterns including branching strategies, commit conventions, merge vs rebase, conflict resolution, and collaborative development best practices for teams of all sizes.
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-commit
Git commit message generator that creates conventional commit messages based on code changes.
memorix-git-memory
Use when the task depends on commit history, what changed, when a fix shipped, or linking engineering evidence to reasoning memory.
git-workflow
Automate the complete Git development workflow — create feature branches with conventional naming, atomic commits with conventional commit messages, interactive rebase, squash merges, PR body generation from commit history, branch cleanup, and git worktree patterns. Use when user asks to create a branch, commit…
git-workflow
Follow this team's Git conventions for branching, commit messages, and pull requests.