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 rules/briangmilnes/apas-verus/rebase-agentsgit clone --depth 1 https://github.com/briangmilnes/APAS-VERUSWrote 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/rules/briangmilnes/apas-verus/rebase-agents)<a href="https://agentmods.dev/rules/briangmilnes/apas-verus/rebase-agents"><img src="https://agentmods.dev/badge/rules/briangmilnes/apas-verus/rebase-agents.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.1 | $0.00320 | $0.00320 |
| Opus 5 | $0.00160 | $0.00160 |
| Sonnet 5 | $0.00064 | $0.00064 |
| Haiku 4.5 | $0.00032 | $0.00032 |
Grade A, and why
rebase-agents 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 5d 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
Rebase Agents
When to use
After committing and pushing changes on main, run scripts/rebase-agents.sh to bring
all agent worktrees up to date with main.
Prerequisites
- Main worktree must be clean (no uncommitted changes).
- Main must be pushed (no unpushed commits).
- The script verifies both before proceeding.
Usage
cd ~/projects/APAS-VERUS && scripts/rebase-agents.sh
What it does
- Verifies main is clean and pushed.
- For each agent (agent1 through agent4):
git fetch origingit rebase origin/maingit push origin agentN/ready --force
- On success, runs
scripts/survey-agents.shto show final state.
Conflict handling
If any agent's rebase fails:
- The script stops immediately (does not continue to the next agent).
- Fix conflicts in the reported worktree directory.
- Run
git add -A && GIT_EDITOR=true git rebase --continueto complete that rebase. - Rerun
scripts/rebase-agents.shto continue with remaining agents.
When NOT to use
- During a merge cycle (Phases 0–7). The merge workflow handles rebases at specific
points. Use
scripts/rebase-agents.shonly outside the merge workflow. - If main has uncommitted or unpushed changes. Commit and push first.
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.
- 5d ago First seen · 42 lines · 320 tokens per session scan A d05b9b49ce67
rebase-agents is a cursor rule published in the GitHub repository briangmilnes/APAS-VERUS (10 stars, last pushed 1mo ago), licensed MIT. It adds 320 tokens to every session, about $0.0016 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 cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.