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/takagoto/rag-learning-academy/code-reviewnpx skills add TakaGoto/rag-learning-academy --skill code-reviewgit clone --depth 1 https://github.com/TakaGoto/rag-learning-academyWrote 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/takagoto/rag-learning-academy/code-review)<a href="https://agentmods.dev/skills/takagoto/rag-learning-academy/code-review"><img src="https://agentmods.dev/badge/skills/takagoto/rag-learning-academy/code-review.svg" alt="Measured on agentmods" 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.00011 | $0.01148 |
| Opus 5 | $0.00005 | $0.00574 |
| Sonnet 5 | $0.00002 | $0.00230 |
| Haiku 4.5 | $0.00001 | $0.00115 |
Grade A, and why
code-review 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 6d 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Review: Expert Feedback on Your RAG Implementation
Review the learner's RAG code with the eye of an experienced RAG engineer, providing actionable feedback that improves correctness, performance, and robustness.
Language awareness: See
.claude/LANGUAGE_AWARENESS.md.
Step 1: Identify the Code to Review
Welcome! Let's take a close look at your RAG code together.
First, determine what code is available for review:
-
If the user specifies a file or directory (e.g.,
/code-review projects/my-rag/retriever), review that. -
If no argument is given, check for a learner profile at
progress/learner-profile.mdand look for code insrc/andprojects/. -
If no RAG code exists anywhere in
projects/orsrc/(and no file was specified), guide them warmly:"It looks like you haven't written any RAG code yet — that's the perfect place to start! Run
/buildto create your first RAG component, and then come back here for expert feedback on what you've built. I'll be ready to help you level it up!"Stop here — do not continue to Step 2.
-
If code is found and multiple files exist, ask which component they want reviewed, or offer to review the full pipeline.
Step 2: Read and Understand the Code
Before giving feedback, thoroughly understand what the code does:
- Read all relevant files
- Trace the data flow from input to output
- Identify the overall architecture and design pattern
- Note which libraries and models are being used
Step 3: Review Dimensions
Evaluate the code across these dimensions, providing specific feedback for each:
Correctness
- Does the code produce correct results?
- Are there logic errors, off-by-one errors, or incorrect API usage?
- Are edge cases handled (empty input, very large documents, special characters)?
- Are embeddings and vector operations mathematically correct?
RAG-Specific Best Practices
- Chunk size and overlap: Are they appropriate for the document type and use case?
- Embedding dimensions: Do all components agree on the embedding dimension?
- Prompt engineering: Is the RAG prompt well-structured? Does it instruct the model to use only the provided context?
- Context window management: Could the context exceed the model's token limit?
- Metadata handling: Is useful metadata preserved through the pipeline?
- Error handling: What happens when the retriever returns no results? When the API is down?
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.
- 6d ago First seen · 118 lines · 11 tokens per session scan A 187ca5039a0a
code-review is a skill published in the GitHub repository TakaGoto/rag-learning-academy (18 stars, last pushed 5mo ago), licensed MIT. It adds 11 tokens to every session and 1,148 once invoked, about $0.0001 per session on Opus 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-08-30.
Other skills, from other repositories
embeddings
Vector embeddings with HNSW indexing, sql.js persistence, and hyperbolic support. 75x faster with agentic-flow integration. Use when: semantic search, pattern matching, similarity queries, knowledge retrieval. Skip when: exact text matching, simple lookups, no semantic understanding needed.
agent-platform-rag-engine-management
Manage and query Agent Platform RAG Engine Corpora and retrieve grounded contexts using the Google GenAI SDK. Use when listing RAG corpora or files, inspecting a corpus, retrieving contexts, or generating content grounded in a RAG corpus. Do not use for standard database queries (use SQL/Spanner skills), Google…
llm-app-patterns
Production-ready patterns for building LLM applications. Covers RAG pipelines, agent architectures, prompt IDEs, and LLMOps monitoring. Use when designing AI applications, implementing RAG, building agents, or setting up LLM observability.
9router-embeddings
Generate vector embeddings via 9Router /v1/embeddings using OpenAI / Gemini / Mistral / Voyage / Nvidia / GitHub embedding models for RAG, semantic search, similarity. Use when the user wants embeddings, vectors, RAG, semantic search, or to embed text.
azure-search-documents-dotnet
Azure AI Search SDK for .NET (Azure.Search.Documents). Use for building search applications with full-text, vector, semantic, and hybrid search. Covers SearchClient (queries, document CRUD), SearchIndexClient (index management), and SearchIndexerClient (indexers, skillsets). Triggers: "Azure Search .NET"…
similarity-search-patterns
Implement efficient similarity search with vector databases. Use when building semantic search, implementing nearest neighbor queries, or optimizing retrieval performance.