Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/borda/ai-rig/resolvenpx skills add Borda/AI-Rig --skill resolvegit clone --depth 1 https://github.com/Borda/AI-RigWrote 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/borda/ai-rig/resolve)<a href="https://agentmods.dev/skills/borda/ai-rig/resolve"><img src="https://agentmods.dev/badge/skills/borda/ai-rig/resolve.svg" alt="Measured on agentmods" 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 | $0.00272 | $0.17496 |
| Opus 5 | $0.00136 | $0.08748 |
| Sonnet 5 | $0.00054 | $0.03499 |
| Haiku 4.5 | $0.00027 | $0.01750 |
Grade C, and why
resolve scanned grade C 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 4d 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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
<!-- branch: main-path — post-pr (call 4 of 4 normal / 5 of 5 with codex-cap) --> How it starts
The opening of the file, as written. The whole thing — 884 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OSS maintainer fast-close workflow. PR number → three phases fire automatically:
- PR intelligence — synthesize motivation from PR body, linked issues, thread; classify comments into action items
- Conflict resolution — checkout PR branch (fork-aware), merge
BASE_REF, resolve conflicts with contributor intent as priority lens - Action item implementation — implement each item as separate commit attributed to review comment, push to contributor's fork
Result: conflict-free PR branch pushed to fork, ready to merge — no GitHub UI.
Core invariant — transparent, reversible: every action = visible named git object. Use git merge (new commit, two parents), never git rebase (rewrites SHA, kills revert/cherry-pick). Each action item = own commit — granular revert always possible.
Bare comment text → skip to Codex dispatch (Step 12).
- $ARGUMENTS: one of:
- Omitted → review-handoff mode: auto-detect PR from most recent
.reports/review/*/review-report.md(oss lineage) or.reports/codex/review/*/review-notes.md(codex lineage, detected but not parsed — see Step 0 lineage guard) - PR number (e.g.
42or#42) or GitHub PR URL → pr mode report(bare word) → report mode: latest review findings as action items; no GitHub re-fetch42 reportor<URL> report→ pr + report mode: aggregate live GitHub comments + review report, deduplicated in one pass- Bare review comment text → comment dispatch mode (jumps to Step 12)
- Omitted → review-handoff mode: auto-detect PR from most recent
--no-challenge: optional — skip challenge gate per item; all selected items treated asVALID--no-codemap: optional — disable codemap structural context (on by default when codemap installed + index present)--codemap: optional — strict mode: stop and report if codemap not installed or index missing--agent <name>: optional — use<name>agent for implementation instead of Codex; must be an implementation agent; bare name auto-prefixed withfoundry:if no plugin prefix detected (e.g.--agent sw-engineer→foundry:sw-engineer;--agent linting-expert→foundry:linting-expert;--agent doc-scribe→foundry:doc-scribe); explicit prefix also accepted (--agent foundry:sw-engineer); see routing table inaction-item-dispatch.md.--agentalso applies toINTEL_AGENT(Step 3b thread intelligence) — explicit--agentoverrides label/title routing for the thread-intelligence subagent as well, so a docs-focused PR routed via--agent foundry:doc-scribeuses doc-scribe for both classification and implementation.
NOT-for additions (scope guards):
- NOT for non-Python source PRs (TypeScript, Go, Rust, Java) unless action items are limited to documentation or CI/CD changes — Step 9's lint-qa gate runs Python-specific tools (
ruff/mypy); non-Python PRs will receive partial or no static-analysis review. For non-Python repos, run/oss:resolveinreportmode with manually-curated findings. - NOT for branches with uncommitted local edits — the
report-mode no-PR# path operates on the current branch as-is; uncommitted changes will be committed alongside the action items. Stash (git stash) or commit local edits before invoking; the workflow does not auto-stash.
loads: compaction-contract.md
- Key boundary: end of Step 8 — per-item implementation loop complete, before Step 9 lint gate. Contract overwrites on each iteration (latest state wins).
- Second boundary: start of Step 11 — before final report write, after push.
- Preserve at boundary 1: PR#, implemented/remaining item state.
- Preserve at boundary 2: final report path, PR#.
What ships with it
7 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.
- 4d ago First seen · 884 lines · 272 tokens per session scan C 935aba382c55
resolve is a skill published in the GitHub repository Borda/AI-Rig (25 stars, last pushed today), licensed Apache-2.0. It adds 272 tokens to every session and 17,496 once invoked, about $0.0014 per session on Opus 5. A static security scan graded it C with 1 finding (hidden instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
ao-desktop-dev
Launch, restart, or troubleshoot the real AO Electron desktop app from this repository; run a checkout against isolated or real local AO data; combine PR branches for local UI review; and diagnose stale Electron processes, port conflicts, or preload bridge mismatches. Use whenever asked to run, open, show, or visually…
intuitive-port-worktree
Port changes from one git worktree or checkout into the default repository folder's current branch, then by default sync the result to the remote default branch when everything is clean. Use when the user asks to move, copy, transfer, transplant, cherry-pick, apply a patch, or port worktree changes into the…
testing-mcp-with-cli-agents
Test an MCP server by driving real CLI agents (Claude, Codex, Cursor, Gemini, Grok, agy, opencode) against it, using isolated tmux sockets and send-keys instead of trusting unit tests alone. Use this whenever verifying MCP-server behavior end-to-end, checking that a local branch or checkout works across installed…
store-submission-checklist
Use when preparing a game for Steam, console, mobile, or other storefront submission with platform metadata, compliance, ratings, privacy, package, entitlement, and approval requirements.
platform-device-compatibility-matrix
Use when a game needs a platform and device compatibility matrix across OS, hardware, GPU, memory, resolution, input, network, storefront, certification, test evidence, and support policy; not for store metadata preparation.
vinyl-dig
Use when asked to run a vinyl-shop dig — crawl a set of local record shops' online catalogs in parallel, benchmark prices against Discogs, and produce a tiered buy list. Originated for Johnny's Chicago digs; portable to any city/shop-list as long as the calling project provides the companion files below.