AgentInvariant is a behavioral safety evaluator for tool-using AI agents. Agent workflows are probabilistic: two requests with the same meaning can produce materially different external actions. AgentInvariant uses metamorphic testing to determine whether critical operational behavior remains consistent across meaning-equivalent inputs. For each input variant, AgentInvariant starts a fresh OpenAI conversation and an isolated SQLite database. The target agent uses real tools to check coverage, retrieve authorization requirements, record business approval, and submit a synthetic prior-authorization request. AgentInvariant records the complete structured tool trace and evaluates it using deterministic Python invariants—not an LLM judge. It verifies that exactly one submission occurs and that matching coverage and business approval are successfully recorded before submission. The evaluator is exposed through a Streamable HTTP MCP server and invoked by a TrueForge agent using the `evaluate_agent` tool. Results include per-variant PASS or BLOCKED decisions, ordered traces, exact invariant violations, compliance rate, and the shortest failing counterexample. The demo compares an explicitly labeled unsafe negative control, which AgentInvariant correctly blocks, with a hardened candidate that follows the required workflow. All healthcare data is synthetic. This project is an administrative workflow reliability demonstration and is not clinical decision support.
Built at The Agent Harness Hackathon
AgentInvariant
AgentInvariant is a behavioral safety evaluator for tool-using AI agents. Agent workflows are probabilistic: two requests with the same meaning can produce materially different external actions. AgentInvariant uses metamorphic testing to determine whether critical operational behavior remains consistent across meaning-equivalent inputs. For each input variant, AgentInvariant starts a fresh OpenAI conversation and an isolated SQLite database. The target agent uses real tools to check coverage, retrieve authorization requirements, record business approval, and submit a synthetic prior-authorization request. AgentInvariant records the complete structured tool trace and evaluates it using deterministic Python invariants—not an LLM judge. It verifies that exactly one submission occurs and that matching coverage and business approval are successfully recorded before submission. The evaluator is exposed through a Streamable HTTP MCP server and invoked by a TrueForge agent using the `evaluate_agent` tool. Results include per-variant PASS or BLOCKED decisions, ordered traces, exact invariant violations, compliance rate, and the shortest failing counterexample. The demo compares an explicitly labeled unsafe negative control, which AgentInvariant correctly blocks, with a hardened candidate that follows the required workflow. All healthcare data is synthetic. This project is an administrative workflow reliability demonstration and is not clinical decision support.
TrueFoundryPython 3.12, OpenAI Responses API, GPT-4.1 Mini, Model Context Protocol (MCP), MCP Python SDK, Streamable HTTP, SQLiteKeep exploring what builders shipped.
Sports Whisperer
SportsWhisperer
With AI becoming centre stage - Content and Entertainment will be the king. Sport has the highest amount of spend as industry and creates massive economic drive, so we have built an All in One - Sports Whisperer for all major sports Crickets, NFL, Soccer, Basketball, Baseball, etc where the novice and experienced players can interact with the favorite games and players !!! More details captured - https://docs.google.com/presentation/d/1_q0SDTvutQP9kd2SLdDXYYkc-h9QVYwj0vdih1Cuqzc/edit?slide=id.gcb9a0b074_1_0#slide=id.gcb9a0b074_1_0
HackerSquad project
Robo Harness
Hardess for robo
sproutsource
harness profiler
# Harness Profiler Measures how **agent harness design choices** change the inference load of a coding agent, and turns the measurements into per-task rules. Everyone else benchmarks hardware with the harness held fixed. We hold the hardware fixed and vary the harness. Built on [TrueForge](https://trueforge.dev), TrueFoundry's open-source agent harness. ## Read this first - [`PROJECT.md`](PROJECT.md) — what we're building, why, and the architecture - [`TRACE_SCHEMA.md`](TRACE_SCHEMA.md) — the contract between the two halves ## Layout ``` collector/ teammate A — runs agents, writes traces analyzer/ teammate B — reads traces, produces metrics + report samples/ hand-made traces so the analyzer works before any real run tasks/ task cards + the broken-test repo under test traces/ output (gitignored) ``` The two halves meet **only** at `traces/*.jsonl`. Neither reads the other's code. ## Quick start git clone <this repo> && cd harness-profiler Teammate A: git checkout collector cd collector && npm install Teammate B: git checkout analyzer cd analyzer && npm install npm run analyze -- ../samples/*.jsonl ## Working with Codex / Claude Code Both read the repo-root brief automatically (`AGENTS.md` for Codex, `CLAUDE.md` for Claude Code; both point at `PROJECT.md`). Open the repo and state which half you own, e.g. > I'm teammate B. Build the parser and metrics layer in `analyzer/` against > `samples/`. Don't touch `collector/`.