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.
npx skills add dmae97/omk --skill interrogategit clone --depth 1 https://github.com/dmae97/omkWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/dmae97/omk/interrogate)<a href="https://agentmods.dev/skills/dmae97/omk/interrogate"><img src="https://agentmods.dev/badge/skills/dmae97/omk/interrogate/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/dmae97/omk/interrogate"><img src="https://agentmods.dev/badge/skills/dmae97/omk/interrogate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00053 | $0.01065 |
| Opus 5.5 | $0.00021 | $0.00426 |
| Sonnet 5.5 | $0.00011 | $0.00213 |
| Haiku 4.5 | $0.00005 | $0.00106 |
Grade A, and why
pstack-interrogate 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 today.
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.
How it starts
The opening of the file, as written. The whole thing — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Interrogate
Spawn one reviewer per configured role entry to adversarially review code changes. OMK delegates inherit the session model, so independent briefs provide review separation, not model diversity. The deliverable is a synthesized verdict. Do NOT auto-apply changes.
Step 1, 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 with any surrounding context files the reviewers need to understand the code.
Step 2, Intent
Before spawning reviewers, state the intent in one clear paragraph from the user's message, commit messages, the PR description if one exists, and the code. If you're unsure about the intent, ask the user before proceeding.
Step 3, Spawn Reviewers
Launch all reviewers in a single message with the subagent extension, one per entry on the interrogate reviewers line in the pstack settings file (~/.omk/agent/pstack-models.md, written by /skill:pstack-setup-pstack), labeled Reviewer A, B, and so on to match the entry count. If the file or that line is missing, use the table defaults.
Subagent tool. Spawns in this skill use OMK's subagent extension. Call it with agent, task, and agentScope, and use tasks: [{agent, task}, ...] for a parallel fan-out. Keep the prompt and inherit the session model. Pass no model, effort, or speed fields. If the subagent extension is not loaded or the project is not trusted, run each reviewer yourself, one after another.
| Subagent | Default model |
|---|---|
| Reviewer A | inherit-parent |
| Reviewer B | inherit-parent |
Each reviewer is a read-only subagent call. OMK subagents inherit the session model, so auto and inherit-parent entries need no model field; a configured entry that is not in the OMK catalog also falls back to the session model.
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- today Changed 07fc28a89381
- yesterday First seen · 77 lines · 53 tokens per session scan A ba28027d7af3
pstack-interrogate is a skill published in the GitHub repository dmae97/omk (151 stars, last pushed today), licensed MIT. It adds 53 tokens to every session and 1,065 once invoked, about $0.0002 per session on Opus 5.5. 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-10-27.
Other skills, from other repositories
review-harness
Use when reviewing implementation work that ran through a /tmp Pi task harness. Checks contract drift, unsafe shortcuts, validation evidence, and status honesty.
review
Review checkpoints in SyncPoint — create review requests, add checklists, submit evidence, approve or request changes. Use when reviewing another agent's work before it can proceed.
pr-review
Review Cool Workflow pull requests or branch diffs. Use when Codex must inspect code changes for bugs, regressions, FreeBSD/POLA violations, missing tests, generated artifact drift, release-contract risk, or CI implications, and return findings first with file/line citations.
autofix-pr
Watch a pull request and fix it from a worktree of its own - CI failures, review feedback from trusted authors and merge conflicts are fixed, pushed to the PR branch and answered on the PR under the user's git and gh identity. Usage - /autofix-pr [ | ] [--once] [--every ] [--no-reply] [--yes] [instructions]…
gh-find-prs
Survey open Codewhale PRs and triage each for mergeability and disposition against the real landing branch.
review
Diff-scoped correctness review that reads the codebase around the change — callers, contracts, and invariants — and returns line-anchored findings ranked by severity with confidence, then a merge-risk verdict. Use for reviewing a PR, diff, or named change set. Not for style review, approvals-as-rubber-stamp, or…