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.
npx skills add causify-ai/helpers --skill text.criticizegit clone --depth 1 https://github.com/causify-ai/helpersWrote 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.
[](https://agentmods.dev/skills/causify-ai/helpers/text.criticize)<a href="https://agentmods.dev/skills/causify-ai/helpers/text.criticize"><img src="https://agentmods.dev/badge/skills/causify-ai/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.
<a href="https://agentmods.dev/skills/causify-ai/helpers/text.criticize"><img src="https://agentmods.dev/badge/skills/causify-ai/helpers/text.criticize.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 3 Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
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.00009 | $0.00719 |
| Opus 5.5 | $0.00004 | $0.00288 |
| Sonnet 5.5 | $0.00002 | $0.00144 |
| Haiku 4.5 | $0.00001 | $0.00072 |
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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 84 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
- Identify mistakes in the passed text
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)
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.
- 1mo ago Changed · +5 lines bb767746a758
- 1mo ago First seen · 79 lines · 9 tokens per session scan A 72aaa185f82a
text.criticize is a skill published in the GitHub repository causify-ai/helpers (150 stars, last pushed yesterday), licensed Apache-2.0. It adds 9 tokens to every session and 719 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-09-03.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…