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-research/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-research)<a href="https://agentmods.dev/skills/xsovad06/sova/sova-research"><img src="https://agentmods.dev/badge/skills/xsovad06/sova/sova-research/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-research"><img src="https://agentmods.dev/badge/skills/xsovad06/sova/sova-research.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.00019 | $0.01470 |
| Opus 5.5 | $0.00008 | $0.00588 |
| Sonnet 5.5 | $0.00004 | $0.00294 |
| Haiku 4.5 | $0.00002 | $0.00147 |
Grade A, and why
sova-research 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 — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Research
Investigate a task's codebase impact and produce a structured research assessment. Designed for autonomous execution: always writes findings back to the tracker. For interactive pre-development planning, use the sova-spec skill instead.
Task: the arguments provided when this skill is invoked
Instructions
Step 1: Fetch the Task
Get the issue number or ticket key from the arguments provided when this skill is invoked. If empty, stop with an error.
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
Save the original description verbatim.
If the issue has no description or body, report "Issue has no description; needs specification before research" and stop.
If the issue body already contains a ## Research section, report "Issue already has a research section; ready for development" and stop.
Step 2: Read Project Context
Read whatever exists; skip files that are missing:
CLAUDE.mdandAGENTS.mdfor project conventions.claude/rules/architecture.mdfor component overview and design decisions- The cookbook for known patterns and past mistakes: the
README.mdindex 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.mdif present
Step 3: Explore the Codebase
Based on the issue, investigate the affected areas. Use file reads, grep, and search; do not guess from file names alone.
- Identify affected files: find every file that needs to be modified, created, or deleted. Read the actual source to confirm.
- Find the pattern: locate the closest existing implementation to follow. Note specific file paths, class names, and method signatures.
- Check for data model changes: determine if DB models, schemas, or migrations are needed.
- Check for API changes: identify new or modified endpoints with request/response shapes.
- Find reusable code: identify utilities, base classes, test fixtures, and patterns that the implementation should use. Reference specific functions and classes.
- Anticipate edge cases: based on reading the actual code, identify failure modes and edge cases not obvious from the issue description.
- Check for UI implications: templates, components, user-facing behavior changes.
- Design implementation approach: produce a concrete 3-6 step plan referencing specific files.
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 4bbea234afe3
- 16d ago Changed · +6 lines 21e7e8208440
- 21d ago Changed 1b27665340b0
- 22d ago First seen · 167 lines · 19 tokens per session scan A 9c90fa973ad4
sova-research is a skill published in the GitHub repository xsovad06/sova (2 stars, last pushed today), licensed Apache-2.0. It adds 19 tokens to every session and 1,470 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
find-simplifications
Use for a periodic repo-wide sweep of qwen-code for accumulated excess surface — dead components and files, orphaned locale keys, exports nothing consumes, added-then-removed scaffolding — filing candidates on a tracking issue and landing only what a maintainer has said yes to. Repo-wide and evidence-first; every…
code-review
You are a senior code reviewer. You receive diffs via stdin.
agent-debug-ci
Investigate failed scheduled or nightly GitHub Actions runs on the default branch, determine whether the failure is reproducible and repository-owned, implement the smallest evidence-backed fix, validate it, and open a pull request. Use when a failed nightly CI event starts an agent, or when the standard CI or…
audit-ci
Run and analyze Elements cold CI performance profiles and propose evidence-backed build, test, lint, and dependency-graph improvements. Use whenever asked to profile or benchmark pnpm run ci, rerun ci:profile, create a CI performance audit, compare CI timings, find bottlenecks or the completion path, investigate a CI…
review
Adversarial review of an increment before it ships, by a fresh context or another model family; every finding cites path:line and is re-verified. Use for "review", "qa", "critique this".
tech-debt-ci-review
Codex adapter for deep technical-debt and CI-stability audits. Use when asked to find test theater, flaky tests, missing or mis-scoped tests, brittle CI/toolchain behavior, structural debt blocking green PRs, or a remediation order for opencode-swarm.