|
| 1 | +# Launch Plan for llm-sentry |
| 2 | + |
| 3 | +## Hacker News Post (Show HN) |
| 4 | + |
| 5 | +**Title:** Show HN: LLM Sentry – 12 diagnostic engines for AI pipelines, zero dependencies, no API keys |
| 6 | + |
| 7 | +**Text:** |
| 8 | + |
| 9 | +I built llm-sentry because I was tired of debugging LLM apps by staring at RAGAS scores. |
| 10 | + |
| 11 | +RAGAS tells you your RAG pipeline scores 0.6. Now what? Is it retrieval? Generation? Context assembly? Is your agent stuck in a loop? Did your last prompt change break something? RAGAS won't tell you. Neither will DeepEval, TruLens, or Promptfoo. |
| 12 | + |
| 13 | +llm-sentry runs 12 specialized diagnostic engines across your entire AI stack in a single scan: |
| 14 | + |
| 15 | +- RAG Pathology: Classifies failures into 4 types (retrieval miss, poor grounding, noisy context, healthy) — tells you exactly WHERE your RAG pipeline breaks |
| 16 | +- Chain Probe: CASCADE fault analysis for multi-step pipelines — finds the root cause, not just the symptom |
| 17 | +- Agent Patrol: Detects 5 agent pathologies (futile cycles, oscillation, stall, drift, abandonment) |
| 18 | +- CoT Coherence: Catches reasoning gaps, contradictions, and unsupported conclusions |
| 19 | +- Prompt Brittleness: Stress-tests prompts under paraphrase — finds fragile prompts before production does |
| 20 | +- Plus 7 more: injection detection, mutation testing, model swap parity, output drift, contracts, context recall |
| 21 | + |
| 22 | +Key differentiators: |
| 23 | + |
| 24 | +1. Zero dependencies. No OpenAI key required. No LLM calls to evaluate LLMs. |
| 25 | +2. Works completely offline. |
| 26 | +3. One install, one API: `pip install llm-sentry` gives you everything. |
| 27 | +4. Diagnosis, not just scores. Every check tells you what's wrong AND what to fix. |
| 28 | + |
| 29 | +```python |
| 30 | +import llmguardrail as lg |
| 31 | + |
| 32 | +report = lg.scan( |
| 33 | + pipeline_name="my_app", |
| 34 | + checks=["rag", "coherence", "agents"], |
| 35 | + rag_queries=[("What is the return policy?", [("Returns within 30 days", 0.95)], "Returns within 30 days")], |
| 36 | +) |
| 37 | +print(report.summary()) |
| 38 | +# Pipeline: my_app |
| 39 | +# Health: HEALTHY (92%) |
| 40 | +# Checks: 3 run |
| 41 | +``` |
| 42 | + |
| 43 | +GitHub: https://github.com/Rowusuduah/llm-sentry |
| 44 | +PyPI: https://pypi.org/project/llm-sentry/ |
| 45 | +License: MIT |
| 46 | + |
| 47 | +I'd love feedback on what checks you wish existed, or what's missing from your current AI debugging workflow. |
| 48 | + |
| 49 | +--- |
| 50 | + |
| 51 | +## Reddit r/MachineLearning Post |
| 52 | + |
| 53 | +**Title:** [P] I built a zero-dependency diagnostic toolkit for LLM pipelines — 12 engines, no API keys, works offline |
| 54 | + |
| 55 | +**Body:** |
| 56 | + |
| 57 | +Every LLM eval tool I've tried (RAGAS, DeepEval, TruLens) gives me a score. A score doesn't help when production is broken at 2 AM. |
| 58 | + |
| 59 | +I built llm-sentry — a unified platform with 12 diagnostic engines that tell you WHAT is wrong and WHERE in your pipeline: |
| 60 | + |
| 61 | +**What it catches:** |
| 62 | +- RAG failures: Is it retrieval, generation, or noisy context? (Four Soils classification) |
| 63 | +- Agent loops: Futile cycles, oscillation, stall, drift, abandonment |
| 64 | +- Reasoning breaks: CoT gaps, contradictions, unsupported conclusions |
| 65 | +- Prompt fragility: Which prompts break under paraphrase? |
| 66 | +- Pipeline faults: Root cause analysis across multi-step chains |
| 67 | +- Output drift: Schema violations, behavioral changes after model swaps |
| 68 | + |
| 69 | +**Why it's different:** |
| 70 | +- No API keys. No OpenAI calls. Zero external dependencies. |
| 71 | +- Works offline. Runs in CI/CD. |
| 72 | +- Diagnoses, not just scores. Every check gives you a fix. |
| 73 | + |
| 74 | +```bash |
| 75 | +pip install llm-sentry |
| 76 | +``` |
| 77 | + |
| 78 | +```python |
| 79 | +import llmguardrail as lg |
| 80 | +report = lg.scan(pipeline_name="prod", checks=["rag", "coherence", "agents"]) |
| 81 | +print(report.summary()) |
| 82 | +``` |
| 83 | + |
| 84 | +GitHub: https://github.com/Rowusuduah/llm-sentry |
| 85 | + |
| 86 | +Looking for feedback — what diagnostic would you add? What's the hardest part of debugging your LLM apps? |
| 87 | + |
| 88 | +--- |
| 89 | + |
| 90 | +## Reddit r/Python Post |
| 91 | + |
| 92 | +**Title:** [Project] llm-sentry: Unified diagnostic platform for LLM pipelines — 12 engines, pure Python, zero deps |
| 93 | + |
| 94 | +**Body:** |
| 95 | + |
| 96 | +I built llm-sentry, a pure-Python toolkit for diagnosing failures in LLM-powered applications. |
| 97 | + |
| 98 | +The problem: You have an LLM app in production. Something breaks. Existing tools (RAGAS, DeepEval) give you a score but don't tell you what's wrong. |
| 99 | + |
| 100 | +llm-sentry gives you 12 diagnostic engines under one API: |
| 101 | + |
| 102 | +| Engine | What it catches | |
| 103 | +|--------|----------------| |
| 104 | +| RAG Pathology | Retrieval miss vs. grounding failure vs. context noise | |
| 105 | +| Chain Probe | Root cause in multi-step pipelines | |
| 106 | +| Agent Patrol | 5 agent pathologies (loops, stall, drift, etc.) | |
| 107 | +| CoT Coherence | Reasoning gaps and contradictions | |
| 108 | +| Prompt Brittleness | Prompts that break under paraphrase | |
| 109 | +| + 7 more | Injection, mutation, model parity, drift, contracts, context | |
| 110 | + |
| 111 | +Design decisions: |
| 112 | +- Zero dependencies (pure Python, stdlib only) |
| 113 | +- No LLM calls needed to evaluate LLMs |
| 114 | +- Every engine has a SQLite store built in for history/trends |
| 115 | +- Unified `scan()` API runs any combination of checks |
| 116 | +- Extensible: register your own custom checks |
| 117 | + |
| 118 | +```bash |
| 119 | +pip install llm-sentry |
| 120 | +``` |
| 121 | + |
| 122 | +Built with hatchling, tested with pytest (37+ tests), MIT licensed. |
| 123 | + |
| 124 | +GitHub: https://github.com/Rowusuduah/llm-sentry |
| 125 | +PyPI: https://pypi.org/project/llm-sentry/ |
| 126 | + |
| 127 | +--- |
| 128 | + |
| 129 | +## Twitter/X Thread |
| 130 | + |
| 131 | +**Tweet 1:** |
| 132 | +I just shipped llm-sentry — 12 diagnostic engines for LLM pipelines, zero dependencies, no API keys. |
| 133 | + |
| 134 | +RAGAS gives you a score. llm-sentry tells you what's broken and how to fix it. |
| 135 | + |
| 136 | +pip install llm-sentry |
| 137 | + |
| 138 | +🧵 What's inside: |
| 139 | + |
| 140 | +**Tweet 2:** |
| 141 | +1/ RAG Pathology — "Four Soils" classification |
| 142 | + |
| 143 | +Your RAG scores 0.6. But WHY? |
| 144 | + |
| 145 | +- PATH: Retrieval missed entirely → fix embeddings |
| 146 | +- ROCKY: Good retrieval, bad generation → fix grounding prompt |
| 147 | +- THORNY: Noisy context → add reranking |
| 148 | +- GOOD: Working as intended |
| 149 | + |
| 150 | +**Tweet 3:** |
| 151 | +2/ Agent Patrol — detects 5 agent pathologies |
| 152 | + |
| 153 | +Your agent is "thinking" for 5 minutes. Is it: |
| 154 | +- Futile cycling (same actions over and over)? |
| 155 | +- Oscillating between two states? |
| 156 | +- Stalled on a subtask? |
| 157 | +- Drifted from the original goal? |
| 158 | +- Abandoned the task entirely? |
| 159 | + |
| 160 | +Now you know. |
| 161 | + |
| 162 | +**Tweet 4:** |
| 163 | +3/ Chain Probe — CASCADE fault analysis |
| 164 | + |
| 165 | +Multi-step pipeline fails at step 5. But the REAL problem was step 2. |
| 166 | + |
| 167 | +Chain Probe traces the cascade: ROOT_CAUSE → INHERITED → INHERITED → INHERITED → symptom. |
| 168 | + |
| 169 | +Fix the root, fix everything. |
| 170 | + |
| 171 | +**Tweet 5:** |
| 172 | +The key insight: you don't need GPT-4 to evaluate GPT-4. |
| 173 | + |
| 174 | +Every engine in llm-sentry works with zero LLM calls. Pure algorithmic diagnosis. Works offline. Runs in CI/CD. |
| 175 | + |
| 176 | +GitHub: https://github.com/Rowusuduah/llm-sentry |
| 177 | +PyPI: https://pypi.org/project/llm-sentry/ |
| 178 | + |
| 179 | +MIT licensed. Feedback welcome. |
0 commit comments