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 agentmods add skills/biolytics-ai/rhetoric-engine/critique-iteratornpx skills add Biolytics-AI/rhetoric-engine --skill critique-iteratorgit clone --depth 1 https://github.com/Biolytics-AI/rhetoric-engineWrote 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/biolytics-ai/rhetoric-engine/critique-iterator)<a href="https://agentmods.dev/skills/biolytics-ai/rhetoric-engine/critique-iterator"><img src="https://agentmods.dev/badge/skills/biolytics-ai/rhetoric-engine/critique-iterator.svg" alt="Measured on agentmods" 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.00034 | $0.00909 |
| Opus 5 | $0.00017 | $0.00454 |
| Sonnet 5 | $0.00007 | $0.00182 |
| Haiku 4.5 | $0.00003 | $0.00091 |
Grade A, and why
critique-iterator 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 5d 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Critique Iterator
Convert feedback into a ranked revision backlog. Treat critique as evidence about audience risk, not as a vote on preferences.
Inputs
- Draft deck, outline, talk track, speaker notes, rehearsal notes, review comments, rubric scores, or stakeholder feedback.
- Approved intent, insight, argument spine, slide thesis map, evidence dossier, design guidance, delivery constraints, and success criteria when available.
- Audience, setting, duration, decision need, and required standards.
- Prior critique backlog and delta report when running another review loop.
Outputs
severity_ranked_issues: ordered issues with risk type, affected slide or section, evidence, severity, and owner when useful.root_causes: underlying causes such as unclear thesis, weak proof, broken sequence, overload, inaccessible design, or delivery mismatch.concrete_fixes: specific revisions that preserve approved artifacts or route upstream when they cannot.retest_plan: rubric checks, audience tests, rehearsal checks, and acceptance criteria for the next loop.delta_report: what changed since the prior version, what improved, what regressed, and what remains unresolved.
Workflow
- Normalize all feedback into observable audience risks before ranking it.
- Classify each issue as comprehension, credibility, action, design, or delivery risk; label mere taste separately and do not let it outrank material risk.
- Compare feedback against the approved intent, insight, argument spine, slide thesis map, evidence, and delivery constraints.
- Identify root causes instead of only restating symptoms.
- Rank by severity, audience impact, likelihood, dependency order, and effort only after impact is clear.
- Propose concrete fixes that name the affected artifact, slide, note, transition, visual, or delivery behavior.
- Support rubric-driven review loops by mapping issues to rubric dimensions, score changes, acceptance criteria, and retest actions.
- Produce a delta report for repeat reviews; separate fixed, improved, unchanged, new, and regressed items.
- Route upstream when a fix would change approved intent, insight, argument spine, slide thesis map, or evidence claims.
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.
- 5d ago First seen · 68 lines · 34 tokens per session scan A 4e7f0ce12a47
critique-iterator is a skill published in the GitHub repository Biolytics-AI/rhetoric-engine (1 stars, last pushed 3mo ago), licensed MIT. It adds 34 tokens to every session and 909 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
spec-kitty-charter-doctrine
Run charter interview, generation, context, and sync workflows for project governance in Spec Kitty 3.x. Access doctrine artifacts programmatically via DoctrineService. Resolve agent profiles. Load action-scoped governance context iteratively, not all at once. Triggers: "interview for charter", "generate charter"…
mongodb-query-optimizer
Help with MongoDB query optimization and indexing. Use only when the user asks for optimization or performance: "How do I optimize this query?", "How do I index this?", "Why is this query slow?", "Can you fix my slow queries?", "What are the slow queries on my cluster?", etc. Do not invoke for general MongoDB query…
polar-local-environment
This skill should be used when setting up or managing Polar local development environment with Docker.
neo4j-modeling-skill
Design, review, and refactor Neo4j graph data models. Use when choosing node labels vs relationship types vs properties, migrating relational/document schemas to graph, detecting anti-patterns (generic labels, supernodes, missing constraints), designing intermediate nodes for n-ary relationships, enforcing schema with…
lov-article-creator
统一创建、改写、品牌化或忠实转载微信公众号文章包：正文写作调用唯一文风与作者性能力，离线完成结构、品牌、封面、4:3 首图、来源与质量验收。Use when asked to write, brand, audit, or faithfully repost a WeChat article package.
lov-env-management
统一管理平台、账号与多组 API Key，维护有效期和启用状态，安全同步到 zsh 或用户会话环境，并提供脱敏 Dashboard；用户说“管理环境变量”“rotate API keys”时使用。.