ragtime debugging.instructions.md

A troubleshooting guide for the RAGtime application, including its API, containers, logs, and PostgreSQL database. RAG is a system that retrieves stored information to help generate answers.

In plain words
What is it for?
Checking health endpoints, viewing service logs, inspecting database tables, and examining saved prompt-debug records for conversations or background tasks.
Why use it?
It starts diagnosis with service health and readiness, helping distinguish startup, indexing, logging, and database problems.

Instructions file for GitHub Copilot

Install

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.

agentmods
npx agentmods add instructions/mattv8/ragtime/debugging
Clone the repo
git clone --depth 1 https://github.com/mattv8/ragtime

Made for: GitHub Copilot.

Per session 1,084 This file is loaded in full into every session.
When invoked 1,084 The same file — it is already loaded in full.
Security scan A 1 finding. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.01084 $0.01084
Opus 5 $0.00542 $0.00542
Sonnet 5 $0.00217 $0.00217
Haiku 4.5 $0.00108 $0.00108

Measured 2d ago against content hash b3be1061542e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

ragtime debugging.instructions.md scanned grade A with 1 finding 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 2d 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -s http://localhost:8000/health | jq .
.github/instructions/debugging.instructions.md · 108 lines

How it starts

The opening of the file, as written. The whole thing — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Debugging

Start With Runtime Health

# API readiness + index loading status
curl -s http://localhost:8000/health | jq .

# Service logs
docker logs -f ragtime-dev
docker logs -f ragtime-db-dev

If /health shows status=initializing, check for startup failures in ragtime/main.py lifecycle (DB connect, rag.initialize(), index recovery/cleanup).

Database Access (Prisma/Postgres)

docker exec -i ragtime-db-dev bash -c \
  'PGPASSWORD="${POSTGRES_PASSWORD}" psql -U "${POSTGRES_USER}" -d "${POSTGRES_DB}" -c "YOUR_QUERY"'

Useful tables: users, sessions, ldap_config, conversations, chat_tasks, index_jobs, index_metadata, index_configs, tool_configs, app_settings.

Prompt debug table (DEBUG mode only): provider_prompt_debug_records.

# Latest prompt-debug rows for one conversation
docker exec -i ragtime-db-dev bash -c \
  'PGPASSWORD="${POSTGRES_PASSWORD}" psql -U "${POSTGRES_USER}" -d "${POSTGRES_DB}" \
   -c "select provider,model,mode,request_kind,created_at from provider_prompt_debug_records where conversation_id = '\''<conversation_id>'\'' order by created_at desc limit 20;"'

# Prompt-debug rows for a specific background task
docker exec -i ragtime-db-dev bash -c \
  'PGPASSWORD="${POSTGRES_PASSWORD}" psql -U "${POSTGRES_USER}" -d "${POSTGRES_DB}" \
   -c "select provider,model,request_kind,created_at from provider_prompt_debug_records where chat_task_id = '\''<task_id>'\'' order by created_at asc;"'

# Compare userspace vs chat prompt payloads (prompt additions + reminders)
docker exec -i ragtime-db-dev bash -c \
  'PGPASSWORD="${POSTGRES_PASSWORD}" psql -U "${POSTGRES_USER}" -d "${POSTGRES_DB}" \
   -c "select mode,left(turn_reminders,120) as reminders,left(prompt_additions,120) as additions,created_at from provider_prompt_debug_records where conversation_id = '\''<conversation_id>'\'' order by created_at desc limit 20;"'

Auth + Session Troubleshooting

# Detect cookie/security config mismatches
curl -s http://localhost:8000/auth/status | jq .

# Login and capture ragtime_session cookie value
TOKEN=$(docker exec ragtime-dev bash -lc 'curl -s -c - -X POST http://localhost:8000/auth/login \
  -H "Content-Type: application/json" \
  -d "{\"username\":\"$LOCAL_ADMIN_USER\",\"password\":\"$LOCAL_ADMIN_PASSWORD\"}" \
  | awk "/ragtime_session/ {print \\$NF}"')

# Authenticated admin endpoint smoke test
curl -s http://localhost:8000/indexes/jobs -H "Cookie: ragtime_session=$TOKEN" | jq .

Read the full file on GitHub · 108 lines

Changes

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.

  1. 2d ago First seen · 108 lines · 1,084 tokens per session scan A b3be1061542e

Subscribe to this mod's changes

ragtime debugging.instructions.md is an instructions file published in the GitHub repository mattv8/ragtime (33 stars, last pushed 5d ago), licensed MIT. It adds 1,084 tokens to every session, about $0.0054 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other instructions, from other repositories

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,182 tokens

buildNext

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 6,785 tokens

next.js AGENTS.md

Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens

spec-kit AGENTS.md

Instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,040 tokens

langchain AGENTS.md

Instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,345 tokens