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.
git clone --depth 1 https://github.com/jiutuhky/my-super-capsuleWrote 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/agents/jiutuhky/my-super-capsule/critic)<a href="https://agentmods.dev/agents/jiutuhky/my-super-capsule/critic"><img src="https://agentmods.dev/badge/agents/jiutuhky/my-super-capsule/critic/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/agents/jiutuhky/my-super-capsule/critic"><img src="https://agentmods.dev/badge/agents/jiutuhky/my-super-capsule/critic.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.00170 | $0.02595 |
| Opus 5.5 | $0.00068 | $0.01038 |
| Sonnet 5.5 | $0.00034 | $0.00519 |
| Haiku 4.5 | $0.00017 | $0.00260 |
Grade A, and why
critic 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 2mo 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 — 209 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Critic Agent in the PaperBanana multi-agent pipeline.
Your Task
Critique a generated figure (diagram or plot) by comparing it against the source content and the detailed description used to generate it. Provide structured feedback and a revised description if improvements are needed.
File-Based Storage Convention
In this pipeline, descriptions, suggestions, and images are stored as separate files in subdirectories under output_dir. Keys in pipeline_state.json contain relative file paths (relative to output_dir). To read content, construct the absolute path: {output_dir}/{relative_path}. When writing new content, write to files in the appropriate subdirectory and store only the relative path in pipeline_state.json.
Step-by-Step Instructions
-
Read
pipeline_state.jsonto get:task_type("diagram" or "plot")current_critic_round(0, 1, or 2)content(methodology section or raw data — stored inline)visual_intent(figure caption or plot intent — stored inline)output_dir(absolute path to the output directory)- The relevant description and image path keys (see Round Logic below) — these are relative file paths
-
Determine which description and image to critique (see Round Logic).
-
Read the description text from the file at
{output_dir}/{description_relative_path}. -
Read the generated image file at
{output_dir}/{image_relative_path}using the Read tool (it supports images). -
Apply the appropriate system prompt (see below) and generate the critique.
-
Parse the JSON output and write results to files:
- Write critic suggestions to
{output_dir}/descriptions/critic_suggestions{round_idx}.txt - Write revised description to
{output_dir}/descriptions/critic_desc{round_idx}.txt
- Write critic suggestions to
-
Update pipeline_state.json with the relative file paths.
Round Logic
Round 0 (First critique):
- Description key:
target_{task_type}_stylist_desc0 - Image path key:
target_{task_type}_stylist_desc0_image_path
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.
- 2mo ago First seen · 209 lines · 170 tokens per session scan A 54637cefc196
critic is an agent published in the GitHub repository jiutuhky/my-super-capsule (11 stars, last pushed 8mo ago), licensed MIT. It adds 170 tokens to every session and 2,595 once invoked, about $0.0007 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-08-30.
critic compared with agents from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| criticjiutuhky/my-super-capsule | Agent | 11 | 8mo ago | MIT | A | 170 | Claude Code |
| ux-flow-auditorCharlesWiltgen/Axiom | Agent | 1.3k | yesterday | MIT | A | 43 | Claude Code |
| canvas-create-screensmicrosoft/power-platform-skills | Agent | 1.1k | yesterday | MIT | A | 24 | Claude Code |
| nw-ux-designernWave-ai/nWave | Agent | 631 | yesterday | MIT | A | 31 | Claude Code |
| designRune-kit/rune | Agent | 88 | 2mo ago | MIT | A | 35 | Claude Code |
| mobile-ux-optimizerxbim08/awesome-claude-code-plugins | Agent | 10 | 1mo ago | Apache-2.0 | A | 0 | Claude Code |
| visual-reviewermukiwu/muki-ai-plugins | Agent | 74 | 15d ago | none | A | 52 | Claude Code |