A skill for creating, reviewing, checking, maintaining, and exporting skills for coding agents. It focuses on the instruction files and supporting structure that define how an agent skill works.

Use it to author or review SKILL.md files, validate skill packages, maintain shared copies, and export skills to repositories.

Skill files can contain formatting mistakes, routing errors, or checks that fail silently. This provides workflows for finding and correcting those problems.

skills-guru — Skill for Claude Code by izkreny/agentifico

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 izkreny/agentifico --skill skills-guru

Clone the repo

git clone --depth 1 https://github.com/izkreny/agentifico

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/izkreny/agentifico/skills-guru/github.svg)](https://agentmods.dev/skills/izkreny/agentifico/skills-guru)

Your own site

<a href="https://agentmods.dev/skills/izkreny/agentifico/skills-guru"><img src="https://agentmods.dev/badge/skills/izkreny/agentifico/skills-guru/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/izkreny/agentifico/skills-guru"><img src="https://agentmods.dev/badge/skills/izkreny/agentifico/skills-guru.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 1,811 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.00105	$0.01811
Opus 5.5	$0.00042	$0.00724
Sonnet 5.5	$0.00021	$0.00362
Haiku 4.5	$0.00011	$0.00181

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

Security

Grade A, and why

skills-guru 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 17d ago.

The scan reads SKILL.md. This mod also ships 19 executable files (scripts/check.js, scripts/lint-config.js, scripts/rules/frontmatter.js, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

skills/skills-guru/SKILL.md · 80 lines

How it starts

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

Tools used: Read / Grep / Glob to inspect existing skills, Write / Edit to author them, Bash(node:*) for the check in scripts/, which runs Vale with the prose rules in assets/, npm for the one-time install of what the check needs and for its suite and lint, and skills for install and updates, both left out of allowed-tools so that each command prompts, Bash(gh:*) for repository visibility during export and, with git, for reading findings and fix commits when a phrase list grows.

This skill was invoked with the argument: $ARGUMENTS

This is a routing skill. Read $ARGUMENTS and the conversation context, pick exactly one workflow, read that workflow file, and follow its instructions inline.

All paths below are relative to this skill's own directory. Resolve them against wherever this skill is installed rather than assuming a location. A fenced command is different, because whoever pastes it stands in their own working directory rather than in the skill: there the skill's own files are named through <skill-dir>, the placeholder workflows/new.md defines for the directory this skill is installed to, and every workflow here uses that one placeholder rather than a bare scripts/... that runs only from inside the skill.

Where skills live

Keep one canonical copy in an agent-neutral location such as <home-dir>/.agents/skills/<name>/, and symlink each agent's skills directory to it as needed: one file then serves every agent, and no copy drifts. Each agent reads its own directory; Claude Code, for example, reads <home-dir>/.claude/skills/<name>/SKILL.md. When a workflow below says "the skills directory", resolve it for the agent in use.

The facts every workflow here depends on

The description is the whole trigger surface

Only the frontmatter is read before a skill loads. As far as discovery is concerned the body does not exist, so every phrase that should cause the skill to fire has to appear in description:. A trigger documented only in the body will never fire, because nothing reads the body until something has already decided to load it.

Read the full file on GitHub · 80 lines

Files

What ships with it

45 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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.

17d ago Changed · +1 lines 28dda410ac49
18d ago First seen · 79 lines · 105 tokens per session scan A a09a9a7accc4

Subscribe to this mod's changes

skills-guru is a skill published in the GitHub repository izkreny/agentifico (2 stars, last pushed 10d ago), licensed MIT. It adds 105 tokens to every session and 1,811 once invoked, about $0.0004 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-09-30.

Building agents

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

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens

systematic-debugging

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

obra/superpowers · 21 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

component-fixtures

Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.