What is webgpt-todo-response?

A handoff-writing guide for sending an AI review back after updating a task list. It helps summarize which suggestions were accepted, questioned, or rejected.

Preparing a concise reply about changes to docs/todolist.md and asking the reviewer to check specific items again.

It prevents the next review from missing important decisions or revisiting settled points.

How yusifeng/formax configures Codex

Reuse

Borrowing it

Nothing to install: this file belongs to yusifeng/formax. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/yusifeng/formax/main/.codex/skills/webgpt-todo-response/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/yusifeng/formax

Made for: Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/yusifeng/formax/webgpt-todo-response/github.svg)](https://agentmods.dev/skills/yusifeng/formax/webgpt-todo-response)

Your own site

<a href="https://agentmods.dev/skills/yusifeng/formax/webgpt-todo-response"><img src="https://agentmods.dev/badge/skills/yusifeng/formax/webgpt-todo-response/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/yusifeng/formax/webgpt-todo-response"><img src="https://agentmods.dev/badge/skills/yusifeng/formax/webgpt-todo-response.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 66 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 975 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

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.

Model	Per session	Once invoked
Fable 5.1	$0.00066	$0.00975
Opus 5.5	$0.00026	$0.00390
Sonnet 5.5	$0.00013	$0.00195
Haiku 4.5	$0.00007	$0.00097

Measured 2mo ago against content hash 1def8bdb6c2e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

webgpt-todo-response 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.

.codex/skills/webgpt-todo-response/SKILL.md · 114 lines

How it starts

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

WebGPT Todo Response

Purpose

Generate the message to send back to WebGPT after we have read its previous analysis and drafted or updated docs/todolist.md.

Use this skill when the user asks:

whether we have rebuttals or questions for WebGPT
what to include when sending our todo back to WebGPT for another pass
to prepare a response asking WebGPT to evaluate, improve, or challenge our todo
to compare WebGPT's recommendations against our chosen implementation scope

Inputs To Inspect

Read only the files needed for the current handoff:

WebGPT response, usually under repomix-output/
current todo, usually docs/todolist.md
relevant canonical docs under docs/contracts/*, docs/frontend/*, or other explicitly governing docs when the todo depends on them
optional other LLM replies if the user asks for a multi-model synthesis

Do not re-run broad repository analysis unless the todo or WebGPT response depends on code facts that are unclear.

Workflow

Identify WebGPT's strongest recommendations.
- Mark which ones are adopted in the todo.
- Mark which ones are intentionally deferred.
- Mark which ones are rejected or still need clarification.
Check the todo against Formax boundaries.
- Canonical semantics belong in docs/contracts/* and canonical runtime layers, not only UI.
- Web reference UI should reflect runtime/platform truth, not invent it.
- Do not move thread/runtime state ownership into ad hoc component-local logic when the task is structurally runtime-driven.
- Preserve parity-sensitive behavior when relevant: transcript surface semantics, URL/thread sync, prompt/tool exposure boundaries, permissions flow, and active-thread canonical gating.
- Avoid turning a focused task into a broad cleanup or cross-subsystem redesign unless explicitly requested.
Find weak spots in the todo.
- Missing canonical-doc step
- Missing data/type/interface step before UI
- Runtime state ownership drift
- Welcome/draft/thread semantics being mixed together
- Scope creep into unrelated app-server, terminal, diff, approval, or desktop integration work
- Missing tests or review gates
- Missing statement of protocol constraints or non-atomic failure boundaries

Read the full file on GitHub · 114 lines

Files

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.

agents/openai.yaml 182 B

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.

2mo ago First seen · 114 lines · 66 tokens per session scan A 1def8bdb6c2e

Subscribe to this mod's changes

webgpt-todo-response is a skill published in the GitHub repository yusifeng/formax (184 stars, last pushed 3mo ago), licensed MIT. It adds 66 tokens to every session and 975 once invoked, about $0.0003 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.

Project management Writing and docs ai assistant cli developer-tools ink

webgpt-todo-response next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
webgpt-todo-responseyusifeng/formax	Skill	184	3mo ago	MIT	A	66	Codex
unbrokerKevRojo/Dulus	Skill	508	3d ago	GPL-3.0	A	15	Claude Code, Codex
obsidian-basesKevRojo/Dulus	Skill	508	3d ago	GPL-3.0	A	63	Claude Code, Codex
json-canvasKevRojo/Dulus	Skill	508	3d ago	GPL-3.0	A	54	Claude Code, Codex
obsidian-markdownKevRojo/Dulus	Skill	508	3d ago	GPL-3.0	A	105	Claude Code, Codex
obsidian-cliKevRojo/Dulus	Skill	508	3d ago	GPL-3.0	A	102	Claude Code, Codex
defuddleKevRojo/Dulus	Skill	508	3d ago	GPL-3.0	A	74	Claude Code, Codex

formax: Skill for Codex