bear-stats

bear-stats is a skill for Claude Code from jtprogru/bear-skills. It costs 112 tokens per session (831 once invoked), scanned A, original, MIT.

A statistics tool for skills that reads past Claude Code session logs and counts which skills were actually used. It separates unused new skills, skills with poor descriptions, and skills that are not needed.

In plain words
What is it for?
Use it to see skill usage over all time or a recent period, identify skills that never triggered, compare competing skills, and decide what to improve or remove.
Why use it?
It replaces guesses about a skill collection with evidence from previous sessions and helps identify dead or hard-to-discover skills.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions Claude Code.

Part of the bear-skills plugin — 42 skills, 3 commands, 11 agents, 1 hook shipped together

Good fit Use it to see skill usage over all time or a recent period, identify skills that never triggered, compare competing skills, and decide what to improve or remove.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jtprogru/bear-skills/bear-stats
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 jtprogru/bear-skills --skill bear-stats
Clone the repo
git clone --depth 1 https://github.com/jtprogru/bear-skills

Made for: Claude Code.

Or install bear-skills, the plugin that ships this one along with the rest of its 42 skills, 3 commands, 11 agents, 1 hook.

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 bear-stats

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/jtprogru/bear-skills/bear-stats"><img src="https://agentmods.dev/badge/skills/jtprogru/bear-skills/bear-stats.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 112 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 831 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.00112 $0.00831
Opus 5 $0.00056 $0.00415
Sonnet 5 $0.00022 $0.00166
Haiku 4.5 $0.00011 $0.00083

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

Security

Grade A, and why

bear-stats 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 8d 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.

domains/bear/skills/bear-stats/SKILL.md · 54 lines

How it starts

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

bear-stats — Что реально работает

Данные

bear-skills stats              # за всё время
bear-skills stats --since 30   # за последние 30 дней

Команда читает логи сессий Claude Code и считает фактические вызовы скиллов. Это факт, а не оценка — но факт про прошлое, поэтому у свежих скиллов ноль по определению.

Как читать

Скиллы с вызовами — рабочая часть коллекции. Порядок по частоте показывает, вокруг чего на самом деле крутится работа. Часто расходится с ожиданиями.

Ни разу не сработавшие — три разных случая, и их важно различать:

  1. Свежие. Добавлены недавно, повода не было. Ничего не значит.
  2. Плохое описание. Задача возникала, но модель скилл не нашла. Признак: пользователь помнит, как делал это руками или через другой скилл. Лечится переписыванием description под живые формулировки.
  3. Не нужен. Задача не возникает. Кандидат на удаление.

Различить второй и третий случай можно только спросив пользователя: «за последние месяцы ты писал постмортемы?» Если писал, а скилл не срабатывал — проблема в описании, а не в скилле.

Чужие скиллы в выводе показывают, что ещё конкурирует за срабатывание. Чужой скилл с высокой частотой на территории нашего домена — повод посмотреть, не перехватывает ли он триггеры.

Что делать с результатом

Мёртвый скилл — не безобидный балласт. Скиллы конкурируют за срабатывание описаниями, и чем их больше, тем хуже точность выбора. Удаление ненужного улучшает работу оставшихся.

Предложи конкретное действие по каждому мёртвому: переписать описание, снять с установки (bear-skills uninstall skill:<имя>) или удалить из репозитория. Не сноси ничего сам.

Границы

Считаются только явные вызовы скиллов из логов. Работа, где модель применила знание из правила или сделала задачу без скилла, сюда не попадает — и это нормально: скилл, который не вызывался, но чьи правила соблюдались, всё равно не оправдывает места в каталоге.

Логов может не быть вовсе (новая машина, другой агент). Тогда так и скажи, а не выдавай пустой результат за «всё мертво».

Read the full file on GitHub · 54 lines

Files

What ships with it

1 file 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.

  1. 8d ago First seen · 54 lines · 112 tokens per session scan A 953e3324c6a2

Subscribe to this mod's changes

bear-stats is a skill published in the GitHub repository jtprogru/bear-skills (1 stars, last pushed 21d ago), licensed MIT. It adds 112 tokens to every session and 831 once invoked, about $0.0006 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

content-planner

GSC-driven content calendar. Pulls real Search Console data, finds the highest click-potential opportunities (striking-distance queries at positions 5-20, unanswered query intent, related-keyword expansions), and produces a dated, prioritized content calendar — ready to hand to /content-writer. Use when the user asks…

nowork-studio/notfair-plugin · 123 tokens

setup-cms

Connect a CMS to notfair SEO tools. Guides users through configuring WordPress, Strapi, Contentful, or Ghost — tests the connection, and writes credentials to .env.local. Once set up, seo-analysis automatically cross- references CMS content against Google Search Console data. Use whenever the user says "connect my…

nowork-studio/notfair-plugin · 111 tokens

broken-link-checker

Scans a website to find broken links (404s, 500s). Crawls internal pages, identifies broken outbound links, and reports source pages for easy fixing. Use this when the user asks to "check for broken links", "find 404s", "audit my links", or "is my site healthy".

nowork-studio/notfair-plugin · 72 tokens

google-ads-audit

Google Ads account audit and business context setup. Run this first — it gathers business information, analyzes account health, and saves context that all other ads skills reuse. Trigger on "audit my ads", "ads audit", "set up my ads", "onboard", "account overview", "how's my account", "ads health check", "what should…

nowork-studio/notfair-plugin · 114 tokens

google-ads-copy

Generate and A/B test Google Ads copy. Use when asked to write ad copy, headlines, descriptions, create ad variants, test ad messaging, improve CTR, or generate RSA (Responsive Search Ad) components. Trigger on "ad copy", "write ads", "headlines", "descriptions", "RSA", "responsive search ad", "ad text", "ad…

nowork-studio/notfair-plugin · 121 tokens

hreflang-international

International / multilingual SEO audit focused on hreflang correctness. Detects and diagnoses the most common (and ranking-damaging) hreflang mistakes: missing or broken return tags, wrong language/region codes, missing x-default, self-referencing errors, conflicts between hreflang and canonical, and inconsistent…

nowork-studio/notfair-plugin · 242 tokens