gut-check

A review step for checking decisions and factual claims before acting on them. The available details do not explain its exact checking method.

In plain words
What is it for?
Use it before committing to an important decision or stating that something is fixed, tested, found, or understood.
Why use it?
It helps catch conclusions based only on memory, an unchecked assumption, or an incomplete handoff.

Plugin for Claude Code

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.

Claude Code
/plugin marketplace add technicalpickles/pickled-claude-plugins
agentmods
npx agentmods add plugins/technicalpickles/pickled-claude-plugins/gut-check
Clone the repo
git clone --depth 1 https://github.com/technicalpickles/pickled-claude-plugins

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Security

Grade A, and why

gut-check scanned grade A with 0 findings 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.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/gut-check/.claude-plugin/plugin.json · 11 lines

What it actually says

{
  "name": "gut-check",
  "description": "Ground before you act: catch decisions and factual claims made from a thin basis",
  "author": {
    "name": "Josh Nichols",
    "email": "[email protected]"
  },
  "repository": "https://github.com/technicalpickles/pickled-claude-plugins",
  "license": "MIT"
}
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 · 11 lines scan A 58ffddacf6e6

Subscribe to this mod's changes

gut-check is a plugin published in the GitHub repository technicalpickles/pickled-claude-plugins (10 stars, last pushed 5d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other plugins, from other repositories

qiushi-skill

Qiushi Skill: methodology skills for AI agents guided by seeking truth from facts, with Claude Code, Cursor, OpenClaw, Codex, OpenCode, and Hermes guidance.

HughYau/qiushi-skill · not measured

kiln

Multi-model software creation pipeline. A conversation becomes running, tested software — an interactive brainstorm, then an autonomous build: GPT-5.6 writes the code, Claude shapes the plans and interfaces, and each family inspects the work of the other.

Fredasterehub/kiln · not measured

kit

Spec-driven Claude Code workflow with verification pipeline. Hooks, slash commands, and verification subagents.

dwarvesf/dwarves-kit · not measured

ticket-flow

Beads-backed ticket workflow for Claude Code: spec → pickup → implement → finish behind verdict and merge gates, orchestrated by /flow (--local with resume, --parallel, --serial/--loop unattended queue runner), each ticket in its own git worktree. Five visible commands; the phase skills are model-invoked.

keefar/ticket-flow · not measured

superpowers-graph

The Superpowers software-development methodology executed as a guarded state machine: 21 typed nodes, 96 total exit guards, 9 bounded retry loops, durable run state that survives compaction, and a ledger recording every step that could not run.

RonMizrahi/superpowers-graph · not measured

atelier

Agent-orchestration plugin: a lead reviews a plan, gates on user approval, and routes tasks to specialist agents by capability.

tunahanaliozturk/atelier · not measured