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/issue-template/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/issue-template)<a href="https://agentmods.dev/skills/xsovad06/sova/issue-template"><img src="https://agentmods.dev/badge/skills/xsovad06/sova/issue-template/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/issue-template"><img src="https://agentmods.dev/badge/skills/xsovad06/sova/issue-template.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.00043 | $0.01948 |
| Opus 5.5 | $0.00017 | $0.00779 |
| Sonnet 5.5 | $0.00009 | $0.00390 |
| Haiku 4.5 | $0.00004 | $0.00195 |
Grade A, and why
issue-template 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 21d 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 — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue Body Template
When creating, drafting, or rewriting an issue for the tracker, produce the body
below. The headings are not stylistic: SOVA's triage role scores them
deterministically. A body that scores below the threshold is rewritten by an LLM
enrichment pass, or downgraded to needs_spec when enrichment is disabled or
falls short, so the issue waits instead of shipping. An issue written with this
template scores 8/8 and goes straight to the pipeline.
Canonical Body
## Objective
<One sentence: what needs to be done and why it matters.>
## Detailed Description
<The current behavior, the desired behavior, and the mechanism that gets from
one to the other. Name the functions, data, and call sites that change. Two to
six sentences beats a paragraph of background.>
## Acceptance Criteria
- [ ] <Binary, testable outcome.>
- [ ] <Second binary outcome.>
- [ ] All existing tests pass (`make check`)
- [ ] No new lint warnings (`make lint`)
## Files / Modules to Change
- [ ] `path/to/module.py`: <what changes there>
- [ ] `tests/test_module.py`: <coverage added>
## Out of Scope / Constraints
- <What must NOT be touched, and any constraint the implementation must respect.>
## Dependencies
None
## References
- Related: #<issue-number>
- Code: `path/to/module.py`
Scoring Rules
compute_quality_score() in sova/roles/triage.py awards 8 points:
| Points | Requirement |
|---|---|
| 1 | ## Objective heading |
| 1 | ## Detailed Description heading |
| 2 | ## Acceptance Criteria heading AND a literal - [ ] somewhere in the body |
| 1 | ## Files / Modules to Change (or ## Files to Change, or ## Files) |
| 1 | ## Out of Scope / Constraints (or ## Out of Scope, ## Constraints, ## Scope Boundaries) |
| 1 | ## References heading, or any issue ref, URL, or backticked file path |
| 1 | No LLM preamble or postamble |
Non-negotiable rules, in the order they break issues:
- Every canonical section is exactly
##. The scorer's regex is^##\s+. A section written as###, or bolded as**Objective**, scores zero. - Acceptance criteria need at least one unchecked
- [ ]. A list of already-checked- [x]items fails the check, which costs 2 points and caps the body at 6/8. The check is also required independently of the total, so no threshold is low enough to let the issue through without it. - Start the body directly at
## Objective. No conversational framing. Six line-initial patterns cost the LLM-leak point, matched case-insensitively against every line of the body:Here's a/an/the, and theHere is a/an/thespellingI'veorI havefollowed bycreated,written,drafted,prepared, orupdatedLet me, exceptLet me know, which is explicitly exemptSure,Certainly, orAbsolutelyfollowed by,,!, or.I'llFeel free toorDon't hesitate to
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.
- 21d ago Changed · +8 lines · -6 tokens per session 807e3a01429a
- 1mo ago First seen · 171 lines · 49 tokens per session scan A b106fccb6c59
issue-template is a skill published in the GitHub repository xsovad06/sova (2 stars, last pushed today), licensed Apache-2.0. It adds 43 tokens to every session and 1,948 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-09-08.
Other skills, from other repositories
protocol-tracker
Internal skill for commands. The tracker verb-resolution protocol - how a lets-tracker block resolves through the active adapter, the neutral read shape, body crossing, degradation, preflight and trust. Loaded by a command or skill right before its first tracker verb. Do not trigger on user conversation.
ensemble-beads-build
Drive an existing bead hierarchy to completion through the full builder, code-review, and close pipeline (Codex skill for /ensemble:beads-build).
jjj
Use when working in Jujutsu repositories for problem tracking, solution management, and code review — implements Popperian epistemology (problems → solutions → critiques) directly in version control.
github-guide
Use when managing GitHub tickets, Projects kanban, pull-request delivery/review, durable issue or PR context comments, or native CI/repository enforcement on github.com or GitHub Enterprise Server. Triggers on GitHub issues, issue relationships, gh issue, Projects v2 items/Status/fields, gh project, decision or…
resume-work
Pick up exactly where a stopped or paused task stopped, at the same phase. Reads the ship record, verifies which claims of the previous session or agent still hold against the repo, reloads only the context the next step needs, and keeps going with ship or land. In the same chat after a usage limit it re-reads…
issues
Turn an agreed outcome into tracker issues with acceptance, dependencies, references, and verification. Keep planning proportional to the work.