report-review

A review workflow for checking an existing presentation against an audience-focused checklist. The instructions are in Chinese and start a /report-coaching session for the document you provide.

In plain words
What is it for?
For reviewing and improving an existing presentation or report with a specific audience in mind.
Why use it?
It helps find missing content or unclear parts in a presentation before it is shared. It focuses the review on whether the intended audience can follow the report.

Skill for Claude CodeCodex

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 skills/jtsang4/efficient-coding/report-review
Any agent
npx skills add jtsang4/efficient-coding --skill report-review
Clone the repo
git clone --depth 1 https://github.com/jtsang4/efficient-coding

Made for: Claude Code, Codex.

Per session 21 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 60 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. 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.00021 $0.00060
Opus 5 $0.00010 $0.00030
Sonnet 5 $0.00004 $0.00012
Haiku 4.5 $0.00002 $0.00006

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

Security

Grade A, and why

report-review 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 2d 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.

skills/report-review/SKILL.md · 8 lines

What it actually says

运行一次 /report-coaching 会话,使用审稿模式。目标文档:$ARGUMENTS

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. 2d ago First seen · 8 lines · 21 tokens per session scan A 78cf1a34c1bb

Subscribe to this mod's changes

report-review is a skill published in the GitHub repository jtsang4/efficient-coding (2 stars, last pushed 8d ago), licensed MIT. It adds 21 tokens to every session and 60 once invoked, about $0.0001 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.