sem is a Git-based semantic version control tool that compares changes to code entities such as functions, methods, and classes instead of individual lines. It helps developers and coding agents review changes, trace responsibility, and assess their impact across repositories. Catalogue add-ons provide agent integrations and workflows for operating sem.
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 skills add Ataraxy-Labs/sem --skill weave-merge-previewgit clone --depth 1 https://github.com/Ataraxy-Labs/semWrote 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/ataraxy-labs/sem/weave-merge-preview)<a href="https://agentmods.dev/skills/ataraxy-labs/sem/weave-merge-preview"><img src="https://agentmods.dev/badge/skills/ataraxy-labs/sem/weave-merge-preview/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/ataraxy-labs/sem/weave-merge-preview"><img src="https://agentmods.dev/badge/skills/ataraxy-labs/sem/weave-merge-preview.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.00038 | $0.00285 |
| Opus 5.5 | $0.00015 | $0.00114 |
| Sonnet 5.5 | $0.00008 | $0.00057 |
| Haiku 4.5 | $0.00004 | $0.00028 |
Grade A, and why
weave-merge-preview 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
Preview a branch merge
Use the host's terminal in the user's chosen Git repository. Confirm weave --version
is Ataraxy Weave (tested with 0.5.4). If absent, explain the prerequisite;
do not install it or alter Git's merge driver automatically.
Identify the exact branch/ref the user wants compared with the current HEAD.
Check the current branch and working-tree status using the host's Git tools.
Use weave preview BRANCH, replacing BRANCH with the shell-quoted requested ref.
To narrow a known conflict, weave preview BRANCH --file path/to/file previews
that file. Do not fetch remote branches unless the task authorizes it.
Report the conflicts or independent entity changes the preview actually shows. A clean structural merge is not proof that the combined program compiles or behaves correctly. Unsupported file types may use line-level merge behavior.
This workflow previews only. Do not run weave setup, weave land, git merge,
stage changes, or modify source because a preview succeeded. Applying a merge
and running the repository's build/tests require the user's corresponding request
and the host's normal approval flow.
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 · 26 lines · 38 tokens per session scan A 4df1f21b42d8
weave-merge-preview is a skill published in the GitHub repository Ataraxy-Labs/sem (3,413 stars, last pushed 2d ago), licensed Apache-2.0. It adds 38 tokens to every session and 285 once invoked, about $0.0002 per session on Opus 5.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-10-14.
Other skills, from other repositories
inspect
Entity-level code review for Git. Scores changes by risk and groups them by logical dependency.
weave
Entity-level semantic merge driver for Git. Resolves conflicts at the function/class level instead of the line level, so two changes to different functions in the same file never conflict.
trace-mcp-pre-commit
Run trace-mcp security, quality-gate, and antipattern checks before committing or opening a PR. Activate when the agent is about to create a commit or pull request in a project indexed by trace-mcp.
basemind
Navigate large or unfamiliar codebases via the basemind MCP server — outlines, symbol search, reference/caller lookups, commit history, blame, and diffs without reading source files. Reach for it whenever the user asks "where is X defined", "what calls Y", "what changed recently in Z", or whenever you're about to grep…
basemind-cli
Navigate codebases and manage caches via the basemind CLI — outlines, symbol search, reference/caller lookups, git history, blame, and diffs. For headless scripting, CI, or when driving the CLI more efficiently than interactive MCP calls. Shares the same index as the MCP server.
basemind-git-history
Explore git history without shelling out to git — recent commits, commits touching a path, per-line and per-symbol blame, structural diffs across revisions, churn ranking, and a symbol's history over time. Reach for it whenever the user asks "what changed recently", "who last touched this", "when did this symbol…