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-implement-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-implement-issue)<a href="https://agentmods.dev/skills/jarmak-personal/hvir/hvir-implement-issue"><img src="https://agentmods.dev/badge/skills/jarmak-personal/hvir/hvir-implement-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-implement-issue"><img src="https://agentmods.dev/badge/skills/jarmak-personal/hvir/hvir-implement-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.00081 | $0.02283 |
| Opus 5 | $0.00041 | $0.01141 |
| Sonnet 5 | $0.00016 | $0.00457 |
| Haiku 4.5 | $0.00008 | $0.00228 |
Grade A, and why
hvir-implement-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 today.
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 — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implement an hvir issue
Implement the governing issue without allowing its proposed solution to bypass hvir's product constraints or architecture. Spend real effort on ownership and decomposition before editing; raise material concerns while they are still cheap to resolve.
Require an aligned issue
Start from an issue number plus its current, aligned problem statement, desired outcome,
and acceptance criteria. If no governing issue exists, stop and use hvir-create-issue
before implementation. Run a large epic through hvir-implement-epic, which coordinates
independently deliverable child issues instead of producing one giant implementation pull request.
Read AGENTS.md, docs/design.md, the relevant CONTRIBUTING.md sections and ADRs, and the
governing issue. Reuse unchanged context already read in this interaction; a correction needs
the changed requirement, source, and evidence, not repeated onboarding. Resolve these questions
before changing files:
- What user or contributor outcome is being implemented?
- Is the issue aligned with the current product boundaries and accepted decisions?
- Which requirements are settled, and which comments are still exploratory?
- Is a new or superseding ADR required before implementation?
- Is this issue small enough for one focused pull request?
If an answer could materially change product behavior, ownership, authority, or scope, surface it and pause for alignment. Otherwise state the assumption and continue.
Select the delivery path and isolated worktree
Supply credentials through the environment described in docs/project-management.md. Plan the
complete startup, review the result, then apply a freshly recomputed plan:
npm run issue:start -- --issue <number> --json
npm run issue:start -- --issue <number> --apply --json
The command refreshes/prunes remote refs, reads the normalized issue, parent, expected base, deterministic branch and worktree, planning state, and open PRs, conservatively reconciles prior workflow-owned issue worktrees, creates or reuses the selected worktree, and prepares locked dependencies. Planning changes only remote-tracking refs. Apply retains partial or ambiguous state with reasons and never mutates Project membership or Kind. Successful apply sets Status to In Progress through its existing owner.
What ships with it
3 files 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.
- today Changed · +4 lines ed36151b9856
- 9d ago First seen · 186 lines · 81 tokens per session scan A 784a2cbc5bf9
hvir-implement-issue is a skill published in the GitHub repository jarmak-personal/hvir (2 stars, last pushed today), licensed MIT. It adds 81 tokens to every session and 2,283 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.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.