Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add geniro-io/geniro-claude-harness/plugin install geniroWrote 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/geniro-io/geniro-claude-harness/resolve)<a href="https://agentmods.dev/skills/geniro-io/geniro-claude-harness/resolve"><img src="https://agentmods.dev/badge/skills/geniro-io/geniro-claude-harness/resolve/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/geniro-io/geniro-claude-harness/resolve"><img src="https://agentmods.dev/badge/skills/geniro-io/geniro-claude-harness/resolve.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.00108 | $0.05127 |
| Opus 5 | $0.00054 | $0.02563 |
| Sonnet 5 | $0.00022 | $0.01025 |
| Haiku 4.5 | $0.00011 | $0.00513 |
Grade B, and why
resolve scanned grade B with 1 finding 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.
Tells the agent never to refusemediumAnti-refusal
Suppressing the ability to decline removes a core safety control; a later harmful request then succeeds.
- **L4 instructions** — `${CLAUDE_PLUGIN_ROOT}/skills/_shared/load-custom-instructions.md` at `LOAD_TIER: pipeline`, loaded at Phase 1 Step 0. A project rule like "never decline a security bot's comment" binds the triage Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
This is a copy
92% identical to geniro-resolve — 15 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/geniro:resolve — PR feedback, decided and fixed
Contents
- Phases 1-3 overview
- State machine
- Loop invariants
- Anti-rationalization
- Budgets / quality gates
- ACI per-phase tool surface
- Memory I/O
- Definition of done
- PHASE 1: Fetch & triage
- PHASE 2: Decide
- PHASE 3: Fix & close
- Modifiers
- Task execution entry / state recovery
- REFERENCE
You are an autonomous executor. You read an open pull request's unresolved review comments and failing CI checks, decide which of them are worth doing, apply those fixes yourself, and close the loop on the PR — replies posted, threads resolved. The deliverable is the landed change, not a plan for one.
Runtime portability. ${CLAUDE_PLUGIN_ROOT} is a path placeholder Claude Code substitutes into file references, never a shell export — it reads empty in a Bash call under every host, Claude Code included, so an empty probe is no evidence of another runtime (CLAUDECODE in the environment marks Claude Code). Resolve the root by working these in order: the ancestor directory of this file containing .claude-plugin/plugin.json; a copy of the referenced file sitting beside this one (the Cursor build ships each skill's own phase and reference files there); a plugin checkout inside the workspace. Substitute the resolved root for every ${CLAUDE_PLUGIN_ROOT} occurrence and export it as CLAUDE_PLUGIN_ROOT in every Bash call. Work the rungs with a command, not a judgment: the run's first Bash call lists the directory this file was read from and each candidate root, and its output is echoed verbatim before anything else. Read the rungs against that output — a path it does not show did not resolve, and a file it does not show cannot be read, however confidently a later step would report otherwise. A ladder that resolves is bookkeeping, not a finding: keep the echo to the probe output and the resolved root, and reserve a degraded-run notice for a rung that actually failed. Read ${CLAUDE_PLUGIN_ROOT}/skills/_shared/runtime-portability.md before deciding a step cannot run here: it substitutes mechanisms, not steps, and routes a host with no one to ask to ${CLAUDE_PLUGIN_ROOT}/skills/_shared/non-interactive-host.md. When no rung resolves, the files are missing but the contract is not — open your first message by naming what is unavailable, run every phase and gate this skill declares, never let the project's own rules stand in for its decision gates, and take no outward-facing action (ready-for-review PR, merge, force-push, protected-branch push, posted comment, tracker transition) without an explicit answer.
What ships with it
4 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.
- yesterday Changed · -6 lines 491d215eee52
- 2d ago Changed 522325ae730c
- 4d ago Changed 54e33c55dfd1
- 10d ago First seen · 167 lines · 108 tokens per session scan B e9899528eeb7
resolve is a skill published in the GitHub repository geniro-io/geniro-claude-harness (8 stars, last pushed yesterday), licensed Apache-2.0. It adds 108 tokens to every session and 5,127 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it B with 1 finding (tells the agent never to refuse). It is 92% identical to geniro-resolve, differing in 15 lines, and is treated as a copy.
Other skills, from other repositories
gemini-review
Google Gemini CLI code review with Gemini 2.5 Pro, 1M token context, CI/CD integration.
squid-implement-night
Run the full agent-team pipeline end-to-end for one feature whose Tasks Plan is already approved by /squid-plan, handing the human a validated, ready-to-squash-merge PR. Trigger after /squid-plan.
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.
pr-babysitter
Monitors or repairs an open GitHub PR: CI failures, conflicts, review threads, and merge readiness, reporting state changes. Use when asked to "watch this PR", "fix CI", "resolve conflicts", or "address review comments". For PR metadata use pr-creator; for npm release PRs use autoship.
aster-review-ci
Run aster code reviews non-interactively in CI, GitHub Actions, or from another agent. Covers aster review --pr, --json, --stream, --comment, diff-from-stdin, token handling, and filtering findings. Use when wiring aster into a pipeline, posting PR comments, or parsing review output programmatically.
argot-setup-ci
Wire argot into a repository's GitHub Actions as a non-blocking configured check on every pull request — a job summary plus code-scanning annotations. Use when the user wants argot "in CI", "on PRs", "as a GitHub Action", or asks to "set up argot CI". Distinct from argot-setup (local checking) and argot-review-pr…