Alternatives
Products that do what LLMSlim does
Tool-aware context, contract-safe.
- 1
- 2PA
2016 · kadena.io
- 3
- 4
- 5
- 6
- 7OS
We’re building an open-source tool that makes it easy to expose secure, LLM-optimized APIs on top of your structured data—without manually designing endpoints or worrying about compliance. AI agents and LLM-powered applications need structured access to data, but traditional APIs and databases weren’t built with AI workloads in mind. Our tool automatically generates APIs that: - Filter out PII & sensitive data to comply with GDPR, CPRA, SOC 2, and other regulations. - Provide traceability & auditing, so AI apps aren’t black boxes, and security teams stay in control. - Optimize for AI…
2025 · github.com
- 8SD
2019 · github.com
- 9OS
2023 · github.com
- 10JA
May 2026 · github.com
- 11GB
Hey HN, We’re excited to share PySpur, an open-source tool that provides a graph-based interface for building, debugging, and evaluating LLM workflows. Why we built this: Before this, we built several LLM-powered applications that collectively served thousands of users. The biggest challenge we faced was ensuring reliability: making sure the workflows were robust enough to handle edge cases and deliver consistent results. In practice, achieving this reliability meant repeatedly: 1. Breaking down complex goals into simpler steps: Composing prompts, tool calls, parsing steps, and branching…
2024 · github.com
- 12CL
With the right technique, I was able to break the so-called secure models like Claude and OpenAI. So, I built an open-source tool to automate this and find security holes in any hosted model. I got claude-sonnet-4 to demonstrate the following harmful behavior: - steal data from downstream tool calls using sql injection, code injection and template injection attacks - install spyware or malware using prompt obfuscation to send data to a third-party server Try it yourself with this simple command: pip install compliant-llm && compliant-llm dashboard
2025 · github.com
- 13CA
2017 · clause.js.org
- 14LF
We built a no/low-code tool that lets you spin up MCPs from a single prompt. MCPs give LLMs access to tools, data, and actions—but they’re hard to build and deploy. Our tool abstracts that: describe what you want, and it auto-generates and hosts the necessary components. No UI flows, no manual chaining—just prompt and go. Examples: • Pull email, parse a DocSend, check Reddit, draft reply • Extract data from a niche site + send a Slack alert • Combine tools without writing glue code Live demo: https://www.youtube.com/watch?v=4uCiaQrgfoE Built over a weekend after getting…
2025 · generatemcp.com
- 15OS
Hi HN, Matvey, Ildar, Joey, and Dominik here. If you're building LLM agents that use tools, you're probably worried about prompt injection attacks that can hijack those tools. We were too, and found that solutions like prompt-based filtering or secondary "guard" LLMs can be unreliable. Our thesis is that agent security should be handled at the network level between the agent and the LLM, just like a traditional web application firewall. So we built Archestra Platform: an open-source gateway that acts as a secure proxy for your AI agents. It's designed to be a deterministic firewall against…
Oct 2025 · archestra.ai
- 16OB
2025 · github.com
- 17CS
We've been building with AI tools and noticed there wasn't a good way to manage MCP servers across a team or see what's actually flowing to LLM providers. Who's running what? Which tools are approved? What data is going where or whats shared on AI websites? So we built CyberCage (). What it does: MCP Management — Auto or manual discovery of MCP servers, with approval workflows. Manage allowed MCP servers org-wide (down to individual tools). Secure MCP catalog (integrates with GitHub's MCP Catalog). Operations — Manage allowed AI applications org-wide. Full audit logs (Splunk integration…
Dec 2025 · cybercage.io
- 18CM
Hey HN, I've been building AutoAgents, an AI agent framework in Rust. Today I'm sharing a feature I haven't seen done well elsewhere: composable middleware layers for LLM inference pipelines. The problem Every agent framework lets you swap LLM providers. Almost none of them give you a structured way to enforce safety, caching, or data sanitization in the inference path itself. You end up with guardrails as application-level if-statements, caching bolted on as a separate service, and PII handling as a "we'll add it later" TODO that never ships. This gets worse with local models. Cloud APIs…
Mar 2026 · github.com
- 19OS
Hello HN, I’ve been building AI agents lately and ran into a common "Context Bloat" problem. When an agent has 20+ skills, stuffing every system prompt, reference doc, and tool definition into a single request quickly hits token limits and degrades model performance (the "lost in the middle" problem). To solve this, I built OpenSkills, an open-source SDK that implements a Progressive Disclosure Architecture for agent skills. The Core Concept: Instead of loading everything upfront, OpenSkills splits a skill into three layers: Layer 1 (Metadata): Light-weight tags and triggers (always loaded…
Jan 2026
- 20CB
AI agents now have impressive reasoning capabilities. This raises an important question: how dangerous are these AI agents at identifying & exploiting web vulnerabilities? We created CVE-bench to find out (I'm one contributor of 16). To our knowledge CVE-bench is the first benchmark using real-world web vulnerabilities to evaluate AI agents' cyberattack capabilities. We included 40 CVEs from NIST's database, focusing on critical-severity vulnerability (CVSS > 9.0). To properly evaluate agents’ attacks, we built isolated environments with containerization and identified 8 common attack…
2025 · github.com
- 21MM
I built MCPlexor to solve a token waste problem I kept running into with MCP-based agents. The Problem: MCP (Model Context Protocol) is great for giving LLMs access to external tools. But if you connect multiple servers (GitHub, Linear, Postgres, Slack), you end up with 40-50k tokens of tool definitions injected into every request – before the agent even does anything. On a 200k context model, that's 25% gone. On smaller models, it's worse. And most runs only use 1-2 tools. The Solution: MCPlexor sits between your agent and your MCP servers. Instead of loading all tool definitions upfront:…
Feb 2026 · mcplexor.com
- 22BM
Today we released an open, Valkey-native context layer for AI agents as part of our packages at BetterDB (agent memory, semantic + multi-tier caching, typed retrieval) that run on a Valkey instance no matter where it is - no vendor lock-in. We even started provisioning Valkey instances starting today. Packages are shipped on npm and PyPi. Why we made it: BetterDB originally started as a monitoring and observability platform for Valkey, Redis and any RESP compatible db. This is still the core of the product, but in the process of building this, we kept seeing that one of the fastest-growing…
Jun 2026 · github.com
- 23FA
LLM agents rely on tool calls — but tool responses are huge. Gmail, CRMs, and APIs return bloated JSON LLMs choke on large responses You only need 2–3 fields, but frameworks give you zero control Toolflow is an AI-native framework to fix this: * Filter tool responses before they hit the LLM * Context modes: `minimal`, `full`, `custom`, or `ai` * Composable TypeScript tool registry GitHub: [https://github.com/dksingh1997/toolflow](https://github.com/dksingh1997/toolflow) Would love feedback — especially from those building with LLMs in production.
2025 · github.com
- 24LF
Hey HN, I built SWE-Kit, LLM toolkit (Function callable tools) which makes building agents specialised in coding like Devin very easy. I noticed a typical pattern while building local agents: creating & perfecting LLM tools to interact with system or codebase was the repeated and time-consuming. We created a layer that simplifies building agents that can interact with code, file system, git, shell and allows you to quickly solve for a wide variety of coding agent use cases. Aren’t there open coding agents already? Well, yes, but most folks would want to solve their specific use case like a…
2024 · swekit.dev
Ranked by how close each launch is in meaning, then by votes. Refine with a description →