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/elnora-ai/elnora-cli/elnora-adminnpx skills add Elnora-AI/elnora-cli --skill elnora-admingit clone --depth 1 https://github.com/Elnora-AI/elnora-cliWhat 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.00154 | $0.02632 |
| Opus 5 | $0.00077 | $0.01316 |
| Sonnet 5 | $0.00031 | $0.00526 |
| Haiku 4.5 | $0.00015 | $0.00263 |
Grade B, and why
elnora-admin scanned grade B with 2 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 3d 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.
Downloads and executes remote codemediumSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
- CLI: `curl -fsSL https://cli.elnora.ai/install.sh | bash` (macOS/Linux) Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- CLI: `curl -fsSL https://cli.elnora.ai/install.sh | bash` (macOS/Linux) This is a copy
100% identical to elnora-admin — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 358 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Elnora Admin & Diagnostics
Authentication, API key management, account settings, health checks, audit logs, feedback, and shell completions.
Tool Access
Elnora is available via two methods. Use whichever is configured.
Option A — CLI via Bash (preferred)
Run commands via your Bash/Shell tool as elnora <group> <action> .... Verify with elnora --version. CLI uses ~5× fewer tokens than MCP.
Option B — MCP tools (when CLI isn't installed)
Look for tools prefixed mcp__elnora__ in your available tools. Call them with structured parameters (camelCase — e.g. projectId, not project-id). See the "MCP Tool Names" table below for the mapping.
If neither is available, tell the user to install one:
- CLI:
curl -fsSL https://cli.elnora.ai/install.sh | bash(macOS/Linux) orirm https://cli.elnora.ai/install.ps1 | iex(Windows) - MCP:
claude mcp add elnora --transport http --scope user https://mcp.elnora.ai/mcpthen/mcpto authenticate.
Never fabricate tool names. Valid commands are in the Commands section; their MCP equivalents are in the MCP Tool Names table.
Invocation
CLI="elnora"
Authentication
Login
$CLI --compact auth login --api-key <KEY>
$CLI --compact auth login --api-key <KEY> --profile university
--api-key is required — there is no interactive prompt. Keys must start with elnora_live_ and be 20+ characters. Saves to ~/.elnora/profiles.toml.
Response: {"profile":"default","verified":true,"configPath":"/Users/<you>/.elnora/profiles.toml"}
Check Auth Status
$CLI --compact auth status
# -> {"profile":"default","authenticated":true,"projectCount":N}
Logout
$CLI --compact auth logout
$CLI --compact auth logout --all
Without --all, removes the current profile. With --all, removes all saved profiles from profiles.toml.
List Profiles
$CLI --compact auth profiles
# -> {"profiles":[{"name":"default","apiKey":"elnora_live_...abcd"}]}
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.
- 3d ago First seen · 358 lines · 154 tokens per session scan B 1f558b96e914
elnora-admin is a skill published in the GitHub repository Elnora-AI/elnora-cli (4 stars, last pushed 7d ago), licensed Apache-2.0. It adds 154 tokens to every session and 2,632 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it B with 2 findings (downloads and executes remote code, makes network calls). It is 100% identical to elnora-admin, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…