llm-coding-failure-modes

llm-coding-failure-modes is a skill for Claude Code, Codex from GoldenWing-360/claude-security-skills. It costs 111 tokens per session (3,675 once invoked), scanned B, original, MIT.

A catalogue of recurring ways that coding agents using language models can fail, including agents like Claude Code, Copilot, Cursor, and Windsurf. It covers unsafe bulk changes, ignored safeguards, indirect instructions, exposed secrets, and outdated code patterns.

In plain words
What is it for?
Use it when reviewing AI-written code, designing an agent's instructions, training a team, investigating an incident, or creating a checklist for agent-related code review.
Why use it?
It helps reviewers recognise mistakes that may look reasonable while an agent is working. The examples make it easier to assess how much damage an agent could cause and what to check afterward.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions CLAUDE.md; mentions Claude Code.

Good fit Use it when reviewing AI-written code, designing an agent's instructions, training a team, investigating an incident, or creating a checklist for agent-related code review.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/goldenwing-360/claude-security-skills/llm-coding-failure-modes
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 GoldenWing-360/claude-security-skills --skill llm-coding-failure-modes
Clone the repo
git clone --depth 1 https://github.com/GoldenWing-360/claude-security-skills

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 llm-coding-failure-modes

README.md
[![agentmods](https://agentmods.dev/badge/skills/goldenwing-360/claude-security-skills/llm-coding-failure-modes/github.svg)](https://agentmods.dev/skills/goldenwing-360/claude-security-skills/llm-coding-failure-modes)
Your own site
<a href="https://agentmods.dev/skills/goldenwing-360/claude-security-skills/llm-coding-failure-modes"><img src="https://agentmods.dev/badge/skills/goldenwing-360/claude-security-skills/llm-coding-failure-modes/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 llm-coding-failure-modes

Your own site · 80×15
<a href="https://agentmods.dev/skills/goldenwing-360/claude-security-skills/llm-coding-failure-modes"><img src="https://agentmods.dev/badge/skills/goldenwing-360/claude-security-skills/llm-coding-failure-modes.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 111 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,675 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. 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.00111 $0.03675
Opus 5 $0.00056 $0.01837
Sonnet 5 $0.00022 $0.00735
Haiku 4.5 $0.00011 $0.00367

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

Security

Grade B, and why

llm-coding-failure-modes scanned grade B with 1 finding 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 11d 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.

Recursive force deletemediumDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

**What happens.** Pre-commit hook fails → agent adds `--no-verify`. Rebase produces a conflict → agent runs `git push --force`. `DISALLOW_FILE_EDIT=true` blocks a quick fix → agent flips it to false. `rm -rf node_modules

Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.

llm-coding-failure-modes/SKILL.md · 231 lines

How it starts

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

LLM Coding Failure Modes

This is the antipattern catalog for LLM-assisted development. Every entry is a recurring, observed failure mode — not theoretical risk. Most are subtle when they happen and obvious in hindsight, which is the worst combination.

Pairs with ai-agent-guardrails (how to design agents that don't do these things) and prompt-injection-defense (the input side). This skill is about what to watch for in the wild when an LLM is writing code or taking actions on real systems.

When to invoke

  • Reviewing code written by an LLM agent (yours or a contributor's)
  • Designing or hardening a coding agent's system prompt / harness
  • Onboarding a team to "vibe coding" / LLM-assisted workflows
  • Investigating an incident where an agent caused damage
  • Auditing an existing agent for blast radius before granting more access
  • Writing a code-review checklist that catches LLM-typical mistakes

🔴 Top tier — catastrophic + common

1. Bulk operations without per-item review

What happens. User says "fix the title on the homepage." Agent runs 47 update_post calls across the whole site. User says "clean up the tests." Agent deletes 200 files. The model rationalizes scope expansion as helpfulness.

Where it bites hardest. CMS bulk-edits (Elementor / WordPress sites — entire staging instances destroyed by well-meaning "fix-everything" runs), database migrations, file renames, mass refactors.

Detection in review. A single conversational request that produced > N tool calls in a similar shape. A diff that touches files outside the requested area. Commit messages that say "and refactored adjacent code."

Mitigation.

  • Bound per-conversation tool-call counts for write operations
  • Force delete_post(id) shape over delete_posts(filter) shape
  • Dry-run-first for tier ≥ 3 operations
  • Force a checkpoint / approval before the Nth same-type write call

→ See ai-agent-guardrails for the design patterns.

Read the full file on GitHub · 231 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. 11d ago First seen · 231 lines · 111 tokens per session scan B cbc614adb796

Subscribe to this mod's changes

llm-coding-failure-modes is a skill published in the GitHub repository GoldenWing-360/claude-security-skills (17 stars, last pushed 1mo ago), licensed MIT. It adds 111 tokens to every session and 3,675 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it B with 1 finding (recursive force delete). 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

ux-audit

Walk through a live web app AS a real user to find usability + behavioural bugs that static reviews miss. REQUIRES proof of interaction (typing, clicking, sending, observing) before any verdict — a sweep that didn't interact terminates with verdict 'Incomplete'. Walks threads, exercises every element, runs the…

jezweb/claude-skills · 217 tokens

design-loop

Autonomous multi-page site builder using a baton-passing loop. Each iteration reads a task from .design/next-prompt.md, generates a page in HTML/Tailwind, integrates it into the site, verifies visually, then writes the next task to keep the loop alive. Use whenever the user asks to build an entire site autonomously…

jezweb/claude-skills · 130 tokens

product-showcase

Generate a comprehensive marketing website for a web app — multi-page with real screenshots, animated GIF walkthroughs, feature deep-dives, and workflow demonstrations. Browses the running app, captures screens and sequences, and produces a deployable site that actually teaches people what the product does. Especially…

jezweb/claude-skills · 117 tokens

google-apps-script

Build Google Apps Script automation for Sheets and Workspace. Custom menus, triggers (onEdit / time-driven / form submit), dialogs, sidebars, email batches, PDF export, external API. Use whenever the user wants to automate a Google Sheet, build a Sheets menu / sidebar / dialog, hit a Sheets row from email or a…

jezweb/claude-skills · 89 tokens

cloudflare-api

Hit the Cloudflare REST API directly for operations that wrangler and MCP can't handle well. Bulk DNS, custom hostnames, email routing, cache purge, WAF rules, redirect rules, zone settings, Worker routes, D1 cross-database queries, R2 bulk operations, KV bulk read/write, Vectorize queries, Queues, and fleet-wide…

jezweb/claude-skills · 141 tokens

tanstack-start

Build a full-stack TanStack Start app on Cloudflare Workers from scratch — SSR, file-based routing, server functions, D1+Drizzle, better-auth, Tailwind v4+shadcn/ui. Use whenever the user mentions TanStack Start, asks to scaffold a full-stack Cloudflare app with SSR, wants an SSR dashboard, or asks for a React 19 +…

jezweb/claude-skills · 115 tokens