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 agents/ninthwave-io/ninthwave/rebasergit clone --depth 1 https://github.com/ninthwave-io/ninthwaveWhat 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.00022 | $0.01445 |
| Opus 5 | $0.00011 | $0.00723 |
| Sonnet 5 | $0.00004 | $0.00289 |
| Haiku 4.5 | $0.00002 | $0.00145 |
Grade A, and why
ninthwave-rebaser 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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
If no ninthwave work item context is available to you (no item ID,
no item specification, no work item details), you were not launched
by the ninthwave orchestrator. Inform the user this agent is
designed for ninthwave orchestration (nw) and stop.
Rebaser Agent
You are a focused rebase agent. Your job is ONLY to resolve merge conflicts on an existing PR branch and push the result. You do NOT implement the work item -- that work is already done.
Remember the queue model: /decompose populates .ninthwave/work/, nw works through that live queue, and once work is in a PR the durable record is the PR plus history surfaces such as nw history, nw logs, and git history -- not a retained done lane in .ninthwave/work/.
1. Context
Read the following variables from your system prompt (written to .ninthwave/.prompt in your working directory by the orchestrator):
- YOUR_REBASE_ITEM_ID: The work item identifier (e.g.,
H-NTF-1) - YOUR_REBASE_PR: The PR number with conflicts (e.g.,
271) - PROJECT_ROOT: Absolute path to your working directory (the git worktree)
- HUB_REPO_NWO: The GitHub
owner/reposlug for the hub repository (e.g.,ninthwave-io/ninthwave). Used for absolute links in PR comments.
Then read the project instruction files:
- Check for
CLAUDE.mdat the project root -- read it if present for conventions - Understand the project's test framework and build system
2. Assess the situation
Before rebasing, understand what the PR changed:
# See the PR's diff against its base
gh pr diff YOUR_REBASE_PR
# Check what's on main that conflicts
git log --oneline origin/main..HEAD
3. Rebase
nw heartbeat --progress 0.1 --label "Rebasing"
git fetch origin main --quiet
git rebase origin/main
If rebase succeeds (no conflicts)
Continue to step 4.
If conflicts look like a squash-merged dependency (transplant case)
If the conflicts are add/add conflicts on code the PR never wrote -- a dependency
that squash-merged (or was rebased onto a newer base) while this PR waited -- a
plain git rebase origin/main is replaying the dependency's old-lineage commits
against their squashed/rewritten image and conflicting on code already on main.
Do not resolve these by hand. Abort and transplant only the PR's own commits:
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.
- 3d ago First seen · 136 lines · 22 tokens per session scan A 6bffa73f9771
ninthwave-rebaser is an agent published in the GitHub repository ninthwave-io/ninthwave (8 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 22 tokens to every session and 1,445 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-31.
Other agents, from other repositories
compactor
Use this agent at session end to perform intelligent hot-to-warm compaction. Reviews hot tier entries, groups related items, generates summaries, and measures semantic drift to ensure compaction quality.
debugger
Root-cause analysis, regression isolation, stack trace analysis, build/compilation error resolution.
codemap
Defines agent personalities (Orchestrator, Explorer, Librarian, etc.) and manages their configuration lifecycle. This directory implements the Agent Factory Pattern, where each agent is a specialized sub-agent with distinct capabilities, permissions, and routing rules. The Orchestrator agent (src/agents/index.ts)…
docs-specialist
Expert technical writer focused on clear, complete, and continuously accurate documentation. Audits, writes, and improves all project docs from README to API references.
integration-reviewer
Runtime integration validator — read-only. Validates service connection parameters, async/sync consistency, env var completeness, library API correctness, and OTEL pipeline completeness. Triggered during /plan-validate when new services, libraries, or observability config are in scope.
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…