Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add nexiouscaliver/OmniForge/plugin install omniforgeWrote 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/nexiouscaliver/omniforge/omnireview-gitlab)<a href="https://agentmods.dev/skills/nexiouscaliver/omniforge/omnireview-gitlab"><img src="https://agentmods.dev/badge/skills/nexiouscaliver/omniforge/omnireview-gitlab.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.00041 | $0.10745 |
| Opus 5 | $0.00020 | $0.05372 |
| Sonnet 5 | $0.00008 | $0.02149 |
| Haiku 4.5 | $0.00004 | $0.01074 |
Grade B, and why
omnireview-gitlab scanned grade B with 1 finding 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 yesterday.
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.
Recursive force deletemediumDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
Then **Read `/tmp/omni_wait_out_{id}/status.json`** — entries with `"state":"stalled"` or `"harvested_partial":true` are partial-output agents; `"state":"missing"` agents never produced a transcript. **For every agent wh Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 739 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OmniForge
Multi-agent adversarial MR review — 3 parallel agents, 3 worktrees, 1 consolidated report.
Dispatch 3 parallel specialized agents in isolated git worktrees to perform adversarial, independent analysis of a GitLab MR. Consolidate findings via confidence scoring, present actionable report, then offer structured actions (comment, create issues, approve).
Core principle: Independent adversarial review + confidence filtering + worktree isolation = high-signal feedback with minimal noise.
Announce at start: "I'm using OmniForge to review MR !{id}."
Prerequisites
glabCLI authenticated (glab auth statusto verify)- Git repository with remote pointing to GitLab
- Current working directory is in the git repo
Input Parsing
Accept any of: MR number (136), prefixed (!136), or full GitLab URL.
Extract MR ID. If URL provided, extract project path and MR IID.
The Process
digraph omnireview_flow {
rankdir=TB;
node [shape=box];
gather [label="Phase 1: Gather MR Data\nglab mr view + diff + comments"];
worktrees [label="Phase 2: Create 3 Worktrees\n(on MR source branch)"];
dispatch [label="Phase 3: Dispatch 3 OmniForge Agents\nIN PARALLEL"];
analyst [label="MR Analyst (OmniForge)\n(worktree 1)"];
codebase [label="Codebase Reviewer (OmniForge)\n(worktree 2)"];
security [label="Security Reviewer (OmniForge)\n(worktree 3)"];
consolidate [label="Phase 4: Consolidation\nconsolidator + worklist"];
report [label="Phase 5: Present Report\n(NEVER auto-post)"];
action [label="Phase 6: Action Menu\n(user chooses)"];
cleanup [label="Phase 7: Cleanup\n(ALWAYS runs)"];
gather -> worktrees -> dispatch;
dispatch -> analyst;
dispatch -> codebase;
dispatch -> security;
analyst -> consolidate;
codebase -> consolidate;
security -> consolidate;
consolidate -> report -> action -> cleanup;
}
Phase 1: Gather MR Data
Fetch ALL data before dispatching agents. Agents get data injected — they never re-fetch.
What ships with it
16 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/codebase-reviewer-prompt.md 8.0 KB
- references/consolidation-guide.md 11 KB
- references/mr-analyst-prompt.md 7.7 KB
- references/posting-guide.md 10 KB
- references/security-reviewer-prompt.md 9.9 KB
- scripts/omni_adjudicate.py 19 KB runs code
- scripts/omni_consolidate.py 19 KB runs code
- scripts/omni_digest.py 17 KB runs code
- scripts/omni_fetch_mr.py 20 KB runs code
- scripts/omni_fixprompt.py 22 KB runs code
- scripts/omni_glab_api.py 8.2 KB runs code
- scripts/omni_partition.py 12 KB runs code
- scripts/omni_post_review.py 32 KB runs code
- scripts/omni_prepare.py 27 KB runs code
- scripts/omni_validate_findings.py 4.0 KB runs code
- scripts/omni_wait.py 20 KB runs code
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.
- yesterday Changed 61e18bc2511e
- 2d ago Changed · +309 lines 2c853a95351d
- 7d ago First seen · 430 lines · 41 tokens per session scan B 3e495a5d3d94
omnireview-gitlab is a skill published in the GitHub repository nexiouscaliver/OmniForge (4 stars, last pushed 2d ago), licensed MIT. It adds 41 tokens to every session and 10,745 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
boundaries
Analyze Phoenix context boundaries and module coupling via mix xref. Use when checking cross-context calls, validating dependencies, before splitting modules, or reviewing architecture.
triage
Triage review findings interactively — approve, skip, or prioritize each issue. Use after /phx:review to filter findings before fixing.
techdebt
Analyze Elixir/Phoenix technical debt — duplicates, refactoring opportunities, credo issues. Use when asked about code quality, cleanup, or what to improve.
great_cto
Use when the CTO describes a feature, task, or project goal. Orchestrates the full SDLC pipeline automatically based on project type.
vertical-real-estate
Residential-proptech domain knowledge so architect / pm aren't naive when speccing real-estate products (listings, lead-crm, transaction-coordination, property-mgmt). Codifies MLS/IDX reality, listing status lifecycle + syndication canonical-source, long-cycle lead nurture, transaction-coordination as the high-pain…
skeptical-triage
Reusable 3-round self-challenge + arbiter pattern for filtering false positives from findings/verdicts. Use when the cost of a false-positive gate block exceeds the cost of 4 extra LLM turns.