agentrig: Skill for Claude Code

.agents/skills/log-gotcha/SKILL.md

log-gotcha is a skill for Claude Code from doidor/agentrig. It costs 25 tokens per session (280 once invoked), scanned A, original, MIT.

A rule for recording newly discovered technical problems or surprising behavior in a repository wiki before handing work to a reviewer.

In plain words
What is it for?
Use it after finding a non-obvious runtime, framework, workflow, or repository issue that future contributors should know about.
Why use it?
It prevents later agents from repeating the same mistake. The rule focuses entries on real gotchas, such as flaky tests, hidden library behavior, or cross-file dependencies.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: installed under .agents/ (shared by several agents).

This is doidor/agentrig's own configuration. It tells Claude Code how to work on agentrig itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything agentrig configures →

Reuse

Borrowing it

Nothing to install: this file belongs to doidor/agentrig. 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/doidor/agentrig/main/.agents/skills/log-gotcha/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/doidor/agentrig

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 log-gotcha

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/doidor/agentrig/log-gotcha"><img src="https://agentmods.dev/badge/skills/doidor/agentrig/log-gotcha.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 25 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 280 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.00025 $0.00280
Opus 5.5 $0.00010 $0.00112
Sonnet 5.5 $0.00005 $0.00056
Haiku 4.5 $0.00003 $0.00028

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

Security

Grade A, and why

log-gotcha 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 29d 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.

.agents/skills/log-gotcha/SKILL.md · 23 lines

What it actually says

Log a gotcha

When a non-obvious behavior, failure, or instruction gap affects your work, use an existing wiki or knowledge base immediately. If none exists, report the observed behavior, supporting evidence, and prevention to the human; do not install a wiki just for this skill.

  1. If a knowledge base exists, search it for an existing entry. Improve that entry if it already covers the issue; do not add duplicate advice or style preferences.
  2. If a knowledge base exists and no entry covers the issue, create a short entry with the observed symptom, actual cause, fix, and one-line prevention. Follow the repository's existing format and index; in this repository, use .agents/wiki/_TEMPLATE.md and .agents/wiki/index.md.
  3. If a rule or skill should have prevented the same failure, sharpen that instruction and check whether the new wording would have changed the original outcome.
  4. Verify a wiki entry is in your diff when there is a wiki; otherwise include the evidence in your handoff. Do not wait until after handoff to record or report the gotcha.
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. 29d ago Changed · -46 lines · -15 tokens per session ba6ff5dd2afe
  2. 2mo ago First seen · 69 lines · 40 tokens per session scan A de432c5255d8

Subscribe to this mod's changes

log-gotcha is a skill published in the GitHub repository doidor/agentrig (5 stars, last pushed 28d ago), licensed MIT. It adds 25 tokens to every session and 280 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-08-31.

Related

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…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

vercel/next.js · 95 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens

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…

vercel/next.js · 83 tokens