Solaris: Skill for OpenCode

.opencode/skills/solaris-cli-ux/SKILL.md

solaris-cli-ux is a skill for OpenCode from Shivansh779/Solaris. It costs 26 tokens per session (1,637 once invoked), scanned A, original, MIT.

A skill for improving the readability of Solaris's command-line interface, the text-based screen where users interact with the program. It covers Markdown, tables, code blocks, status messages, and layout across terminal widths.

In plain words
What is it for?
Use it to improve terminal rendering, syntax highlighting, progress and error messages, spacing, wrapping, and source presentation.
Why use it?
It addresses output that is hard to read, overflows the terminal, or displays formatted content as raw text.

Skill for OpenCode

Written for OpenCode: installed under .opencode/. Also seen: mentions OpenCode.

This is Shivansh779/Solaris's own configuration. It tells OpenCode how to work on Solaris itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything Solaris configures →

Reuse

Borrowing it

Nothing to install: this file belongs to Shivansh779/Solaris. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/Shivansh779/Solaris/main/.opencode/skills/solaris-cli-ux/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/Shivansh779/Solaris

Made for: OpenCode.

Wrote 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.

agentmods badge for solaris-cli-ux

README.md
[![agentmods](https://agentmods.dev/badge/skills/shivansh779/solaris/solaris-cli-ux/github.svg)](https://agentmods.dev/skills/shivansh779/solaris/solaris-cli-ux)
Your own site
<a href="https://agentmods.dev/skills/shivansh779/solaris/solaris-cli-ux"><img src="https://agentmods.dev/badge/skills/shivansh779/solaris/solaris-cli-ux/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.

agentmods 80×15 button for solaris-cli-ux

Your own site · 80×15
<a href="https://agentmods.dev/skills/shivansh779/solaris/solaris-cli-ux"><img src="https://agentmods.dev/badge/skills/shivansh779/solaris/solaris-cli-ux.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 26 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,637 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00026 $0.01637
Opus 5 $0.00013 $0.00818
Sonnet 5 $0.00005 $0.00327
Haiku 4.5 $0.00003 $0.00164

Measured 5d ago against content hash 2c5e9775ae27, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

solaris-cli-ux 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 5d 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.

.opencode/skills/solaris-cli-ux/SKILL.md · 383 lines

How it starts

The opening of the file, as written. The whole thing — 383 lines — stays where its author put it; the contents beside it link to each section on GitHub.

What I do

  • Inspect Solaris' existing CLI and TUI architecture.
  • Identify problems with AI response readability and terminal presentation.
  • Improve Markdown rendering in the terminal.
  • Render Markdown tables as readable terminal-native tables.
  • Improve code-block presentation and syntax highlighting where appropriate.
  • Improve headings, lists, blockquotes, links, spacing, and line wrapping.
  • Improve status, progress, warning, and error presentation.
  • Improve web-search source presentation where relevant.
  • Research suitable terminal/UI libraries when necessary.
  • Prefer a small number of capable libraries over many tiny dependencies.
  • Preserve Solaris' existing architecture unless a larger change is genuinely justified.
  • Test the resulting CLI experience across different response types and terminal widths.

When to use me

Use this when improving Solaris' command-line or terminal user experience.

Use me when:

  • AI responses are difficult to read.
  • Markdown is being printed as raw text.
  • Tables are difficult to read.
  • Code blocks need better presentation.
  • Long responses overflow or become difficult to navigate.
  • Status/progress output needs improvement.
  • Errors and warnings need clearer presentation.
  • Web-search results or sources need better terminal presentation.
  • The Solaris CLI needs a general UX improvement.

Do not use this skill merely to add decorative styling.

The primary objective is readability and usability.

Core principle

Solaris should treat AI output as content and the terminal as the presentation layer.

Preferred architecture:

AI response
    ↓
Markdown / response content
    ↓
Solaris renderer
    ↓
Terminal

Do not make the AI model responsible for generating ANSI escape sequences or terminal-specific formatting.

Workflow

1. Inspect first

Before changing code, inspect the existing Solaris implementation.

Understand:

  • current TUI architecture
  • response pipeline
  • response printing/rendering
  • existing Markdown handling
  • existing table handling
  • code-block handling
  • spinner/loading implementation
  • status and error output
  • current dependencies

Read the full file on GitHub · 383 lines

Changes

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.

  1. 5d ago First seen · 383 lines · 26 tokens per session scan A 2c5e9775ae27

Subscribe to this mod's changes

solaris-cli-ux is a skill published in the GitHub repository Shivansh779/Solaris (1 stars, last pushed 2d ago), licensed MIT. It adds 26 tokens to every session and 1,637 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-09-05.

Related

Other skills, from other repositories

frontend-design

Design-quality layer for frontend code — typography, color, motion, spatial composition, and avoiding generic "AI slop" aesthetics. Use this as a companion when you are already writing or styling frontend code and want it to look distinctive and production-grade. For building an app, dashboard, tracker, calculator…

vellum-ai/vellum-assistant · 96 tokens

web-artifacts-builder

Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.

ThinkInAIXYZ/deepchat · 64 tokens

ui-html-renderer

Use this specialist for unusually complex stateful HTML, blank/runtime-risk repair, strict source-to-HTML fidelity, reusable component galleries, brand boards, or detailed implementation handoff. Ordinary single-page HTML uses ui-design-executor, which already preserves HTML-default delivery and baseline…

Orkas-AI/Orkas · 4 tokens

product-ui

Use this skill when UI design and UI implementation should happen together. It turns product context into usable frontend screens, components, layout decisions, design-system choices, accessibility rules, and visual polish.

Orkas-AI/Orkas · 2 tokens

frontend-ui-ux-system

A company-level guide for designing web interfaces and user experiences. It covers visual styles, design tokens (named values for colors, spacing, and typography), layout, interaction, accessibility, motion, and review checks.

hashgraph-online/awesome-codex-plugins · 60 tokens

impeccable

Use when the user wants distinctive, production-grade frontend design, anti-generic AI aesthetics, UX critique, technical UI audits, or final polish through bundled Impeccable references and an optional upstream detector CLI.

Peiiii/nextclaw · 47 tokens