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 SebastianElvis/reaper --skill critiquegit clone --depth 1 https://github.com/SebastianElvis/reaperWrote 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/sebastianelvis/reaper/critique)<a href="https://agentmods.dev/skills/sebastianelvis/reaper/critique"><img src="https://agentmods.dev/badge/skills/sebastianelvis/reaper/critique/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/sebastianelvis/reaper/critique"><img src="https://agentmods.dev/badge/skills/sebastianelvis/reaper/critique.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.00047 | $0.02055 |
| Opus 5 | $0.00023 | $0.01027 |
| Sonnet 5 | $0.00009 | $0.00411 |
| Haiku 4.5 | $0.00005 | $0.00205 |
Grade A, and why
critique 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 10d 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.
How it starts
The opening of the file, as written. The whole thing — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Critique
Provide external perspective on investigation results. Three modes: human feedback, Codex consultation, and self-review. Can trigger additional investigation cycles when feedback requires deeper exploration.
Usage
Invoke this skill by name; pass either feedback as a quoted string, --codex, or --self. On slash-command hosts, prefix with / (e.g. /critique "<feedback>").
# Human feedback — iterate on existing results
critique "dig deeper into the liveness proof gap under partial synchrony"
# External-model consultation — get AI devil's advocate or inspiration (requires MCP host)
critique --codex
# Self-review — agent reviews its own findings for gaps
critique --self
Inputs
Always read before starting:
reaper-workspace/notes/current-understanding.md— the "branch tip" of accumulated knowledgereaper-workspace/notes/results.md— what's been tried and what happenedreaper-workspace/notes/problem-statement.md— model assumptions and property definitionsreaper-workspace/notes/ideas.md— the ideas to investigatereaper-workspace/feedbacks/— prior feedback rounds
Lazy-load only when needed:
reaper-workspace/notes/paper-summary.md— the source paper (if provided)reaper-workspace/notes/literature.md— known prior workreaper-workspace/papers/— downloaded PDFs and per-paper notes
Mode: Human Feedback
When the argument is quoted text, the skill enters human feedback mode. This is used after investigation has produced results and the user wants to refine, deepen, or challenge specific findings.
1. Determine the Feedback Round
Check reaper-workspace/feedbacks/ for existing round-*.md files. The new round number is one greater than the highest existing round, or 1 if none exist.
2. Classify and Save Feedback
Classify the user's feedback and write reaper-workspace/feedbacks/round-N.md:
# Feedback Round N
**User request**: [the user's feedback, verbatim or lightly paraphrased]
**Category**: [scope | deepen | explore | rewrite]
**Action plan**: [what will be done]
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.
- 10d ago First seen · 148 lines · 47 tokens per session scan A 2fa4d1709d2b
critique is a skill published in the GitHub repository SebastianElvis/reaper (9 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 47 tokens to every session and 2,055 once invoked, about $0.0002 per session on Opus 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-08-31.
Other skills, from other repositories
content-refinement-agent
Step 5 of the PaperOrchestra pipeline (arXiv:2604.05018). Iteratively refine drafts/paper.tex by simulating peer review and applying targeted revisions, with strict accept/revert halt rules, deterministic 0-100 decision bands (Accept/Minor/Major/Reject) that drive a target-met early stop, and a Devil's Advocate…
literature-review-agent
Step 3 of the PaperOrchestra pipeline (arXiv:2604.05018). Execute the literature search strategy from outline.json — discover candidate papers via web search, verify them through Semantic Scholar (Levenshtein > 70 fuzzy title match, temporal cutoff, dedup by paperId), cross-corroborate against Crossref + OpenAlex to…
agent-research-aggregator
Pre-pipeline aggregator that scans AI agent cache directories (.claude, .cursor, .antigravity, .openclaw) or any user-specified directory for experimentation logs, extracts insights and numeric results, and formats them as PaperOrchestra-ready inputs (idea.md + experimentallog.md). TRIGGER when the user says…
paper-orchestra
Orchestrate the full PaperOrchestra (Song et al., 2026, arXiv:2604.05018) five-agent pipeline to turn unstructured research materials (idea, experimental log, LaTeX template, conference guidelines, optional figures) into a submission-ready LaTeX manuscript and compiled PDF. TRIGGER when the user asks to "write a paper…
section-writing-agent
Step 4 of the PaperOrchestra pipeline (arXiv:2604.05018). ONE single multimodal LLM call that drafts the remaining paper sections (Abstract, Methodology, Experiments, Conclusion), extracts numeric values from experimentallog.md into LaTeX booktabs tables, splices the generated figures from Step 2, and merges…
plotting-agent
Step 2 of the PaperOrchestra pipeline (arXiv:2604.05018). Execute the visualization plan from outline.json — render plots and conceptual diagrams from experimentallog.md and idea.md, optionally refine via VLM critique loop, and produce context-aware captions. Runs in parallel with the literature-review-agent. TRIGGER…