Borrowing it
Nothing to install: this file belongs to jarmak-personal/hvir. 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/jarmak-personal/hvir/main/.claude/skills/hvir-create-issue/SKILL.mdgit clone --depth 1 https://github.com/jarmak-personal/hvirWrote 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/jarmak-personal/hvir/hvir-create-issue)<a href="https://agentmods.dev/skills/jarmak-personal/hvir/hvir-create-issue"><img src="https://agentmods.dev/badge/skills/jarmak-personal/hvir/hvir-create-issue/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/jarmak-personal/hvir/hvir-create-issue"><img src="https://agentmods.dev/badge/skills/jarmak-personal/hvir/hvir-create-issue.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.00085 | $0.01601 |
| Opus 5 | $0.00043 | $0.00800 |
| Sonnet 5 | $0.00017 | $0.00320 |
| Haiku 4.5 | $0.00009 | $0.00160 |
Grade A, and why
hvir-create-issue 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 yesterday.
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 — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create an hvir issue
Turn an observation or idea into an issue that is worth discussing before code starts. Be opinionated about product fit and precise about what is known, while preserving unresolved questions for the issue discussion.
Require authorization before doing work
Do not research, evaluate, or draft an issue until the user explicitly asks to use this skill
or clearly approves an agent's proposal to use it. Discovering a bug, improvement, or possible
follow-up is not authorization. In that situation, offer at most one brief sentence such as
“I can use hvir-create-issue to evaluate and draft this if you want,” then stop that workflow.
Treat drafting and publishing as separate approvals:
- The first approval authorizes product research and an issue draft.
- After presenting the exact title, body, and labels, ask whether to create the issue.
- Only a clear user approval after that preview authorizes the external write.
Do not infer either approval from silence, the usefulness of the finding, a general preference for issue-first development, or permission granted for a different issue.
Establish context
- Read
AGENTS.md,CONTRIBUTING.md,docs/design.md, and the ADR index. - Read the ADRs that govern the affected product area or seam.
- Inspect relevant local code or documentation when it helps test the proposal against the product as it exists.
- Ask only for missing information that materially changes the problem, scope, or fit. Make and state reasonable assumptions for smaller gaps.
Do not treat the reporter's proposed solution as the requirement. First identify the user or contributor problem and the observable outcome.
Classify product fit
State one of these conclusions before drafting:
- Aligned: the outcome reinforces hvir's view-first, agent-aware workbench.
- Needs design discussion: it may fit, but a product boundary or durable architecture choice is unresolved.
- Conflicts with current direction: a design guardrail or ADR rejects the proposed approach. Name the exact conflict and recast the issue as a proposal to revisit that decision only if the reporter intends that discussion.
- Out of scope: the outcome would turn hvir into an IDE, editor, extension platform, task runner, or session orchestrator, or otherwise violates an explicit non-goal. Explain this directly instead of manufacturing an implementation issue.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- yesterday Changed · +10 lines 0ec6f7f4fd1a
- 10d ago First seen · 142 lines · 85 tokens per session scan A 73d75cc3a43f
hvir-create-issue is a skill published in the GitHub repository jarmak-personal/hvir (2 stars, last pushed yesterday), licensed MIT. It adds 85 tokens to every session and 1,601 once invoked, about $0.0004 per session on Opus 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 skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
remove
Remove a deployed framework or addon from the current workspace.