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/.claude/commands/find-task.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/commands/xsovad06/sova/find-task)<a href="https://agentmods.dev/commands/xsovad06/sova/find-task"><img src="https://agentmods.dev/badge/commands/xsovad06/sova/find-task/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/commands/xsovad06/sova/find-task"><img src="https://agentmods.dev/badge/commands/xsovad06/sova/find-task.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.00047 | $0.02783 |
| Opus 5.5 | $0.00019 | $0.01113 |
| Sonnet 5.5 | $0.00009 | $0.00557 |
| Haiku 4.5 | $0.00005 | $0.00278 |
Grade A, and why
find-task 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 — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Find Next Task
Triage this project's open tickets (Jira or GitHub, whichever task_source.type is configured) into AUTO, INTERACTIVE, BLOCKED or CLOSE, print one compact table, and record each ticket's suitability: the matching agent: label for a self-assigned ticket, and a local record (sova assess set) for every AUTO/INTERACTIVE/BLOCKED ticket regardless of assignee.
Scope: $ARGUMENTS
Instructions
1. Determine the Task Source
sova config get task_source.type
Read every other setting through sova config get as well (never assume a default): task_source.jira_project_key, task_source.jira_jql_filter, task_source.labels, task_source.milestone, triage.skip_title_prefixes, triage.skip_labels, triage.interactive_title_prefixes, triage.interactive_labels.
2. Build the Ticket Pool
Jira (task_source.type = "jira"):
# Pickup states only, current user first, scoped to <jira_project_key> and with <jira_jql_filter> from step 1:
jira issue list -q "project = <jira_project_key> AND status in (Backlog, \"To Do\", New, \"Selected for Development\") AND assignee = currentUser() AND (<jira_jql_filter>)"
jira issue list -q "project = <jira_project_key> AND status in (Backlog, \"To Do\", New, \"Selected for Development\") AND assignee is EMPTY AND (<jira_jql_filter>)"
The project = <jira_project_key> clause is mandatory on both queries and is independent of task_source.jira_jql_filter: the account running this command can usually see several Jira projects, so without it an empty filter widens the pool to every accessible project and step 7 then writes agent: labels onto tickets this project does not own. If task_source.jira_project_key is empty, stop and report that rather than running an unscoped query.
GitHub (default, task_source.type = "github"):
gh issue list --assignee @me --state open --limit 50 --json number,title,labels,milestone,updatedAt,body
gh issue list --search "no:assignee" --state open --limit 30 --json number,title,labels,milestone,updatedAt,body
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 2490af0b2973
- 14d ago Changed · +12 lines · +13 tokens per session b70f7e7a6017
- 16d ago Changed · +62 lines · +16 tokens per session 65ed80bb76c3
- 2mo ago First seen · 82 lines · 18 tokens per session scan A e5d4b7cc40d6
find-task is a command published in the GitHub repository xsovad06/sova (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 47 tokens to every session and 2,783 once invoked, about $0.0002 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.
Other commands, from other repositories
dashboard
Phase 3 monitoring — System health, execution insights, and velocity analytics.
run
Execute an approved PRD using feature branch workflow (v7.0). This command generates briefs, auto-reviews them, allows user iteration, and then orchestrates execution.
anchors
List what each requirement tag anchors to (read-only).
implement-evidence-asks
Read by /implement Phase 1 (D-CMD-REF-HAND). "The grammar below", "the exception grammar above" and "the record above" name sections of this file. Any other "above" means the Phase 1 text before the step that sent you here.
afe
Evaluate feature - code review or comparison (shortcut for feature-eval).
aitask-pr-import
Create an aitask from a pull request by analyzing PR data and generating a structured task with implementation plan.