omni-usage-logs
Skill0 starsChanged 3 months agoMITView on GitHub
Access detailed call logs and usage analytics. Filter by provider, model, time range, status, and cost. Export logs and aggregate token usage across all connections.
- Reads credentials
- Sends data out
3 other projects use a version of this, 3 of them edited.
Adopted by
Most recently taken up by
- MMACABRE/SKILLSedited, first seen Nov 8, 2026
- cheaper-inference/OmniRouteedited, first seen Oct 25, 2026
- diegosouzapw/OmniRouteedited, first seen Oct 22, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 3
- cheaper-inference/OmniRoute★ 86k45% same
- diegosouzapw/OmniRoute★ 86k45% same
- MMACABRE/SKILLS★ 151% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository49 other files it gives its agents.
- AGENTS.mdAGENTS.md
- app_backup/AGENTS.mdAGENTS.md
- app_backup/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- cli-a2aSkill
- cli-backup-syncSkill
- cli-batchesSkill
- cli-chatSkill
- cli-compressionSkill
- cli-contextsSkill
- cli-cost-usageSkill
- cli-evalSkill
- cli-healthSkill
- cli-keysSkill
- cli-mcpSkill
- cli-modelsSkill
- cli-plugins-skillsSkill
- cli-policy-auditSkill
- cli-providersSkill
- cli-resilienceSkill
- cli-routingSkill
- cli-serveSkill
- cli-setupSkill
- cli-skill-collectorSkill
- cli-tunnelSkill
- config-codex-cliSkill
- nerve-inferenceSkill
- nerve-mcpSkill
- omni-agents-a2aSkill
- omni-api-keysSkill
- omni-authSkill
- omni-budgetSkill
- omni-cacheSkill
- omni-cli-toolsSkill
- omni-combos-routingSkill
- omni-compressionSkill
- omni-context-rtkSkill
- omni-db-backupsSkill
- omni-github-skillsSkill
- omni-modelsSkill
- omni-providersSkill
- omni-proxiesSkill
- omni-resilienceSkill
- omni-settingsSkill
- omni-sync-cloudSkill
- omni-tunnelsSkill
- omni-version-managerSkill
- omni-webhooksSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 0 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 13
All requests require a valid Bearer token or session cookie.
- Very specific: line 121
Only successful (status = 200) calls with a non-null cache column are counted.
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
<!-- generated by src/lib/agentSkills/generator.ts; manual edits will be overwritten -->Overview
Access detailed call logs and usage analytics. Filter by provider, model, time range, status, and cost. Export logs and aggregate token usage across all connections.
Authentication
All requests require a valid Bearer token or session cookie. Obtain a token via POST /api/auth/login or configure REQUIRE_API_KEY=false for local development.
Endpoints
GET /api/usage/analytics
Get usage analytics
curl https://localhost:20128/api/usage/analytics \
-H "Authorization: Bearer $NERVE_TOKEN"GET /api/usage/call-logs
Get call logs
curl https://localhost:20128/api/usage/call-logs \
-H "Authorization: Bearer $NERVE_TOKEN"GET /api/usage/call-logs/{id}
Get a specific call log
curl https://localhost:20128/api/usage/call-logs/{id} \
-H "Authorization: Bearer $NERVE_TOKEN"GET /api/usage/{connectionId}
Get usage for a specific connection
curl https://localhost:20128/api/usage/{connectionId} \
-H "Authorization: Bearer $NERVE_TOKEN"GET /api/usage/history
Get usage history
curl https://localhost:20128/api/usage/history \
-H "Authorization: Bearer $NERVE_TOKEN"GET /api/usage/logs
Get usage logs
curl https://localhost:20128/api/usage/logs \
-H "Authorization: Bearer $NERVE_TOKEN"GET /api/usage/proxy-logs
Get proxy logs
curl https://localhost:20128/api/usage/proxy-logs \
-H "Authorization: Bearer $NERVE_TOKEN"GET /api/usage/request-logs
Get request logs
curl https://localhost:20128/api/usage/request-logs \
-H "Authorization: Bearer $NERVE_TOKEN"GET /api/usage/budget
Get usage budget status
Returns current budget limits and consumption.
curl https://localhost:20128/api/usage/budget \
-H "Authorization: Bearer $NERVE_TOKEN"POST /api/usage/budget
Configure usage budget
Set or update budget limits for usage tracking.
curl -X POST https://localhost:20128/api/usage/budget \
-H "Authorization: Bearer $NERVE_TOKEN"
-H "Content-Type: application/json" \
-d '{}'GET /api/usage/cache-health
Get prompt-cache health summary
Summarizes the write/read cache ratio from call_logs for a time window:
distribution (p50/p90/p99/max of cache-write tokens), warm/cold/rewrite/uncached
call counts, the "heavy write" outlier share (10x the window median, floored at
1024 tokens — Anthropic's cache-creation minimum), and a per-model breakdown.
Only successful (status = 200) calls with a non-null cache column are counted.
curl https://localhost:20128/api/usage/cache-health \
-H "Authorization: Bearer $NERVE_TOKEN"GET /api/usage/model-latency-stats
Get per-model/provider latency statistics
Aggregates usage_history rows into per-(provider, model) latency stats (avg/p50/p95/p99, std-dev, TTFT, tokens/sec) over a rolling window. Falls back from successful-only to all-sample rows when the successful count is below minSamples.
curl https://localhost:20128/api/usage/model-latency-stats \
-H "Authorization: Bearer $NERVE_TOKEN"Payloads
See the full OpenAPI specification at GET /api/openapi/spec or docs/openapi.yaml for detailed request/response schemas.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

