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.
git clone --depth 1 https://github.com/latestaiagents/agent-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/commands/latestaiagents/agent-skills/eval-rag)<a href="https://agentmods.dev/commands/latestaiagents/agent-skills/eval-rag"><img src="https://agentmods.dev/badge/commands/latestaiagents/agent-skills/eval-rag/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/commands/latestaiagents/agent-skills/eval-rag"><img src="https://agentmods.dev/badge/commands/latestaiagents/agent-skills/eval-rag.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.00008 | $0.00471 |
| Opus 5.5 | $0.00003 | $0.00188 |
| Sonnet 5.5 | $0.00002 | $0.00094 |
| Haiku 4.5 | $0.00001 | $0.00047 |
Grade A, and why
eval-rag 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.
What it actually says
/eval-rag
Run comprehensive evaluation on your RAG pipeline.
What I Need
Tell me:
- Do you have a test dataset? (queries + expected answers)
- What metrics matter most? (accuracy, latency, cost)
- Current retrieval/generation setup?
Evaluation Steps
Step 1: Test Dataset
I'll help you create or validate your test dataset:
- Query variety (simple, complex, edge cases)
- Ground truth answers
- Relevant document mappings
Step 2: Retrieval Metrics
Measure retrieval quality:
- Recall@k - Are relevant docs in top-k?
- MRR - How high do relevant docs rank?
- NDCG - Quality of ranking order
Step 3: Generation Metrics
Assess answer quality:
- Faithfulness - Is answer grounded in context?
- Relevance - Does answer address the question?
- Correctness - Is answer factually correct?
Step 4: System Metrics
Track operational performance:
- Latency - p50, p95, p99 response times
- Cost - Per-query LLM/embedding costs
- Throughput - Queries per second
Quick Evaluation
from ragas import evaluate
from ragas.metrics import faithfulness, answer_relevancy
# Prepare data
eval_data = {
"question": [...],
"answer": [...],
"contexts": [...],
"ground_truth": [...]
}
# Run evaluation
results = evaluate(Dataset.from_dict(eval_data),
metrics=[faithfulness, answer_relevancy])
print(results)
Benchmark Targets
| Metric | Good | Great |
|---|---|---|
| Recall@5 | >0.7 | >0.85 |
| MRR | >0.6 | >0.75 |
| Faithfulness | >3.5/5 | >4.0/5 |
| Relevance | >3.5/5 | >4.0/5 |
| Latency p95 | <2s | <500ms |
Output
I'll provide:
- Metric scores with comparisons
- Failure case analysis
- Specific improvement recommendations
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 · 82 lines · 8 tokens per session scan A 82d45fa4c3fe
eval-rag is a command published in the GitHub repository latestaiagents/agent-skills (5 stars, last pushed 6mo ago), licensed MIT. It adds 8 tokens to every session and 471 once invoked, about $0.0000 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-03.
Other commands, from other repositories
dataset
Manage dataset manifests for data that is too large or unsuitable to store directly in the wiki. The wiki becomes the index/interface; the data stays external.
ai
Invoke the AI/LLM Application Engineer for RAG, agents, prompt engineering, evals, tool use, and LLM guardrails.
fdk-refactor
Reduce function complexity in a Freshworks app to meet cyclomatic complexity ≤ 7 per function. Extracts helper functions, simplifies conditionals, and preserves behavior while improving code quality.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.