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/CES-Ltd/LumiWrote 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/ces-ltd/lumi/octo-spec)<a href="https://agentmods.dev/commands/ces-ltd/lumi/octo-spec"><img src="https://agentmods.dev/badge/commands/ces-ltd/lumi/octo-spec/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/ces-ltd/lumi/octo-spec"><img src="https://agentmods.dev/badge/commands/ces-ltd/lumi/octo-spec.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.00014 | $0.00389 |
| Opus 5 | $0.00007 | $0.00195 |
| Sonnet 5 | $0.00003 | $0.00078 |
| Haiku 4.5 | $0.00001 | $0.00039 |
Grade A, and why
octo-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 10d 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
Spec - NLSpec Authoring
INSTRUCTIONS FOR CLAUDE
When the user invokes this command (e.g., /octo:spec <arguments>):
CORRECT - Use the Skill tool:
Skill(skill: "octo:spec", args: "<user's arguments>")
INCORRECT:
Skill(skill: "flow-spec", ...) ❌ Wrong! Internal skill name, not resolvable by Skill tool
Task(subagent_type: "octo:spec", ...) ❌ Wrong! This is a skill, not an agent type
Auto-loads the spec skill for NLSpec authoring.
Quick Usage
Just describe what you want to specify:
"Specify a user authentication system"
"Create a spec for real-time chat"
"Define requirements for payment processing"
What Is Spec?
NLSpec (Natural Language Specification) authoring:
- Structured specification from multi-AI research
- Question-first approach to understand scope
- Probe-based research for domain context
- Validated completeness checking
What You Get
- Multi-AI research (Claude + Gemini + Codex) on the domain
- Structured NLSpec with behaviors, actors, constraints
- Adversarial completeness challenge from a second provider (surfaces missing requirements and overlooked edge cases)
- Completeness validation with scoring
- Saved specification file for downstream workflows
When To Use
- Starting a new project from scratch
- Defining requirements before implementation
- Creating a specification for handoff
- Establishing acceptance criteria upfront
Natural Language Examples
"Specify an OAuth 2.0 authentication system"
"Create a spec for a REST API gateway"
"Define the requirements for a CI/CD pipeline"
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.
- 10d ago First seen · 65 lines · 14 tokens per session scan A 13893a68fde6
octo-spec is a command published in the GitHub repository CES-Ltd/Lumi (31 stars, last pushed 4mo ago), licensed MIT. It adds 14 tokens to every session and 389 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
refactor-clean
You are a code refactoring expert specializing in clean code principles, SOLID design patterns, and modern software engineering best practices. Analyze and refactor the provided code to improve its quality, maintainability, and performance.
deps-audit
Audit project dependencies for vulnerabilities, outdated packages, license conflicts, and supply chain risks — then provide actionable remediation strategies.
workflow-classify
Classify task size (S/M/L/XL) and recommend the appropriate workflow pipeline.
pull-repos
Pull all repos (parent + marketplace clones + configured project repos).
sonarqube
Analyze SonarCloud quality issues for a specific PR.
plan-start
5-phase planning command: PRD analysis, design review, technical decisions, dynamic research team, metrics. Produces a complete implementation plan + ADRs before any code is written.