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 skills/nexiouscaliver/omniforge/omnicreate-githubnpx skills add nexiouscaliver/OmniForge --skill omnicreate-githubgit clone --depth 1 https://github.com/nexiouscaliver/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/omnicreate-github)<a href="https://agentmods.dev/skills/nexiouscaliver/omniforge/omnicreate-github"><img src="https://agentmods.dev/badge/skills/nexiouscaliver/omniforge/omnicreate-github.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.00044 | $0.01455 |
| Opus 5 | $0.00022 | $0.00727 |
| Sonnet 5 | $0.00009 | $0.00291 |
| Haiku 4.5 | $0.00004 | $0.00145 |
Grade B, and why
omnicreate-github 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 6d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
sudo apt install gh # Debian/Ubuntu How it starts
The opening of the file, as written. The whole thing — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Pull Request Creator
Context
- Current git status: !
git status --porcelain - Current branch: !
git branch --show-current - Recent commits: !
git log --oneline -5 - GitHub remote: !
git remote -v | grep github | head -1 - gh version: !
gh version 2>/dev/null || echo "NOT_INSTALLED" - gh auth status: !
gh auth status 2>&1 || echo "NOT_AUTHENTICATED" - Unpushed commits: !
git log @{u}..HEAD --oneline 2>/dev/null || echo "NO_UPSTREAM" - Repo root: !
git rev-parse --show-toplevel 2>/dev/null || echo "NOT_A_GIT_REPO"
Your Task
Create a GitHub pull request using the mcp__omniforge__create_github_pr MCP tool.
Why MCP instead of raw bash? The MCP tool validates all inputs, uses safe subprocess execution (no shell interpretation), and provides structured error output — making it safe for use by all models without risk of shell injection.
Prerequisites
- Verify
ghis installed. If not, inform the user:brew install gh # macOS sudo apt install gh # Debian/Ubuntu - Verify the current directory is a git repository with a GitHub remote.
- Ensure there are commits to create a PR from (not on main/master without changes).
Pre-Flight Checklist
Before creating the PR, verify:
- Check environment: Verify
ghis installed and authenticated, git repo has GitHub remote - Check branch: If on main/master, inform user they need to create a feature branch first
- Check for changes: If no commits, inform user they need to commit changes first
- Warn about uncommitted changes: If working directory is dirty, warn user before proceeding
- Get repo root: Run
git rev-parse --show-toplevelto obtain the absolute path - Call MCP tool: Invoke
mcp__omniforge__create_github_prwithrepo_rootand any user-specified options - Report output: Show the PR URL, number, and any relevant details from the tool response
MCP Tool: mcp__omniforge__create_github_pr
Use this tool for all PR creation. It wraps gh pr create safely.
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.
- 6d ago First seen · 131 lines · 44 tokens per session scan B d24546873045
omnicreate-github is a skill published in the GitHub repository nexiouscaliver/OmniForge (4 stars, last pushed yesterday), licensed MIT. It adds 44 tokens to every session and 1,455 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
create-site
Creates a new Power Pages code site (SPA) using React, Angular, Vue, or Astro. Guides through the full process from initial concept to deployed site: requirements discovery, scaffolding, component planning, design, implementation, validation, and deployment. Use when the user wants to create, build, or scaffold a new…
add-cloud-flow
Integrates Power Automate cloud flows into a Power Pages site. Lists available flows, suggests relevant ones based on intent, identifies scenarios and web roles, creates metadata files, and generates client-side code to call flows. Handles both new flow registration and adding already-registered flows to additional…
configure-env-variables
Configures environment variables for Power Pages site settings to support ALM across environments. Creates environment variable definitions in Dataverse, guides the user through linking site settings to those variables via the Power Pages Management app, adds the variables to the solution, and generates a…
deploy-site
Deploys an existing Power Pages code site to a Power Pages environment using PAC CLI. Handles tooling verification, authentication, environment confirmation, building, and uploading. Use when the user wants to deploy, upload, or publish their code site.
add-teams
Adds Microsoft Teams connector to a Power Apps code app. Use when sending Teams messages, posting to channels, or integrating with Teams chat.
elixir-idioms
OTP/BEAM patterns and Elixir idioms — GenServer, Supervisor, Task, Registry, pattern matching, with chains, pipes. Use when designing processes or debugging BEAM issues.