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 basher83/lunar-claude/plugin install omni-scaleWrote 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/basher83/lunar-claude/analyze-spec)<a href="https://agentmods.dev/commands/basher83/lunar-claude/analyze-spec"><img src="https://agentmods.dev/badge/commands/basher83/lunar-claude/analyze-spec.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.00000 | $0.00633 |
| Opus 5 | $0.00000 | $0.00316 |
| Sonnet 5 | $0.00000 | $0.00127 |
| Haiku 4.5 | $0.00000 | $0.00063 |
Grade A, and why
analyze-spec 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 3d 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analyze Spec
Generate a deployment plan using soft guidelines with anchored outputs.
Variables
PLAN_OUTPUT_DIRECTORY: ${CLAUDE_PROJECT_DIR}/.claude/
Context
Up to two specs may be given, only one spec is required to proceed.
Spec files: @${CLAUDE_PLUGIN_ROOT}/specs/$1 @${CLAUDE_PLUGIN_ROOT}/specs/$2
Plan template: @${CLAUDE_PLUGIN_ROOT}/templates/plan-template.md
Instructions
- Create an implementation plan that is:
- Concise enough to scan quickly
- Detailed enough to execute effectively
- Structured however best fits the content
- Cover: problem, solution, constraints, phases, blockers, risks
- Required sections must appear exactly as specified:
## Next Action
**Phase:** [N]
**Task:** [Specific, concrete step]
**Command:** [Actual command or file to create]
## Critical Files
| File | Why Critical |
|------|--------------|
| [path] | [reason] |
- Save the complete implementation plan to
PLAN_OUTPUT_DIRECTORY/plan.local.md
Workflow
-
Readiness Check (output before proceeding):
- What do I know from loaded context? (structure, patterns, constraints)
- What's unclear or missing for this spec?
- Planned vs Actual: Compare any planned counts/values against actual_distribution, exit_criteria, or live cluster state. Flag discrepancies as "Spec needs reconciliation"
- Key risks I can already identify
- Confidence: X/5 - If < 4, use AskUserQuestion to clarify before proceeding
-
Understand: Focus on the requirements provided and apply your assigned perspective throughout the design process
-
Explore Thoroughly:
- Read any files provided to you in the initial prompt
- Find existing patterns and conventions using GLOB, GREP, and READ tools
- Understand the current architecture
-
Design:
- Create implementation approach based on your perspective
- Determine phases, dependencies, execution order
- Consider trade-offs and architectural decisions
-
Detail the Plan:
- Provide step-by-step implementation strategy
- Identify dependencies and sequencing
- Anticipate potential challenges
- Let structure adapt to content—don't force sections that don't fit
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.
- 3d ago First seen · 91 lines · 0 tokens per session scan A 8c5ca1398314
analyze-spec is a command published in the GitHub repository basher83/lunar-claude (22 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 633 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-09-03.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.