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.
curl -O https://raw.githubusercontent.com/xsovad06/sova/main/.agents/skills/sova-develop/SKILL.mdgit clone --depth 1 https://github.com/xsovad06/sovaWrote 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/skills/xsovad06/sova/sova-develop)<a href="https://agentmods.dev/skills/xsovad06/sova/sova-develop"><img src="https://agentmods.dev/badge/skills/xsovad06/sova/sova-develop/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/skills/xsovad06/sova/sova-develop"><img src="https://agentmods.dev/badge/skills/xsovad06/sova/sova-develop.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.00022 | $0.01324 |
| Opus 5.5 | $0.00009 | $0.00530 |
| Sonnet 5.5 | $0.00004 | $0.00265 |
| Haiku 4.5 | $0.00002 | $0.00132 |
Grade A, and why
sova-develop 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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Develop the requested feature or fix, then verify with tests.
Instructions
You are a development agent. Your job is to implement the requested changes and verify they work. You are an expert in the project's tech stack (see CLAUDE.md and AGENTS.md for conventions).
Task to develop: the arguments provided when this skill is invoked
Core Principles
- Simplicity first: Make the smallest, simplest change possible
- Readability over cleverness: Code should be instantly understandable
- Match existing patterns: Use the project's conventions, not generic patterns
- Consistency: Match existing codebase style exactly
- Testability: Code MUST be testable; non-negotiable
- Proper logging: Add meaningful logs for debugging and monitoring
- Scout rule: Leave every file you touch better than you found it
Workflow
Step 1: Understand the Context
- Check for an approved spec: look for
.claude/specs/{issue-number}-*.md(where issue-number matchesthe arguments provided when this skill is invokedif it's a number). If a spec exists withStatus: approved, read it and use it as primary task context. The spec's steps, file references, and edge cases take precedence over ad-hoc exploration. When spec context is provided inline (belowthe arguments provided when this skill is invoked), use it directly. Do NOT re-fetch the raw issue body from the tracker, as the spec already encodes the same intent in distilled form. - Read the project's CLAUDE.md and AGENTS.md for conventions
- Read agent memory files if they exist:
.claude/agent-memory/MEMORY.mdand.claude/agent-memory/common-mistakes.md- The cookbook: when
.claude/agent-memory/cookbook/exists, read itsREADME.mdindex 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
- Identify which module(s) this work touches and read relevant source code
- Understand the existing patterns before writing any code
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.
- 9d ago Changed · +4 lines cf39724e6ac0
- 14d ago Changed a096d08b0dff
- 16d ago Changed · +5 lines 7fbcef698eef
- 22d ago First seen · 98 lines · 22 tokens per session scan A ec4de27827ea
sova-develop is a skill published in the GitHub repository xsovad06/sova (2 stars, last pushed today), licensed Apache-2.0. It adds 22 tokens to every session and 1,324 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.
Other skills, from other repositories
remove-ai-slops
Removes AI-generated code smells from branch changes or an explicit file list behind regression tests. Use when the user asks to clean up, deslop, or remove AI-slop patterns from recent changes.
review-work
Post-implementation gate review: run manual QA on the real surface yourself, then launch ONE gate reviewer (never a panel) to audit goal, constraints, code quality, security, missed context, and QA evidence. Use before a PR handoff or when the user explicitly asks to review completed work.
include-test-files-that-assert-on-behavior-being-changed-in-decl
When delegating a task affected by this skill, include.
check
Auto-fix lint and formatting, then report types and tests. Run before every commit.
code-guidelines-go
Go 1.24–1.27 coding guidelines for the dimetron/pi-go AI agent runtime. Use this skill whenever writing, reviewing, or refactoring ANY Go code in pi-go. This covers idiomatic style, error handling, concurrency, project layout, testing (table-driven, fuzz, benchmarks, synctest), new stdlib usage, golangci-lint v2…
vhs-e2e-gif
Record a test run, a TUI session, or any terminal command as a GIF with VHS and attach it to a GitHub PR as a release-hosted asset, never a repo commit. Use when asked to record an e2e run, demo a fix on a PR, attach a GIF or screen recording to a pull request, show a test passing visually, or produce a terminal…