Check an agent’s test claims against local Claude Code transcripts and the git working tree. Nine rule-based checks identify gaps such as missing runs or failed tests, with timestamps and quoted evidence, without calling a model.
Check whether the tests the agent said passed actually ran. Reads the Claude Code session transcript and git state locally, then reports each gap with a timestamp and the quoted line. No model calls, nothing leaves the machine.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
Audit the current session's claims against its own record. If the agent said the tests pass, this checks that a test run actually happened, that it did not fail, and that no expected value was quietly rewritten to match a bug.
npx --yes @jinhyuk9714/red-handed@latest audit in the project directoryNo model is called. The same session gives the same verdict every time.
Audit this session. Did the tests I was told about actually run?
The skill runs:
npx --yes @jinhyuk9714/red-handed@latest audit
Useful variations:
npx --yes @jinhyuk9714/red-handed@latest audit --all # every session for this project
npx --yes @jinhyuk9714/red-handed@latest stats # counts across the whole machine
npx --yes @jinhyuk9714/red-handed@latest audit --lang ko # report in Korean
User: "Before I merge this, check whether the tests really ran."
Output:
CAUGHT claim-vs-fail
14:02:31 "All 33 tests pass."
14:01:58 npx vitest run … exit 1, 2 failed
The last run before the claim failed. Nothing ran after it.
A clean session prints nothing to accuse. That is the common case.
CAUGHT needs two things at once: the session shows it happening and the code still shows it nowSUSPICIOUS means the pattern is there but the motive is not establishedSUSPICIOUSNo reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Handle ActiveCampaign contact and marketing tasks through Rube MCP, a connection for agent tools. Find or create contacts, manage tags and subscriptions, enroll contacts in existing automated workflows, and create follow-up tasks.
Research competitors’ live Meta and Google ads to identify opening hooks, offers, calls to action, and landing pages. Receive a sourced creative brief and up to three test ideas adapted to your product.
Add website or app tracking, then use command-line tools to review traffic, signups, drop-off, and returning users across projects. Run A/B tests, which compare alternative headlines or buttons, and inspect results to guide changes.
Establish rules for when an AI agent should recall past context and save lasting decisions, corrections, preferences, and failures. Works with Markdown files or memory services, preserving decision history and surfacing conflicting records.
Audit local AI coding-agent sessions with agenttrace to identify spending, token use, tool failures, and operational problems. Produce readable or structured reports and define pass-or-fail thresholds for automated continuous integration checks.
Audit saved agent sessions for access to private files and evidence that secret values entered an agent's context. Get findings without displaying secrets, identify keys needing rotation, and inspect Claude Code or Codex sessions in a local report.