A command for researching a GitHub repository and adding it as a curated entry to the LibrAIum library. GitHub is a site where developers publish and maintain code projects.

Use it when adding a new GitHub project to the library, including checking its URL, metadata, duplicates, and entry details.

It removes the need to manually collect project details and helps prevent duplicate entries or notes that are not supported by the repository.

add-entry — Command by nel-neru

Install

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.

agentmods

npx agentmods add commands/nel-neru/libraium/add-entry

Clone the repo

git clone --depth 1 https://github.com/nel-neru/LibrAIum

Made for: Claude Code.

Per session 20 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,211 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 1 finding. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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	$0.00020	$0.01211
Opus 5	$0.00010	$0.00606
Sonnet 5	$0.00004	$0.00242
Haiku 4.5	$0.00002	$0.00121

Measured yesterday against content hash a1e26abe83ff, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

add-entry scanned grade A with 1 finding 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -s https://api.github.com/repos/<owner>/<repo>

.claude/commands/add-entry.md · 61 lines

How it starts

The opening of the file, as written. The whole thing — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Add a new curated entry to the LibrAIum library for: $ARGUMENTS

Follow this workflow in order. If the entry-authoring skill is available, load it — it is the authoritative house style; the essentials are repeated below.

1. Normalize the URL and check for duplicates

Derive owner/repo from the input. Accepted URL shapes and normalization rules are implemented in mcp-server/lib/store.js (normalizeGithubUrl): strip protocol, trailing /, .git, and any /tree/... suffix. The canonical form stored in github_url is https://github.com/<owner>/<repo>.

Check for an existing entry (duplicate detection compares lowercased full_name, so search case-insensitively):

grep -ril "^full_name: owner/repo" data/entries/

or reuse the real implementation:

node -e 'import("./mcp-server/lib/store.js").then(s => console.log(s.findDuplicate("data", "owner/repo")))'

If a duplicate exists, stop: show the user the existing entry and ask whether they want to update it instead.

2. Research the repo

Fetch real metadata from the GitHub API — prefer gh when available, otherwise plain HTTPS:
```
gh api repos/<owner>/<repo>        # or:
curl -s https://api.github.com/repos/<owner>/<repo>
```
Take stargazers_count → stars, language → language, pushed_at (date part, YYYY-MM-DD) → last_github_push, and archived (true ⇒ status: archived).
The response's full_name is authoritative — a renamed repo 301-redirects and the API returns the NEW name. If it differs from what you derived in step 1: use it for full_name, rebuild github_url as https://github.com/<full_name>, and re-run the step-1 duplicate check under the new name (an entry may already be shelved there). This mirrors guard_redirected_duplicate in both code add paths.
WebFetch the repository's README (https://github.com/<owner>/<repo>) to understand what it actually does, how mature it is, and what it pairs with. Look for gotchas in the docs (limits, platform caveats, migration notes).
If the network is unavailable: ask the user for stars/language, or omit the optional fields — never invent numbers or dates.

Read the full file on GitHub · 61 lines

Changes

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 · 61 lines · 20 tokens per session scan A a1e26abe83ff

Subscribe to this mod's changes

add-entry is a command published in the GitHub repository nel-neru/LibrAIum (0 stars, last pushed 5d ago), licensed MIT. It adds 20 tokens to every session and 1,211 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Research awesome-list claude-code knowledge-management local-first mcp mcp-server

add-entry

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Makes network callslowCapability

How it starts

1. Normalize the URL and check for duplicates

2. Research the repo

What this file has done since we first saw it

Other commands, from other repositories

implement-issue

review

blz

cli

docs

reset_project