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/sipyourdrink-ltd/bernstein/resolvernpx skills add sipyourdrink-ltd/bernstein --skill resolvergit clone --depth 1 https://github.com/sipyourdrink-ltd/bernsteinWrote 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/sipyourdrink-ltd/bernstein/resolver)<a href="https://agentmods.dev/skills/sipyourdrink-ltd/bernstein/resolver"><img src="https://agentmods.dev/badge/skills/sipyourdrink-ltd/bernstein/resolver.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.00011 | $0.00284 |
| Opus 5 | $0.00005 | $0.00142 |
| Sonnet 5 | $0.00002 | $0.00057 |
| Haiku 4.5 | $0.00001 | $0.00028 |
Grade A, and why
resolver 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 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.
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.
What it actually says
Merge Conflict Resolver Skill
You resolve git merge conflicts between concurrent agent branches.
Specialization
- Reading both sides of a merge conflict to understand intent.
- Determining which changes to keep, combine, or rewrite.
- Preserving correctness from both branches.
- Ensuring the resolved code compiles, passes types, and maintains tests.
Work style
- Read the conflict markers and surrounding context for each file.
- Understand what each side was trying to accomplish.
- Resolve by combining both intents where possible; pick one side only when they are truly incompatible.
- After resolving all conflicts, run any available tests to verify.
- Stage resolved files and commit.
Rules
- Only modify files listed in your task's
owned_files(the conflicting files). - Never discard changes silently - if you drop one side, explain why in the commit message.
- Prefer combining both sides over picking a winner.
- If a conflict is ambiguous and cannot be safely resolved, mark the task as failed with a clear explanation.
- Do not refactor, optimize, or "improve" code beyond what is needed to resolve the conflict.
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 · 39 lines · 11 tokens per session scan A cfa773d3cae7
resolver is a skill published in the GitHub repository sipyourdrink-ltd/bernstein (1,038 stars, last pushed 3d ago), licensed Apache-2.0. It adds 11 tokens to every session and 284 once invoked, about $0.0001 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-30.
Other skills, from other repositories
reticle-aesthetic
Build landing page sections, hero blocks, and marketing surfaces in the Reticle/Sigil engineering-instrument-grid aesthetic. Use when creating new landing sections, hero components, marketing pages, or when the user says "reticle", "hero", "landing page", "new section", "instrument panel", "grid cell", or wants to…
comment
Write doc comments, module docs, and inline comments that follow Dedalus conventions per language. Loads the canonical style guides from the monorepo. Covers Rust, Python, Go, and TypeScript.
frontend-design-taste
Build distinctive frontends that avoid generic AI aesthetics. Provides anti-slop enforcement, variance dials, art direction archetypes, creative arsenal, and performance guardrails. Use when creating new landing pages, UI components, design systems, or when the user says "make it look good", "design direction", "avoid…
generate-interface
Define or refactor subsystem interfaces into small, explicit contracts with clear ownership, narrow scope, stable semantics, and README-first documentation. Use when designing a new API, collapsing ad hoc module boundaries into a few coherent interfaces, hardening internal contracts, or rewriting subsystem docs so…
app-onboarding-questionnaire
Design and build high-converting questionnaire-style app onboarding flows modelled on proven conversion patterns from top subscription apps (Headspace, Noom, Duolingo). Use when building onboarding flows, sign-up funnels, questionnaire UIs, or conversion-optimized first-run experiences. Triggers on "onboarding flow"…
create-hook
Create Cursor hooks. Use when you want to create a hook, write hooks.json, add hook scripts, or automate behavior around agent events.