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-full/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-full)<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.
<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>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.00031 | $0.01424 |
| Opus 5.5 | $0.00012 | $0.00570 |
| Sonnet 5.5 | $0.00006 | $0.00285 |
| Haiku 4.5 | $0.00003 | $0.00142 |
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.
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
- Get the task from
the arguments provided when this skill is invoked: either a GitHub Issue number or a task description. - 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}". Thesova-developskill 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 thesova-specskill {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.
- If found with
- 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
bodyand 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 - Claim the issue (GitHub Issues only):
If the project uses a GitHub Projects board, move the issue to "In Progress".# Assign to self gh issue edit <ISSUE_NUMBER> --add-assignee @me - Read the project's CLAUDE.md and AGENTS.md for conventions and patterns.
- 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.
- Check current branch: if on main/master, create a feature branch before developing, the same way the
sova-new-featureskill 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
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.
- 14d ago Changed 2f62914df1b0
- 16d ago Changed · +4 lines 951ed1cf586a
- 22d ago First seen · 102 lines · 31 tokens per session scan A 08e1c95703e9
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.
Other skills, from other repositories
test-then-commit
Implements a small change and commits it. Use when the user asks for a quick fix with a commit.
am-command-build
Implement the next task incrementally — build, test, verify, commit.
commit-guard
Format, lint, typecheck and test before a commit lands. Use when the task involves: commit, pre-commit, hook, staged, format, lint.
build-ticket
Build Skill: Implements tickets using TDD methodology. Commits code to the current branch. MANDATORY TRIGGERS: build, implement, code, develop, work ticket, TDD, red green refactor, fix bug, write code.
incremental-implementation
Delivers changes incrementally in thin, verifiable slices. Use when implementing any feature or change that touches more than one file, or when picking up the next task from a plan. Use when rolling a change out behind a feature flag, when you're about to write a large amount of code at once, or when a task feels too…
setup-pre-commit
Set up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo. Use when user wants to add pre-commit hooks, set up Husky, configure lint-staged, or add commit-time formatting/typechecking/testing.