agentmods.dev

text.criticize

text.criticize is a skill for Claude Code from gpsaggese/helpers. It costs 9 tokens per session (718 once invoked), scanned A, original, Apache-2.0.

A text-review workflow that checks documents for factual errors, contradictions, technical mistakes, broken references, and opportunities to improve clarity.

In plain words
What is it for?
Use it to review markdown, blog posts, or documentation and propose specific content improvements.
Why use it?
It helps find problems that can mislead readers while separating definite errors from optional style suggestions.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter; reads .claude/ paths.

not rated 158repo +1 today A scan 9 tokens original Apache-2.0

Good fit Use it to review markdown, blog posts, or documentation and propose specific content improvements.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/gpsaggese/helpers/text.criticize
View source ↗ gpsaggese/helpers
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.

Any agent
npx skills add gpsaggese/helpers --skill text.criticize
Clone the repo
git clone --depth 1 https://github.com/gpsaggese/helpers

Made for: Claude Code.

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 text.criticize

README.md
[![agentmods](https://agentmods.dev/badge/skills/gpsaggese/helpers/text.criticize/github.svg)](https://agentmods.dev/skills/gpsaggese/helpers/text.criticize)
Your own site
<a href="https://agentmods.dev/skills/gpsaggese/helpers/text.criticize"><img src="https://agentmods.dev/badge/skills/gpsaggese/helpers/text.criticize/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.

agentmods 80×15 button for text.criticize

Your own site · 80×15
<a href="https://agentmods.dev/skills/gpsaggese/helpers/text.criticize"><img src="https://agentmods.dev/badge/skills/gpsaggese/helpers/text.criticize.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 9 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 718 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.
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.00009 $0.00718
Opus 5.5 $0.00004 $0.00287
Sonnet 5.5 $0.00002 $0.00144
Haiku 4.5 $0.00001 $0.00072

Measured yesterday against content hash 5e1127ab7bab, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

text.criticize 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 yesterday.

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.

.claude/skills/text.criticize/SKILL.md · 83 lines

How it starts

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

Goal

  • Review and criticize the text (markdown, blog posts, documentation)
  • Identify mistakes and improvement opportunities, focusing on factual errors, rather than style suggestions
  • Propose concrete improvements to content, flow, visual clarity, pacing, and audience fit

Workflow

Read the Material

  • Read the text passed by the user carefully

Identify and Rank Mistakes

Definition

  • Criteria for mistakes:

    • Factual inaccuracy (wrong information, outdated claims)
    • Logical contradiction or inconsistency
    • Technical error (code doesn't work, command is wrong, API is misrepresented)
    • Broken reference (link is dead, file path is wrong, name is misspelled)
    • Only report issues you are absolutely certain about

  • Ranking severity:

    • High: Misleads reader or causes confusion
    • Medium: Could improve clarity or accuracy
    • Low: Minor inconsistency or incomplete statement

TODOs

  • Ignore the TODOs that already exist in the text

Suggest Improvements

  • Identify opportunities to improve clarity, structure, or completeness without changing facts

Definition

  • Types of improvements:

    • Clarity: Making text easier to understand
    • Completeness: Adding missing context or examples
    • Consistency: Aligning terminology or formatting
    • Readability: Breaking up dense sections or improving flow

  • Ranking severity:

    • High: Significantly improves comprehension or prevents misunderstanding
    • Medium: Moderately improves clarity or adds useful detail
    • Low: Minor improvement in readability or polish

Write the Results

  • The output format is a vim cfile following .claude/skills/cfile.rules.md

    <full path file>:<LINE_NUMBER>:1 [HIGH/MEDIUM/LOW] Short description of error
<full path file>:<LINE_NUMBER>:1 [HIGH/MEDIUM/LOW] Why this is wrong and what the correct statement should be
...

  • Example

    msml610/lectures_source/README.md:12 [HIGH] Claims "pip install X" but pip package is named "X-lib"
msml610/lectures_source/README.md:5 [HIGH] Add example of basic usage after the description
helpers/docs.md:8 [MEDIUM] Link to API docs is outdated (2023 version, current is 2024)

Read the full file on GitHub · 83 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. yesterday First seen · 83 lines · 9 tokens per session scan A 5e1127ab7bab

Subscribe to this mod's changes

text.criticize is a skill published in the GitHub repository gpsaggese/helpers (158 stars, last pushed today), licensed Apache-2.0. It adds 9 tokens to every session and 718 once invoked, about $0.0000 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-11-06.

Writing and docs
Related

text.criticize compared with skills from other repositories

text.criticize next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
text.criticizegpsaggese/helpersSkill158todayApache-2.0A9Claude Code
imagegenopenai/codexSkill134ktodayApache-2.0A113Codex
local-ai-agentsmicrosoft/ai-agents-for-beginnersSkill79ktodayMITA200Claude Code, Codex
playwright-climicrosoft/playwrightSkill99ktodayApache-2.0A19Claude Code
systematic-debuggingobra/superpowersSkill314k3d agoMITA21Claude Code
next-cache-components-adoptionvercel/next.jsSkill143ktodayMITA95Claude Code
chat-pet-sprite-creationmicrosoft/vscodeSkill195ktodayMITA53Claude Code, Codex