sova: Command for Claude Code

.claude/commands/spec.md

spec is a command for Claude Code from xsovad06/sova. It costs 14 tokens per session (2,248 once invoked), scanned A, original, Apache-2.0.

A command that turns a development task or issue into a structured specification before coding begins. A specification records the problem, requirements, design decisions, and planned work.

In plain words
What is it for?
Use it to prepare an implementation plan from a written task, GitHub issue, or Jira ticket.
Why use it?
It moves important decisions into the planning stage, where misunderstandings are cheaper to fix than after implementation starts. It can read tasks from sources such as GitHub or Jira.

Command for Claude Code

Written for Claude Code: user-invocable in frontmatter. Also seen: mentions CLAUDE.md; mentions AGENTS.md.

This is xsovad06/sova's own configuration. It tells Claude Code how to work on sova 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 sova configures →

Reuse

Borrowing it

Nothing to install: this file belongs to xsovad06/sova. 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/xsovad06/sova/main/.claude/commands/spec.md
Clone the repo
git clone --depth 1 https://github.com/xsovad06/sova

Made for: Claude Code.

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 spec

README.md
[![agentmods](https://agentmods.dev/badge/commands/xsovad06/sova/spec/github.svg)](https://agentmods.dev/commands/xsovad06/sova/spec)
Your own site
<a href="https://agentmods.dev/commands/xsovad06/sova/spec"><img src="https://agentmods.dev/badge/commands/xsovad06/sova/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.

agentmods 80×15 button for spec

Your own site · 80×15
<a href="https://agentmods.dev/commands/xsovad06/sova/spec"><img src="https://agentmods.dev/badge/commands/xsovad06/sova/spec.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 14 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,248 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.00014 $0.02248
Opus 5.5 $0.00006 $0.00899
Sonnet 5.5 $0.00003 $0.00450
Haiku 4.5 $0.00001 $0.00225

Measured 14d ago against content hash d2bb8b0e19f6, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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 14d 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.

.claude/commands/spec.md · 279 lines

How it starts

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

Specification

Produce a structured specification document for a task before development starts. Shifts architectural and UX decisions to the cheap planning phase instead of the expensive coding phase.

Task: $ARGUMENTS

Instructions

Step 1: Fetch the Task

If $ARGUMENTS is a text description (not a number or ticket key), use it directly as the problem statement and skip to Step 2.

Determine the task source by running sova config and reading the task_source row (configuration lives in .claude/sova.db, not in a file).

GitHub (the default):

gh issue view $ARGUMENTS --json number,title,body,labels,milestone

JIRA (task_source.type = "jira"):

jira issue view $ARGUMENTS --plain

Extract: title, description, status, linked/blocked tickets, components.

Save the original description verbatim: it will be preserved in the spec.

Early exit (already implemented): if the issue body contains a Research section that concludes the issue is already fully implemented (look for phrases like "already implemented", "already complete", "no remaining work"), write a minimal spec file to .claude/specs/{issue-number}-already-implemented.md with the following content, then stop. Do not explore the codebase or write a full spec:

# Spec: {Issue title}

**Issue**: #{number}
**Status**: approved
**Created**: {YYYY-MM-DD}
**Complexity**: trivial

## Problem

Already implemented per research findings.

## Solution

No changes needed. The research step confirmed this issue is already fully implemented.

Step 2: Read Project Context

Read whatever exists; skip files that are missing:

  • CLAUDE.md and AGENTS.md for project conventions
  • .claude/rules/architecture.md for component overview and design decisions
  • The cookbook for known patterns and past mistakes: the README.md index of .claude/agent-memory/cookbook/ plus the domain files relevant to this task when that directory exists, otherwise .claude/agent-memory/cookbook.md; also .claude/agent-memory/common-mistakes.md if present

Read the full file on GitHub · 279 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. 14d ago Changed · +11 lines d2bb8b0e19f6
  2. 16d ago Changed · +3 lines e89464945c75
  3. 21d ago Changed af9976f63fa7
  4. 1mo ago Changed 22333e46acf2
  5. 1mo ago Changed · -10 lines aee08a4cd3ee
  6. 2mo ago First seen · 275 lines · 14 tokens per session scan A dc6528bf8486

Subscribe to this mod's changes

spec is a command published in the GitHub repository xsovad06/sova (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 14 tokens to every session and 2,248 once invoked, about $0.0001 per session on Opus 5.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-31.