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.
git clone --depth 1 https://github.com/sruja-ai/srujaWrote 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/commands/sruja-ai/sruja/sruja-pre-merge-review)<a href="https://agentmods.dev/commands/sruja-ai/sruja/sruja-pre-merge-review"><img src="https://agentmods.dev/badge/commands/sruja-ai/sruja/sruja-pre-merge-review/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/commands/sruja-ai/sruja/sruja-pre-merge-review"><img src="https://agentmods.dev/badge/commands/sruja-ai/sruja/sruja-pre-merge-review.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.00000 | $0.00569 |
| Opus 5 | $0.00000 | $0.00284 |
| Sonnet 5 | $0.00000 | $0.00114 |
| Haiku 4.5 | $0.00000 | $0.00057 |
Grade A, and why
sruja-pre-merge-review 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 12d 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sruja: Pre-Merge Review
Structured review workflow before merging changes. Produces actionable feedback with architecture grounding.
Related: plan-feature → implement-from-plan → verify-task → reflect-on-run
Steps
-
Run review with JSON output
sruja review -r . -f jsonThis produces structured suggestions, violations, and health score.
-
Run intent check
sruja intent check -r . -f jsonVerify changes match declared architectural intent.
-
Run drift check
sruja drift -r . -f jsonCheck for new architectural drift.
-
Or use the combined verify-task review profile
sruja verify-task --profile review -r . -f json -
Parse and categorize findings
Output the review results in this structured format:
## Blockers (must fix before merge) - [ ] <severity> <finding>: <description> ## Suggestions (should fix) - [ ] <finding>: <description> ## Nits (optional) - [ ] <finding>: <description>Blockers include:
- Lint errors in
repo.sruja - New drift violations
- Intent mismatches
- Failed tests
Suggestions include:
- Review recommendations from
sruja review - Architecture improvements
- Missing documentation
Nits include:
- Style issues
- Minor refactoring opportunities
- Lint errors in
-
If blockers exist:
- Do not merge
- Fix blockers
- Re-run review
-
If no blockers:
- Review suggestions and nits
- Decide which to address now vs defer
- Proceed with merge
Example Output
## Blockers
- [ ] drift: New violation in AuthContainer -> Database (missing relationship)
## Suggestions
- [ ] Consider splitting AuthContainer into AuthAPI and AuthWorker
- [ ] Add description to new PaymentService component
## Nits
- [ ] Format: run `sruja fmt repo.sruja`
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.
- 12d ago First seen · 90 lines · 0 tokens per session scan A f70ed87ee7e1
sruja-pre-merge-review is a command published in the GitHub repository sruja-ai/sruja (24 stars, last pushed 5d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 569 tokens. 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 commands, from other repositories
merge
Finish a PR properly: every check green, every review addressed — human and bot — then merge and clean up.
pr
Prepare and open a pull request the senior way: gate, template, scrubbed, everything visible.
release
The pre-tag controller: version sync, changelog, clean tree, gate, and suite — every failure listed, the tag printed, never run.
status
The state of play, computed fresh: branch, dirty files, the active sprint, open work, index freshness.
pr
Analyze changes, detect scope issues, and create a well-structured PR.
done
Finish a task - document, create PR or merge, close.