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.
npx agentmods add commands/runkids/skillshare/analyzegit clone --depth 1 https://github.com/runkids/skillshareWhat 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 | $0.00000 | $0.01909 |
| Opus 5 | $0.00000 | $0.00955 |
| Sonnet 5 | $0.00000 | $0.00382 |
| Haiku 4.5 | $0.00000 | $0.00191 |
Grade A, and why
analyze 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 yesterday.
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.
How it starts
The opening of the file, as written. The whole thing — 260 lines — stays where its author put it; the contents beside it link to each section on GitHub.
analyze
Analyze context window usage and skill quality for each target's skills.
skillshare analyze # Interactive TUI (default)
skillshare analyze claude # Details for a single target
skillshare analyze --verbose # Top 10 largest descriptions
skillshare analyze --json # Machine-readable output
skillshare analyze -p # Project mode
When to Use
Optimize Context Budget
Identify which skills consume the most context window tokens:
skillshare analyze # Browse all targets interactively
Compare Across Targets
See how context usage differs between targets (e.g., Claude vs Cursor):
skillshare analyze # Tab to switch targets in TUI
Check Skill Quality
Find skills with missing fields, short descriptions, or no trigger phrases:
skillshare analyze # Lint icons (✗/⚠) appear in TUI
CI/Scripting
Get machine-readable context metrics and lint results:
skillshare analyze --json | jq '.targets[].always_loaded.estimated_tokens'
skillshare analyze --json | jq '.targets[].skills[] | select(.lint_issues | length > 0)'
What It Does
analyze calculates two layers of context cost for each skill:
- Always loaded —
name + descriptionfrom SKILL.md frontmatter (loaded into context on every request for skill matching) - On-demand — Skill body after frontmatter (loaded only when the skill is triggered)
Token estimates use chars / 4 as an approximation.
Skill Quality Lint
In addition to token analysis, analyze runs a built-in lint engine against every skill. Lint rules check SKILL.md structure and description quality, surfacing issues directly in the TUI and JSON output.
| Rule | Severity | What it checks |
|---|---|---|
missing-name |
error | name field is empty or missing |
missing-description |
error | description field is empty or missing |
empty-body |
error | Skill body (after frontmatter) is empty |
description-too-short |
warning | Description under 50 characters |
description-too-long |
warning | Description exceeds 1024-character target limit |
description-near-limit |
warning | Description between 900–1024 characters |
no-trigger-phrase |
warning | Description lacks trigger phrases (e.g. "Use when…") |
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.
- yesterday First seen · 260 lines · 0 tokens per session scan A cda62ca63083
analyze is a command published in the GitHub repository runkids/skillshare (2,597 stars, last pushed 5d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,909 tokens. 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-30.
Other commands, from other repositories
constraints
Define and enforce this project's quality bar — interview, sane defaults, CONSTRAINTS.md.
webperf
Run a web performance audit via the web-performance-auditor persona.
spec
Start spec-driven development — write a structured specification before writing code.
plan
Break work into small verifiable tasks with acceptance criteria and dependency ordering.
pm-arch
Scan project structure and generate Mermaid architecture diagrams + flowcharts under .pm/architecture/.
pm-done
Close a todo (TODO-xxx), sync completed.md, refresh overview.