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 allemaar/open-skills --skill insight-critiquegit clone --depth 1 https://github.com/allemaar/open-skillsWrote 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/allemaar/open-skills/insight-critique)<a href="https://agentmods.dev/skills/allemaar/open-skills/insight-critique"><img src="https://agentmods.dev/badge/skills/allemaar/open-skills/insight-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/allemaar/open-skills/insight-critique"><img src="https://agentmods.dev/badge/skills/allemaar/open-skills/insight-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.00122 | $0.01022 |
| Opus 5 | $0.00061 | $0.00511 |
| Sonnet 5 | $0.00024 | $0.00204 |
| Haiku 4.5 | $0.00012 | $0.00102 |
Grade A, and why
insight-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 12d 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/critique
Advisory review of the last plan, code, architecture, or UI output. Runs four analysis passes and emits a structured report. Never blocks — advisory only.
Structured execution spec:
protocol.yon. Read it for the canonical rules and step sequence; this file is explanation. The two must stay in sync — if you edit one, update the other and refresh the@STAMPdate.
Caller Options. Before executing, run the Caller Options protocol (
caller-options/SKILL.md): triage this invocation for material optionality across the venues and modes declared in front-matter; if one path clearly dominates, proceed silently; otherwise surface the options to the caller. A resolved-invocation marker means COP already ran — execute the fixed combination directly, do not re-enter COP.
Phase 1 — Classify
Identify what is being critiqued. Pick exactly one: Code, Plan, Architecture, UI. If the subject is ambiguous, ask for clarification before proceeding.
Phase 2 — Analysis
Run all four passes. Passes 1–3 are independent. Pass 4 depends on Risks.
- Summary — what is this? State purpose, scope, and approach concisely.
- Strengths — what is well-designed, sound, or admirable? Be specific. Do not pad.
- Risks — what is fragile, dangerous, underspecified, or likely to fail? Rank by severity: High / Medium / Low.
- Fixes — for each risk, propose a concrete actionable change. Distinguish must-fix from nice-to-fix.
Phase 3 — Render Report
Output a structured report with four labeled sections: Summary, Strengths, Risks, Fixes. Then set a verdict:
- ✅ Approved — all risks are Low or cosmetic
- ⚠️ Conditional — risks present but fixable; apply fixes then proceed to
/plan-execute - 🚫 Not Approved — High risks present;
/plan-createor a redesign is required
Constraints
- Advisory only. Never block or halt the user's work unless a kernel-prime violation is detected.
- Never mark Approved when any risk is rated Medium or above.
- Do not pad Strengths to soften the critique. If there are few strengths, say so.
What ships with it
1 file 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.
- 12d ago First seen · 76 lines · 122 tokens per session scan A 3a48e6b1764c
insight-critique is a skill published in the GitHub repository allemaar/open-skills (14 stars, last pushed yesterday), licensed Apache-2.0. It adds 122 tokens to every session and 1,022 once invoked, about $0.0006 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-30.
Other skills, from other repositories
design-is
Audit a design against Dieter Rams' ten "Good design is..." principles, then hand off a /make-plan prompt for one of three outcomes — new design, refine design, or redesign. Use when the user says "audit this design", "design review", "check this UI against Rams", "is this UI good", "critique this design", "design…
design-standards
Apply production-grade design standards when building or reviewing pages, components, or UI. Use this skill whenever the user asks to build a page, design a component, lay out a section, review the UI, fix the layout, or check design quality. Triggers on build a page, create a component, design a section, hero, card…
ln-75-architecture-diagram-builder
Creates current or target architecture diagrams as the primary deliverable. Not for UI design, architecture audits, or invented structure.
pr-screenshot-comparison
Create clear, polished before-and-after screenshots from the actual running product for a GitHub pull request. Use when a UI change needs visual proof: capture matching product states, crop to the relevant UI, stitch and caption one comparison image, attach it natively to the PR, and keep the image out of the…
fabrik-validate-comment
Use when operating as the Fabrik Validate comment reviewer. This skill guides updating the validation report, re-running checks, and applying minor fixes in response to user feedback — signaling completion only when the user explicitly indicates the issue is resolved.
rk-house-style
The ENFORCED house design system — one premium look for every frontend, with gates that stop drift (not just advice). Triggers on building or editing a page, component, view, dashboard, screen, form, table, chart, or any UI surface ("build a page", "create a component", "design a dashboard", "make a form", "add a…