Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add athola/claude-night-market/plugin install abstractWrote 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/athola/claude-night-market/analyze-skill)<a href="https://agentmods.dev/commands/athola/claude-night-market/analyze-skill"><img src="https://agentmods.dev/badge/commands/athola/claude-night-market/analyze-skill/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.
<a href="https://agentmods.dev/commands/athola/claude-night-market/analyze-skill"><img src="https://agentmods.dev/badge/commands/athola/claude-night-market/analyze-skill.svg" alt="Reviewed on agentmods" width="80" 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.00021 | $0.00572 |
| Opus 5 | $0.00010 | $0.00286 |
| Sonnet 5 | $0.00004 | $0.00114 |
| Haiku 4.5 | $0.00002 | $0.00057 |
Grade A, and why
analyze-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 12d 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.
How it starts
The opening of the file, as written. The whole thing — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analyze Skill Complexity
Analyzes a skill file for complexity metrics and provides modularization recommendations based on the modular-skills framework.
When To Use
Use this command when you need to:
- Assessing skill file complexity before adding content
- Planning modularization strategies
- Checking if a skill needs to be split
- Validating progressive disclosure design
When NOT To Use
Avoid this command if:
- Evaluating skill quality - use /skills-eval instead
- Estimating token usage only - use /estimate-tokens instead
- Creating new skills - use /create-skill instead
Usage
# Analyze specific skill file
/analyze-skill skills/my-skill/SKILL.md
# Analyze skill directory
/analyze-skill skills/my-skill
# Analyze current directory (if in a skill folder)
/analyze-skill .
What It Analyzes
The analyzer evaluates several complexity dimensions:
Metrics Collected
- Line count: Total lines vs threshold (default: 150)
- Word/character count: Content density indicators
- Theme sections: Number of
#level headings - Subsections: Number of
##level headings - Code blocks: Embedded code examples
- Estimated tokens: Context window impact
Recommendations Generated
- MODULARIZE: File exceeds thresholds, should be split
- CONSIDER: Approaching limits, evaluate for future growth
- OK: Within acceptable complexity bounds
Examples
/analyze-skill skills/modular-skills/SKILL.md
# Output:
# === Analysis for: skills/modular-skills/SKILL.md ===
# Line count: 180 (threshold: 150)
# Estimated tokens: 1,847
# === Recommendations ===
# MODULARIZE: File exceeds threshold (180 > 150)
# GOOD: Token usage in optimal range
/analyze-skill skills/skills-eval --verbose
# Includes detailed section breakdown
Integration with Modular Skills
This command is the first step in the modular-skills workflow:
- Analyze → Use this command to assess complexity
- Design → Plan module structure based on recommendations
- Estimate → Use
/estimate-tokensfor token budgeting - Validate → Use
/skills-evalfor quality checks
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.
- 12d ago First seen · 86 lines · 21 tokens per session scan A e8b077938a14
analyze-skill is a command published in the GitHub repository athola/claude-night-market (337 stars, last pushed yesterday), licensed MIT. It adds 21 tokens to every session and 572 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-30.
Other commands, from other repositories
analyze-codebase
Generate comprehensive analysis and documentation of entire codebase.
prompt
System instructions for writing effective prompts. Apply when generating commands, skills, agents, or any LLM instructions.
anti-slop-designer
Use when a UI looks machine-made rather than decided. Violet gradients, glassmorphism everywhere, identical cards in a grid, untouched shadcn or Material defaults, emoji bullets, or copy stuffed with seamless and unlock.
design-critic
Use when you want an honest read on a design instead of encouragement. What is wrong, ranked by severity, with the reason attached. Works on a screenshot, a mockup, or a described screen.
ui-copywriter
Use when writing marketing or landing copy. Headlines, hero copy, CTAs, value propositions and section copy that sound like a person making a specific claim rather than a template being filled in.
data-visualization-specialist
Use when a chart misleads or confuses. Wrong chart type for the data, a truncated axis, colour that encodes nothing, unreadable labels on mobile, or charts no screen reader can use.