agentmods.dev

auto_task.criticize

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

A review task for checking whether an automated coding task or GitHub issue clearly states its problem, solution, repositories, and pull requests.

In plain words
What is it for?
Use it to inspect a task plan, identify unclear parts, update its repository checklist, and request clarification before execution.
Why use it?
It finds missing details before work starts, especially when one task affects several code repositories.

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 15 tokens original Apache-2.0

Good fit Use it to inspect a task plan, identify unclear parts, update its repository checklist, and request clarification before execution.

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

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/gpsaggese/helpers/auto_task.criticize"><img src="https://agentmods.dev/badge/skills/gpsaggese/helpers/auto_task.criticize.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 15 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 473 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.00015 $0.00473
Opus 5.5 $0.00006 $0.00189
Sonnet 5.5 $0.00003 $0.00095
Haiku 4.5 $0.00002 $0.00047

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

Security

Grade A, and why

auto_task.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/auto_task.criticize/SKILL.md · 53 lines

What it actually says

Goal

  • The user passes a file <FILE> (e.g., tasks.md) or a GitHub issue number <GITHUB_ISSUE_NUM>
  • Read the content carefully. Make sure the problem and the solution are clear and complete

Workflow

Read Context

  • Read the plan (file or GitHub issue)
  • Analyze the problem and the solution

Create a Plan, If Needed

  • Identify the repos the change affects. This decides whether a PR spans multiple repos

    • Update the * Repo: checklist in .claude/templates/auto_task.template.md, following .claude/skills/auto_task.rules.md section "Multi-Repo Issues, Branches, and PRs"
    • If more than one repo is checked, each PR<NUM> block in "Solution" must name its target repo. An unlabeled PR<NUM> in a multi-repo task is an unclear plan (see "Ask for Clarification Before Executing an Unclear Plan" in .claude/skills/auto_task.rules.md)
    • Do not add or edit a ## Companion PRs section. Once PRs exist, git_create_issue_and_branch.py generates it, per .claude/skills/auto_task.rules.md "Multi-Repo Issues, Branches, and PRs"

  • If the task is not perfectly clear, follow .claude/skills/auto_task.rules.md section "Ask for Clarification Before Executing an Unclear Plan"

Output Results

  • Follow .claude/skills/auto_task.rules.md
  • Write the output as a file in the format .claude/templates/auto_task.template.md

Conventions

  • Follow .claude/skills/coding.rules.md when writing code
  • Follow .claude/skills/testing.rules.md when writing testing code

Verification

  • The problem statement is clear and unambiguous
  • The proposed solution is clear and unambiguous
  • Any needed clarification was requested before the task moves to execution
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 · 53 lines · 15 tokens per session scan A 259e4b3aa53a

Subscribe to this mod's changes

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

Project management
Related

auto_task.criticize compared with skills from other repositories

auto_task.criticize next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
auto_task.criticizegpsaggese/helpersSkill158todayApache-2.0A15Claude 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