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.
git clone --depth 1 https://github.com/jtprogru/bear-skillsWrote 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.
[](https://agentmods.dev/commands/jtprogru/bear-skills/bear-stats)<a href="https://agentmods.dev/commands/jtprogru/bear-skills/bear-stats"><img src="https://agentmods.dev/badge/commands/jtprogru/bear-skills/bear-stats.svg" alt="Measured on agentmods" height="20"></a>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.00015 | $0.00195 |
| Opus 5 | $0.00008 | $0.00097 |
| Sonnet 5 | $0.00003 | $0.00039 |
| Haiku 4.5 | $0.00002 | $0.00019 |
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 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.
What it actually says
Покажи статистику использования скиллов.
bear-skills stats
Если в $ARGUMENTS передано число — ограничь период: bear-skills stats --since $ARGUMENTS.
Разбирая вывод, различай три причины нуля вызовов: скилл свежий и повода не было; описание плохое и модель скилл не находит; скилл не нужен.
Второе от третьего отличается только вопросом пользователю — возникала ли такая задача за период. Задай его, прежде чем предлагать удаление.
Напомни главное: скиллы конкурируют за срабатывание описаниями, поэтому мёртвый скилл ухудшает работу живых. Ничего не удаляй сам.
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.
- 6d ago First seen · 19 lines · 15 tokens per session scan A a82f6e3029c7
bear-stats is a command published in the GitHub repository jtprogru/bear-skills (1 stars, last pushed 19d ago), licensed MIT. It adds 15 tokens to every session and 195 once invoked, about $0.0001 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.
Other commands, from other repositories
address
Address code review feedback — corroborate, validate, and implement changes from a review's final.md.
map
Generate a Code Review Map to help navigate large, complex changesets.
post
Post the current OCR review to a GitHub PR.
show
Display a past OCR review session.
fleet
Show the Fleet Deck board URL and a live summary of every Claude Code session on this machine.
history
List past OCR review sessions.