sova: Skill for Claude Code

.agents/skills/sova-develop-full/SKILL.md

sova-develop-full is a skill for Claude Code, Codex from xsovad06/sova. It costs 31 tokens per session (1,424 once invoked), scanned A, original, Apache-2.0.

An end-to-end workflow for developing a task with test-driven development (TDD), code checks, self-review, and organized commits. TDD means writing a failing test first, then writing code that makes it pass.

In plain words
What is it for?
Use it for a GitHub issue or task description when you need to understand the requirements, claim and implement the work, run tests and lint checks, and prepare clean commits.
Why use it?
Development work can stop at an untested change or leave a messy history that is hard to review. This combines implementation, verification, review, and Git cleanup into one process.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions CLAUDE.md; installed under .agents/ (shared by several agents); mentions AGENTS.md.

This is xsovad06/sova's own configuration. It tells Claude Code and Codex 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/.agents/skills/sova-develop-full/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/xsovad06/sova

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 sova-develop-full

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/xsovad06/sova/sova-develop-full"><img src="https://agentmods.dev/badge/skills/xsovad06/sova/sova-develop-full.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 31 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,424 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.00031 $0.01424
Opus 5.5 $0.00012 $0.00570
Sonnet 5.5 $0.00006 $0.00285
Haiku 4.5 $0.00003 $0.00142

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

Security

Grade A, and why

sova-develop-full 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.

.agents/skills/sova-develop-full/SKILL.md · 106 lines

How it starts

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

Full Development Workflow

Develop a feature or fix end-to-end with TDD, testing, self-review, and clean commit history.

Instructions

Phase 0: Understand the Task

  1. Get the task from the arguments provided when this skill is invoked: either a GitHub Issue number or a task description.
  2. Check for spec (issue numbers only): look for .claude/specs/{issue-number}-*.md.
    • If found with Status: approved: read it. Report: "Using approved spec: {filename}". The sova-develop skill step will follow this spec as its primary guide.
    • If found with Status: draft: warn the user: "Draft spec exists at {filename} but is not approved. Run the sova-spec skill {issue} to review and approve it, or proceed without spec guidance." Wait for user confirmation before continuing (when running headless, with no user to confirm, proceed without spec guidance and say so in the summary).
    • If not found: continue silently. Specs are optional; not every task needs one.
  3. If it's an issue number, fetch details. When an approved spec was found in step 2, it already encodes the task intent in distilled form, so omit body and fetch only the fields this phase still needs (claiming, branch naming, labels):
    # No approved spec:
    gh issue view <ISSUE_NUMBER> --json number,title,body,labels,milestone
    # Approved spec found in step 2:
    gh issue view <ISSUE_NUMBER> --json number,title,labels,milestone
    
  4. Claim the issue (GitHub Issues only):
    # Assign to self
    gh issue edit <ISSUE_NUMBER> --add-assignee @me
    
    If the project uses a GitHub Projects board, move the issue to "In Progress".
  5. Read the project's CLAUDE.md and AGENTS.md for conventions and patterns.
  6. Read agent memory files if they exist:
    • .claude/agent-memory/MEMORY.md and .claude/agent-memory/common-mistakes.md
    • The cookbook: when .claude/agent-memory/cookbook/ exists, read its README.md index and then only the domain files for the modules this work touches (the whole cookbook is too large to load); otherwise read .claude/agent-memory/cookbook.md
  7. Identify which module(s) this work touches and read relevant source code.
  8. Check current branch: if on main/master, create a feature branch before developing, the same way the sova-new-feature skill does (in a dedicated worktree when the project keeps branches under .claude/worktrees/, so the primary checkout stays on the base branch):
    BRANCH=$(git branch --show-current)
    if [ "$BRANCH" = "main" ] || [ "$BRANCH" = "master" ]; then
      echo "On main branch. Create a feature branch before developing."
    fi
    

Read the full file on GitHub · 106 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 2f62914df1b0
  2. 16d ago Changed · +4 lines 951ed1cf586a
  3. 22d ago First seen · 102 lines · 31 tokens per session scan A 08e1c95703e9

Subscribe to this mod's changes

sova-develop-full is a skill published in the GitHub repository xsovad06/sova (2 stars, last pushed today), licensed Apache-2.0. It adds 31 tokens to every session and 1,424 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-10-08.