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 instructions/soumendrak/ragwatch/agents-mdgit clone --depth 1 https://github.com/soumendrak/ragwatchWrote 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/instructions/soumendrak/ragwatch/agents-md)<a href="https://agentmods.dev/instructions/soumendrak/ragwatch/agents-md"><img src="https://agentmods.dev/badge/instructions/soumendrak/ragwatch/agents-md.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 | $0.02930 | $0.02930 |
| Opus 5 | $0.01465 | $0.01465 |
| Sonnet 5 | $0.00586 | $0.00586 |
| Haiku 4.5 | $0.00293 | $0.00293 |
Grade A, and why
ragwatch AGENTS.md 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 4d 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 — 214 lines — stays where its author put it; the contents beside it link to each section on GitHub.
RAGWatch — AGENTS.md
Version: v0.3 (enterprise hardening + runtime wiring) Tagline: "Quality scores in your RAG traces — computed, not just recorded"
Project Overview
- Name: RAGWatch
- Purpose: OpenTelemetry-native RAG observability Python SDK with semantic quality scores
- Key Differentiator:
chunk_relevance_score+user.feedback_score— computed semantic quality - Instrumentation: Explicit decorators only (use OpenLLMetry for auto-instrumentation)
- RAG Types: Linear RAG (v0.1), multi-stage via composed decorators
- Efficiency: ~1-5 ms overhead per request
- Scope: SDK only. Users bring their own OTel backend.
- Install:
uv add ragwatch(recommended) orpip install ragwatch(core);uv add ragwatch --extra langgraphorpip install ragwatch[langgraph]
Architecture
Instrumentation Strategy
Explicit decorators only — no auto-instrumentation in v0.1.
| Layer | Instrumentation | Reason |
|---|---|---|
| LLM calls | None (use OpenLLMetry) | They do it better; compose via OTel |
| Embedding generation | Explicit | Query embedding stored for relevance score |
| Vector search / retrieval | Explicit | chunk_relevance_score computed here |
| User feedback | Explicit | record_feedback() is user-initiated |
| Agent nodes / workflows | Explicit | User decides span boundaries |
Linear RAG Stages
| Stage | Span Name | Key Attributes |
|---|---|---|
| Embedding | ragwatch.embedding.generate |
model.name, embedding.dimensions, duration_ms |
| Vector Search | ragwatch.retrieval.search |
top_k, chunks.returned, chunk.relevance_score |
| Response | ragwatch.response.emit |
response.length, user.feedback_score |
chunk_relevance_score Plumbing (single-process only)
embedding.pycomputes query embedding → stores in OTelContext(not baggage)context.pymanages thread-local storage for query embeddingretrieval.pyreads context → computes cosine similarity → setschunk.relevance_score- Supported dimensions: up to 512-dim
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.
- 4d ago First seen · 214 lines · 2,930 tokens per session scan A 1c41f6cfe5d2
ragwatch AGENTS.md is an instructions file published in the GitHub repository soumendrak/ragwatch (5 stars, last pushed 4mo ago), licensed MIT. It adds 2,930 tokens to every session, about $0.0146 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-31.
Other instructions, from other repositories
graphiti AGENTS.md
AGENTS.md instructions for getzep/graphiti, covering repository guidelines, project structure & module organization, build, test, and development commands, coding style & naming conventions and testing guidelines.
openstatus AGENTS.md
AGENTS.md instructions for openstatusHQ/openstatus, covering agents.md, verify your change, toolchain, architecture and tests.
clawmetry AGENTS.md
AGENTS.md instructions for vivekchand/clawmetry, covering agents.md — for ai coding agents, quick context, where new code goes (open-core split), the rules that bite and common tasks.
openstatus CLAUDE.md
Claude Code instructions for openstatusHQ/openstatus, covering claude.md and investigating production with polylane.
pdf-brain AGENTS.md
Instructions for joelhooks/pdf-brain, covering pdf-brain agent notes, libsql quirks, ai sdk pattern, key files and docs.
Elpis AGENTS.md
AGENTS.md instructions for MasihMoafi/Elpis, covering elpis agent map, start, context discipline, definition of done and evals first.