my-skill

my-skill is a skill for Claude Code from forest6511/claude-code-recipes-v2. It costs 9 tokens per session (215 once invoked), scanned A, original, MIT.

A set of repair notes for fixing common skill-file problems, such as invalid YAML settings, names with unsupported characters, and missing command fallbacks. The input does not clearly describe a complete skill or its overall purpose.

In plain words
What is it for?
Use it when repairing skill metadata or adding a fallback message when a command cannot find the expected pull request.
Why use it?
It can help correct configuration mistakes that stop a skill from being read or used properly.

Skill for Claude Code

Written for Claude Code: dynamic context !`command`.

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.

agentmods
npx agentmods add skills/forest6511/claude-code-recipes-v2/after
Any agent
npx skills add forest6511/claude-code-recipes-v2 --skill after
Clone the repo
git clone --depth 1 https://github.com/forest6511/claude-code-recipes-v2

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 my-skill

README.md
[![agentmods](https://agentmods.dev/badge/skills/forest6511/claude-code-recipes-v2/after.svg)](https://agentmods.dev/skills/forest6511/claude-code-recipes-v2/after)
Your own site
<a href="https://agentmods.dev/skills/forest6511/claude-code-recipes-v2/after"><img src="https://agentmods.dev/badge/skills/forest6511/claude-code-recipes-v2/after.svg" alt="Measured on agentmods" height="20"></a>
Per session 9 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 215 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.00009 $0.00215
Opus 5 $0.00005 $0.00108
Sonnet 5 $0.00002 $0.00043
Haiku 4.5 $0.00001 $0.00021

Measured 6d ago against content hash 8d8e2045fc06, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

my-skill 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 6d 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.

ch09-skills-tips/recipe-51/common-mistakes/after/SKILL.md · 33 lines

What it actually says

修正パターン

YAML構文エラーの修正

値にコロン(:)を含む場合はクォートで囲みます。

nameの修正

# Before: My_Skill
# After:
name: my-skill

小文字、数字、ハイフンのみ使用可能です。

context:forkの修正

ガイドライン型のSkillsにはcontext:forkを使いません。

---
name: api-conventions
---
# context:forkなし(インラインで読み込まれる)

!commandのフォールバック追加

!`gh pr diff 2>/dev/null || echo "現在のブランチにPRが見つかりません。手動で対象を指定してください。"`
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. 6d ago First seen · 33 lines · 9 tokens per session scan A 8d8e2045fc06

Subscribe to this mod's changes

my-skill is a skill published in the GitHub repository forest6511/claude-code-recipes-v2 (5 stars, last pushed 4mo ago), licensed MIT. It adds 9 tokens to every session and 215 once invoked, about $0.0000 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.

Related

Other skills, from other repositories

systematic-debugging

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

obra/superpowers · 21 tokens

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

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