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 skills add OneWave-AI/claude-skills --skill jev-auditgit clone --depth 1 https://github.com/OneWave-AI/claude-skillsWrote 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/onewave-ai/claude-skills/jev-audit)<a href="https://agentmods.dev/skills/onewave-ai/claude-skills/jev-audit"><img src="https://agentmods.dev/badge/skills/onewave-ai/claude-skills/jev-audit/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/onewave-ai/claude-skills/jev-audit"><img src="https://agentmods.dev/badge/skills/onewave-ai/claude-skills/jev-audit.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.00089 | $0.01053 |
| Opus 5.5 | $0.00036 | $0.00421 |
| Sonnet 5.5 | $0.00018 | $0.00211 |
| Haiku 4.5 | $0.00009 | $0.00105 |
Grade A, and why
jev-audit 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 25d 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Inference-cost audit
Most production LLM calls return a label, not prose — a route, a score, a yes/no, a category. Those calls pay for autoregressive generation they do not use. This audit finds them and prices the swap.
Deliverable: a ranked table of candidates with measured deltas. Sellable as a OneWave
engagement; same shape as marketing-brain — a repeatable audit run per client.
1. Find the candidates
Search for LLM calls, then filter to the ones whose output is a label:
grep -rnE "messages\.create|chat\.completions|generateText|\.invoke\(|anthropic\.|openai\." \
--include=*.{ts,tsx,js,py} . | grep -v node_modules
A call is a candidate when all of these hold:
- the prompt asks for one of a known, finite set of answers (≤255)
- the caller parses the response — JSON.parse, a regex, an enum lookup,
.trim() - nothing downstream shows a human the model's reasoning
- it runs often, or a user waits on it
Strong signals in the prompt text: "respond with only", "return JSON", "classify", "choose one of", "rate from 1 to", "answer yes or no", "do not explain".
Disqualifiers: the output is shown to a user, is used as content, needs a citation or justification, or the answer set is open-ended.
2. Measure what it costs today
Do not estimate. Instrument:
- calls/day — from logs or a counter, not a guess
- p50 and p95 latency — p95 is what users feel
- tokens in/out per call → current $/1k calls at the provider's list price
- is anything blocked on it — a user, a page render, an agent's next step
3. Price the swap
Benchmark against a labelled set from that call's real traffic (see jev-eval). Never
project from a vendor benchmark.
Reference numbers, measured on real records, 4 questions per record:
| latency | cost/1k | accuracy | |
|---|---|---|---|
| Jev hosted | 399 ms | $0.023 | matched Claude on a 15-record set |
| Von local | 174 ms | $0.00 | matched only with well-written criteria |
| Claude Haiku 4.5 | 2,322 ms | ~$0.55 | baseline |
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.
- 25d ago First seen · 99 lines · 89 tokens per session scan A 96373e3f023c
jev-audit is a skill published in the GitHub repository OneWave-AI/claude-skills (349 stars, last pushed 15d ago), licensed MIT. It adds 89 tokens to every session and 1,053 once invoked, about $0.0004 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-09-22.
Other skills, from other repositories
seo-aeo-geo
Optimize content and site structure for AI-driven search experiences including AI overviews, large language model citations, generative answer engines, and AI assistants. Use this skill whenever the user wants to optimize for AI search, get cited by language models, appear in AI overviews, build llms.txt, structure…
automl-hyperparameter-optimization
Best practices for AutoML and hyperparameter search with Optuna, Ray Tune, and PyCaret, covering search-space design, validation splits, and leakage prevention. Use when tuning model hyperparameters, setting up a pruned or distributed hyperparameter search, designing a nested validation scheme, or evaluating whether…
google-adk
Best practices for building AI agents with Google's Agent Development Kit (ADK) in Python, covering agent design, tools, sessions, memory, artifacts, evaluation, and deployment. Use when building LLM agents or multi-agent systems with ADK, defining ADK tools, wiring up sessions/state/memory, working with ADK…
pyspark-etl
Best practices for building performant, testable PySpark ETL pipelines with Spark SQL and Apache Iceberg. Use when writing or reviewing PySpark jobs, designing joins and window functions, working with map/array higher-order functions, or building idempotent cumulative/snapshot table merges.
anthropic-claude-development
Expert guidance for Anthropic Claude API development including Messages API, tool use, prompt engineering, and building production applications with Claude models.
openai-api-development
Expert guidance for OpenAI API development including GPT models, Assistants API, function calling, embeddings, and best practices for production applications.