openpress-apply-comments

openpress-apply-comments is a skill for Claude Code, Codex from quan0715/open-press. It costs 52 tokens per session (900 once invoked), scanned A, original, MIT.

A workflow for applying pending review comments marked in source documents. It reads each comment, makes the requested source edit, removes the marker when resolved, and leaves unclear or failed comments for later.

In plain words
What is it for?
Use it to inspect, apply, resolve, or clear pending review markers while editing the original source files.
Why use it?
It keeps review feedback connected to the code or document it describes and prevents comments from being marked complete before the requested change is actually made.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is node engine/cli.mjs validate . # structural checks only, no render.

Good fit Use it to inspect, apply, resolve, or clear pending review markers while editing the original source files.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/quan0715/open-press
agentmods
npx agentmods add skills/quan0715/open-press/openpress-apply-comments

Made for: Claude Code, 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.

agentmods badge for openpress-apply-comments

README.md
[![agentmods](https://agentmods.dev/badge/skills/quan0715/open-press/openpress-apply-comments.svg)](https://agentmods.dev/skills/quan0715/open-press/openpress-apply-comments)
Your own site
<a href="https://agentmods.dev/skills/quan0715/open-press/openpress-apply-comments"><img src="https://agentmods.dev/badge/skills/quan0715/open-press/openpress-apply-comments.svg" alt="Measured on agentmods" height="20"></a>
Per session 52 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 900 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00052 $0.00900
Opus 5 $0.00026 $0.00450
Sonnet 5 $0.00010 $0.00180
Haiku 4.5 $0.00005 $0.00090

Measured 8d ago against content hash 5f7946415ce4, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

openpress-apply-comments 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 8d 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/openpress-apply-comments/SKILL.md · 98 lines

How it starts

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

open-press Apply Comments

This is the workflow skill for turning pending @openpress-comment markers into source edits. A comment is resolved only when the requested source change has been made and the marker has been removed.

openpress-collaborate owns whether the agent should propose, refresh, apply a reviewed preview, or edit directly. Use this skill for marker mechanics. If the user asks to apply .openpress/review/current.json, return to openpress-collaborate instead of interpreting the Comments as a separate direct-edit batch.

Responsibilities

  • List pending @openpress-comment markers.
  • Read the decoded comment note, hint, source path, and nearby source.
  • Apply the requested edit as a small source change.
  • Remove the marker after the edit is complete.
  • Leave ambiguous or failed comments in place.
  • Verify before reporting completion.

Boundary

  • Use openpress for the canonical source/generated path table when unsure.
  • Edit source, not generated output.
  • Default to editing the source file that contains the marker.
  • Route domain-heavy work to the owning skill:
    • openpress-create-pages for page prose, hierarchy, captions, claims, tone, narrative, page theme, and page components.
    • openpress-create-slide for deck narrative, slide density, direct slide sources, active theme tokens, core Object API composition, Tailwind semantic styling, and reusable UI primitives.
    • openpress-plugins for external diagramming, visual tools, and writing helpers.
  • Do not rewrite unrelated sections while resolving one comment.

Workflow

  1. Discover comments.

    rg "@openpress-comment" press -n
    

    If decoded notes are needed and the framework helper exists, use it:

    node --input-type=module -e 'import { listCommentMarkers } from "./packages/core/engine/react/comment-marker.mjs"; console.log(JSON.stringify(await listCommentMarkers({ root: process.cwd() }), null, 2));'
    
  2. Pick the requested scope.

    • If the user names one comment, resolve only that comment.
    • If the user says apply comments without an id, process pending comments in source order.
    • Handle comments one at a time; do not batch unrelated rewrites under one marker.

Read the full file on GitHub · 98 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. 8d ago First seen · 98 lines · 52 tokens per session scan A 5f7946415ce4

Subscribe to this mod's changes

openpress-apply-comments is a skill published in the GitHub repository quan0715/open-press (14 stars, last pushed 9d ago), licensed MIT. It adds 52 tokens to every session and 900 once invoked, about $0.0003 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.

Related

Other skills, from other repositories

emdash-cli

Use the EmDash CLI to manage content, schema, media, and more. Use this skill when you need to interact with a running EmDash instance from the command line — creating content, managing collections, uploading media, generating types, or scripting CMS operations.

emdash-cms/emdash · 56 tokens

adversarial-reviewer

Adversarial code review that assumes bugs exist and hunts for them. Use when asked to review code, find bugs, audit for correctness, stress-test a PR, or when someone says "tear this apart" or "what's wrong with this". Give no benefit of the doubt — every line is guilty until proven innocent.

emdash-cms/emdash · 71 tokens

investigate

Investigate a single EmDash issue end to end -- classify, choose a repro path, reproduce, diagnose, verify, and (only on an explicit maintainer fix directive) fix and confirm. Every verdict carries its evidence.

emdash-cms/emdash · 48 tokens

repro-admin

Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.

emdash-cms/emdash · 48 tokens

repro-public

Reproduce a bug in the public-facing rendered site (not the admin). Attach a container, start the demo dev server, drive public routes with agent-browser, and capture the reproduction as screenshots plus a replayable transcript.

emdash-cms/emdash · 48 tokens

verify

Decide whether the diagnosed behaviour is actually a bug or the code doing what it was designed to do. This is the gate that guards the fix stage.

emdash-cms/emdash · 33 tokens