che-ical-mcp: Skill for Claude Code

.agents/skills/spectra-discuss/SKILL.md

spectra-discuss is a skill for Claude Code, Codex from PsychQuant/che-ical-mcp. It costs 16 tokens per session (2,431 once invoked), scanned A, original, MIT.

A focused discussion workflow for reaching a conclusion about a design question, problem, architecture decision, or proposed change.

In plain words
What is it for?
Use it to explore options, inspect relevant code, clarify vague ideas, and record a final conclusion or design proposal.
Why use it?
It gives technical conversations a clear goal and prevents them from drifting without a decision, while keeping implementation separate.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents); $skill-name invocation.

This is PsychQuant/che-ical-mcp's own configuration. It tells Claude Code and Codex how to work on che-ical-mcp 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 che-ical-mcp configures →

Reuse

Borrowing it

Nothing to install: this file belongs to PsychQuant/che-ical-mcp. 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/PsychQuant/che-ical-mcp/main/.agents/skills/spectra-discuss/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/PsychQuant/che-ical-mcp

Made for: Claude Code, Codex.

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 spectra-discuss

README.md
[![agentmods](https://agentmods.dev/badge/skills/psychquant/che-ical-mcp/spectra-discuss/github.svg)](https://agentmods.dev/skills/psychquant/che-ical-mcp/spectra-discuss)
Your own site
<a href="https://agentmods.dev/skills/psychquant/che-ical-mcp/spectra-discuss"><img src="https://agentmods.dev/badge/skills/psychquant/che-ical-mcp/spectra-discuss/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 spectra-discuss

Your own site · 80×15
<a href="https://agentmods.dev/skills/psychquant/che-ical-mcp/spectra-discuss"><img src="https://agentmods.dev/badge/skills/psychquant/che-ical-mcp/spectra-discuss.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 16 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,431 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00016 $0.02431
Opus 5 $0.00008 $0.01215
Sonnet 5 $0.00003 $0.00486
Haiku 4.5 $0.00002 $0.00243

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

Security

Grade A, and why

spectra-discuss 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.

.agents/skills/spectra-discuss/SKILL.md · 243 lines

How it starts

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

Have a focused discussion about a topic and reach a conclusion.

IMPORTANT: Discuss mode is for thinking, not implementing. You may read files, search code, and investigate the codebase, but you must NEVER write code or implement features. If the user asks you to implement something, remind them to exit discuss mode first (e.g., start a change with $spectra-propose). You MAY create Spectra artifacts (proposals, designs, specs) if the user asks—that's capturing thinking, not implementing.

This is a task-oriented discussion. Every discussion has a topic, works toward a goal, and ends with a clear conclusion. Unlike open-ended exploration, discuss mode converges.

Input: The argument after $spectra-discuss is the topic. Could be:

  • A design question: "should we use WebSockets or SSE?"
  • A problem to solve: "the auth system is getting unwieldy"
  • A change name: "add-dark-mode" (discuss in context of that change)
  • An architecture decision: "how to structure the plugin system"
  • A vague idea that needs sharpening: "real-time collaboration"

Before You Speak

Before asking anything, do a quick codebase scout to decide how to run this discussion.

Step 1: Extract search terms

Pull 2-5 keywords from the user's topic. For "search should support fuzzy matching", that's search, fuzzy, match. For "should we add a plugin system", that's plugin, extension, module.

Step 2: Scout the codebase

Use Grep and Glob to find related source files (not docs, not tests — source code). Spend no more than a few seconds on this. Read up to 5 of the most relevant files found.

Step 3: Pick a mode

  • 3+ related source files foundAssumptions mode: you have enough context to form opinions. List your assumptions, let the user correct.
  • Fewer than 3 related source files foundInterview mode: not enough code to base assumptions on. Fall through to "How to Discuss" below and ask questions one at a time.

Announce which mode you picked and why: "Found search.rs, SearchPanel.svelte, search-store.ts — I have enough context to list my assumptions." or "Didn't find much related code — I'll ask questions instead."

Read the full file on GitHub · 243 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. 12d ago First seen · 243 lines · 16 tokens per session scan A c0ded59a7b49

Subscribe to this mod's changes

spectra-discuss is a skill published in the GitHub repository PsychQuant/che-ical-mcp (35 stars, last pushed 3d ago), licensed MIT. It adds 16 tokens to every session and 2,431 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.

Related

Other skills, from other repositories

apple-pim

Native macOS personal information management for calendars, reminders, contacts, and local Mail.app. Use when the user wants to schedule meetings, create events, check their calendar, create or complete reminders, look up contacts, find someone's phone number or email, manage tasks and to-do lists, triage local…

omarshahine/apple-pim · 83 tokens

apple-calendar-cli

You have access to apple-calendar-cli, a command-line tool for managing Apple Calendar events via EventKit on macOS.

sichengchen/apple-calendar-cli · 0 tokens

macos-harness

Control a whole Mac from one persistent Python session with screenshots, PID-targeted input, an animated virtual pointer, targeted Apple Accessibility, Apple Events, Browser Harness CDP, and filesystem access. Use for native, Electron, browser, dialog, file, or cross-app tasks without moving the physical cursor or…

browser-use/macos-harness · 71 tokens

findmy

Query Find My friend locations on macOS via the findmy-cli plugin tools. Returns name, coarse location (city, state), staleness, and distance for everyone in the FindMy.app People sidebar. Use when the user asks "where is X", "is X home", "how far is X", or wants a location refresh.

omarshahine/findmy-cli · 74 tokens

fetch-weather-report

Fetch the current weather forecast for a specified location and return a structured summary.

prakhar1114/ai_mime · 19 tokens

macos-control

Control macOS GUI applications via mouse automation, keyboard input, screenshots, image recognition, and AppleScript execution. Use when you need to interact with macOS app UIs, take screenshots, click buttons, type text, scroll, drag, or locate images on screen.

NakaokaRei/SwiftAutoGUI · 58 tokens