A scan for unnecessary code and comments commonly left behind during fast, AI-assisted development. It identifies dead code, outdated compatibility workarounds, deprecation notes, and comments that do not help future maintainers.

Use it during code cleanup to find useless comments, dead code, obsolete compatibility hacks, and other leftovers. It writes a categorized removal plan and checks that the plan can be followed safely.

It gives you a structured list of technical debt without deleting legitimate code or documentation. Each finding includes where it appears and why it may be removable.

How TalonT-Org/AutoSkillit configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to TalonT-Org/AutoSkillit. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/TalonT-Org/AutoSkillit/main/.claude/skills/id-slop/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/TalonT-Org/AutoSkillit

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/talont-org/autoskillit/id-slop/github.svg)](https://agentmods.dev/skills/talont-org/autoskillit/id-slop)

Your own site

<a href="https://agentmods.dev/skills/talont-org/autoskillit/id-slop"><img src="https://agentmods.dev/badge/skills/talont-org/autoskillit/id-slop/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/talont-org/autoskillit/id-slop"><img src="https://agentmods.dev/badge/skills/talont-org/autoskillit/id-slop.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 77 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,680 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.

Model	Per session	Once invoked
Fable 5.1	$0.00077	$0.02680
Opus 5	$0.00039	$0.01340
Sonnet 5	$0.00015	$0.00536
Haiku 4.5	$0.00008	$0.00268

Measured 9d ago against content hash 4f7dfc6fd985, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

id-slop 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 9d 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.

.claude/skills/id-slop/SKILL.md · 373 lines

How it starts

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

Slop Identification Skill

Identify and catalog AI-generated code slop in the codebase. Slop is useless code patterns left behind by AI assistants during rapid development - comments that won't make sense to future readers, backward compatibility hacks, dead code, and other technical debt.

When to Use

User says "id slop", "identify slop", "find slop"
User wants "code cleanup" or "cleanup scan"
User mentions "AI-generated junk" or "leftover comments"
User asks to "find useless comments" or "remove dead code"

Critical Constraints

NEVER:

Modify any source code files (this skill only IDENTIFIES slop)
Remove code without creating a removal plan first
Flag legitimate comments, documentation, or architectural patterns
Flag TODO comments that describe actual future work

ALWAYS:

Use subagents for parallel exploration
Write the slop removal plan to temp/id-slop/ directory
Provide file paths and line numbers for each finding
Run dry walkthrough on the generated plan
Categorize slop by type for prioritized removal

Slop Categories

Category 1: Phase Reference Comments (HIGH PRIORITY)

Comments mentioning numbered phases from AI implementation plans that won't make sense to future readers.

Patterns to detect:

Phase [0-9] in comments or docstrings
# Phase 1:, # Phase 2:, etc.
References to "implementation phase" or "migration phase" with numbers
Part of Phase X comments

Example slop:

# Phase 5: Migrate Checkpoint and Session Management
def migrate_session():  # Part of Phase 2 migration

Category 2: Backward Compatibility Hacks (HIGH PRIORITY)

Parameters or code kept solely for "API compatibility" that's no longer needed.

Patterns to detect:

kept for API compatibility
kept for backward compatibility
unused but kept for
ignored - kept for
Parameters that are documented as "unused" or "ignored"

Example slop:

use_file_lock: bool = True,  # Ignored - kept for API compatibility
log_dir: Optional[Path] = None,  # Ignored - kept for API compatibility

Read the full file on GitHub · 373 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.

9d ago First seen · 373 lines · 77 tokens per session scan A 4f7dfc6fd985

Subscribe to this mod's changes

id-slop is a skill published in the GitHub repository TalonT-Org/AutoSkillit (5 stars, last pushed today), licensed MIT. It adds 77 tokens to every session and 2,680 once invoked, about $0.0004 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.

Code review

autoreview

Pre-commit/ship code review: Codex default; optional Claude or Pi.

openclaw/clawhub · 20 tokens

rework-rate

Measure and interpret PR rework rate — the emerging 5th DORA metric.

bradygaster/squad · 20 tokens

omh-code-review

This is a Hermes-native code-review workflow skill.

rlaope/oh-my-hermes · 46 tokens

revdiff-plan

Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…

umputun/revdiff · 84 tokens

code-reviewer

Code review specialist focused on patterns, bugs, security, and performance.

RightNow-AI/openfang · 17 tokens

agent-teams-simplify-and-harden

Implementation + audit loop using parallel agent teams with structured simplify, harden, and document passes. Spawns implementation agents to do the work, then audit agents to find complexity, security gaps, and spec deviations, then loops until code compiles cleanly, all tests pass, and auditors find zero issues or…

LeoYeAI/openclaw-master-skills · 115 tokens

AutoSkillit: Skill for Claude Code