critique AGENTS.md

Instructions for developing an interactive terminal interface, or TUI, built with the OpenTUI framework and React. They cover unreleased package versions, Bun commands, and safe ways to run the project.

In plain words
What is it for?
Use them when updating OpenTUI preview dependencies, reading its current documentation, building the terminal interface, or running non-interactive commands.
Why use it?
They prevent version references from pointing to the wrong code and warn against commands that would start an interactive process and hang the session.

Instructions file for CodexOpenCode

Install

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.

agentmods
npx agentmods add instructions/remorses/critique/agents-md
Clone the repo
git clone --depth 1 https://github.com/remorses/critique

Made for: Codex, OpenCode.

Per session 1,974 This file is loaded in full into every session.
When invoked 1,974 The same file — it is already loaded in full.
Security scan A 1 finding. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.01974 $0.01974
Opus 5 $0.00987 $0.00987
Sonnet 5 $0.00395 $0.00395
Haiku 4.5 $0.00197 $0.00197

Measured 3d ago against content hash 3f691c9fe37e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

critique AGENTS.md scanned grade A with 1 finding 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 3d 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

IMPORTANT! before starting every task ALWAYS read opentui docs with `curl -s https://raw.githubusercontent.com/sst/opentui/refs/heads/main/packages/react/README.md`
AGENTS.md · 172 lines

How it starts

The opening of the file, as written. The whole thing — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.

opentui

opentui is the framework used to render the tui, using react.

IMPORTANT! before starting every task ALWAYS read opentui docs with curl -s https://raw.githubusercontent.com/sst/opentui/refs/heads/main/packages/react/README.md

ALWAYS!

using unreleased opentui versions

to use a pkg.pr.new preview URL for opentui, get the last commit hash (40 chars always) from PR https://github.com/anomalyco/opentui/pull/536:

gh pr view 536 -R anomalyco/opentui --json commits --jq '.commits[-1].oid[:40]'

then use it in package.json:

https://pkg.pr.new/anomalyco/opentui/@opentuah/core@<hash>
https://pkg.pr.new/anomalyco/opentui/@opentuah/react@<hash>

YOU MUST ALWAYS use the commit hash 40 characters long when changing the pkg.pr.new url! not the pr number!

if the commit hash url does not work it means it is still building. ignore the pkg.pr.new comment with the pr number in the install script. you MUST use the url with the commit hash.

bun

NEVER run the interactive TUI (e.g. bun run src/cli.tsx without arguments). It will hang. Instead ask the user to run it.

The web command is safe to run - it generates HTML and exits:

bun run src/cli.tsx web

NEVER use tsc --noEmit in this repo. Always run emitting builds so cli/dist stays updated.

after every code change, run bun run build from cli/ to make sure it compiles. fix any type errors before moving on.

NEVER use require. just import at the top of the file with esm

use bun add to install packages instead of npm

React

NEVER pass function or callbacks as dependencies of useEffect, this will very easily cause infinite loops if you forget to use useCallback

NEVER use useCallback. it is useless if we never pass functions in useEffect dependencies

Try to never use useEffect if possible. usually you can move logic directly in event handlers instead

Rules

  • if you need Node.js apis import the namesapce and not the named exports: import fs from 'fs' and not import { writeFileSync } from 'fs'
  • DO NOT use as any. instead try to understand how to fix the types in other ways
  • to implement compound components like List.Item first define the type of List, using a interface, then use : to implement it and add compound components later using . and omitting the props types given they are already typed by the interface, here is an example
  • DO NOT use console.log. only use logger.log instead
  • uses onInput not onChange. it is passed a simple string value and not an event object
  • to render examples components use renderWithProviders not render
  • ALWAYS bind all class methods to this in the constructor. This ensures methods work correctly when called in any context (callbacks, event handlers, etc). Example:

Read the full file on GitHub · 172 lines

Changes

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.

  1. 3d ago First seen · 172 lines · 1,974 tokens per session scan A 3f691c9fe37e

Subscribe to this mod's changes

critique AGENTS.md is an instructions file published in the GitHub repository remorses/critique (1,264 stars, last pushed 2mo ago), licensed MIT. It adds 1,974 tokens to every session, about $0.0099 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.