interrogate SKILL.md skillA

interrogate from iap/pstack-hermes is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned

mdr add iap/pstack-hermes/interrogate@git:20261006.f7c5841

Pins git:20261006.f7c5841 in mdr.lock. Pin the fingerprint instead.

Audit grade: A, 17 of 17 checks passed
Kind: SKILL.md skill
Repository: iap/pstack-hermes
Path: skills/interrogate/SKILL.md
Versions recorded: 1
Latest version: git:20261006.f7c5841, committed Oct 6, 2026
Size: 5,107 bytes
Repository stars: 30
License: a license file GitHub does not identify

Use for "interrogate", "adversarial review", "multi-model review", "challenge this", "stress test this code", "find blind spots", or "tear this apart". Multiple LLM reviewers challenge changes from independent angles.

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# Interrogate

Spawn one reviewer per configured model to adversarially review code changes. Each model gets the same prompt and rubric. The adversarial signal comes from model diversity, not assigned personas.

The deliverable is a synthesized verdict. Do NOT auto-apply changes.

## Step 1, Determine Scope

Identify what to review from context:

- If the user points at specific files or a diff, use that
- If on a feature branch, run `git diff main...HEAD` (or the appropriate base branch) for the full changeset
- If the user's message references recent work, gather the relevant files

Package the diff (or file contents) plus any surrounding context files the reviewers need to understand the code.

## Step 2, State the Intent

Before spawning reviewers, state the intent explicitly. Derive this from:

- The user's message
- Commit messages
- PR description if one exists
- The code itself

Write one clear paragraph. If you're unsure about the intent, ask the user before proceeding.

## Step 3, Spawn Reviewers
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint

mdr add iap/pstack-hermes/interrogate@sha256:4684d3d96352d459

The line at the top of this page pins the label git:20261006.f7c5841, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.

Badge

[![mdr](https://markdownregistry.com/badge/art_duklhwx3e6pzr2gw.svg)](https://markdownregistry.com/a/art_duklhwx3e6pzr2gw)

2 badge image fetches in 30 days. What the badge shows.

Versions

The registry has recorded 1 version of this file, committed on Oct 6, 2026.

version	committed	commit	size	audit
git:20261006.f7c5841 latest	2026-10-06	f7c5841	5,107 B	A	view

Audit of the latest version

A 17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.

pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (5107 bytes)
pass: No zero-width or bidi control characters
pass: No instruction hidden inside an HTML comment
pass: No link to an exfiltration or paste host
pass: No credential-shaped string
pass: No instruction to send local credentials anywhere
pass: No text hidden with inline styles
pass: No prompt-injection phrasing
pass: No curl or wget piped into a shell
pass: No recursive delete of root, home or parent
pass: No instruction to read or print local credentials
pass: No base64 blob over 200 characters
pass: No link to a raw IP address
pass: No script tag

Source

GitHub

iap/pstack-hermes · 30 stars · license a license file GitHub does not identify · pushed 2026-10-31 · branch dist

API

GET https://markdownregistry.com/api/v1/artifacts/art_duklhwx3e6pzr2gw
GET https://markdownregistry.com/api/v1/resolve?ref=iap/pstack-hermes/interrogate
GET https://markdownregistry.com/api/v1/blob/4684d3d96352d459cc851c3eb7422e87e0a69097edd6935eb37f6c0656aba43d

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from iap/pstack-hermes

architect SKILL.md skill

iap/pstack-hermes · skills/architect/SKILL.md · Sketch types, signatures, and module structure before code, then stay in the loop while implementation fills in. Use…