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 skills add Jarroslav/agentic-os --skill mr-submitgit clone --depth 1 https://github.com/Jarroslav/agentic-osWrote 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/jarroslav/agentic-os/mr-submit)<a href="https://agentmods.dev/skills/jarroslav/agentic-os/mr-submit"><img src="https://agentmods.dev/badge/skills/jarroslav/agentic-os/mr-submit/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/skills/jarroslav/agentic-os/mr-submit"><img src="https://agentmods.dev/badge/skills/jarroslav/agentic-os/mr-submit.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.00159 | $0.02277 |
| Opus 5.5 | $0.00064 | $0.00911 |
| Sonnet 5.5 | $0.00032 | $0.00455 |
| Haiku 4.5 | $0.00016 | $0.00228 |
Grade A, and why
mr-submit 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 2mo 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 — 260 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commit, Push, and Open MR/PR
Blast radius R3 — the create step reaches an external service. Treat MR/PR creation as gated: it fires only on a direct user request, never as a side effect of another skill.
This skill hardcodes no VCS platform. Commit and branch shapes come from the git-workflow guide; the create/check mechanism comes from a runtime adapter declared in the project guide. Everything platform-specific is resolved, not assumed.
When this runs
Trigger only on an explicit user ask to commit, push, or open a review request.
sdlc-auto does not call this skill on its own — the autonomous
pipeline never self-triggers commit/push/MR side effects.
Route by request:
| User says | Do |
|---|---|
| "commit changes" | Commit only (ticket required) |
| "push changes" | Push only |
| "create MR" / "open a PR" | Full push + create workflow |
Inputs
| Source | Provides |
|---|---|
.agentic/guides/standards/git-workflow.md |
Commit pattern, branch pattern, MR title format |
.agentic/guides/project.md → ## Review Adapter |
Adapter status, adapter handle, instructions, body template |
references/mr-adapters.md |
Adapter contract + sample configs (check/create operations, auth notes, no-adapter fallback) |
| Conversation context | Ticket reference, user request type |
Outputs
- A commit whose message begins with a validated ticket reference.
- A pushed branch tracking
origin. - A created MR/PR (URL surfaced to the user), unless one already exists.
- A run-journal entry at
.agentic/runs/<branch>.json. - A user-gated handoff suggestion to
mr-watch(never auto-invoked).
Step 0 — Load conventions and resolve the adapter
Read .agentic/guides/standards/git-workflow.md. If it is not present, stop
immediately and emit this marker verbatim:
[GUIDE MISSING] `.agentic/guides/standards/git-workflow.md` not found.
Run the `repo-guides` skill to generate project guides before using `mr-submit`.
repo-guides is a hard upstream dependency — without the guide there is no
convention to enforce, so do not fall through to defaults.
What ships with it
2 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.
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.
- 2mo ago First seen · 260 lines · 159 tokens per session scan A a5ed2894aad4
mr-submit is a skill published in the GitHub repository Jarroslav/agentic-os (0 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 159 tokens to every session and 2,277 once invoked, about $0.0006 per session on Opus 5.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 skills, from other repositories
review-implement-phase
Implements triaged review actions, commits focused fixes, and posts Done plus resolves threads. Use when the user wants only the implementation phase of the review-framework workflow.
github-pr-workflow
Prepare a GitHub pull request from a feature branch — branch hygiene, commit shape, title/body, verification notes, screenshots for UI work, and replies to review comments.
review-delta
Review only changes since last commit using impact analysis. Token-efficient delta review with automatic blast-radius detection.
github-contributor
A step-by-step guide for contributing code, tests, documentation, or build changes to open-source projects you do not maintain. It explains how to prepare a pull request that follows the project’s rules and is easier for maintainers to review.
hero-diff-highlight
A dark code editor reveals a red deletion then a green addition with a soft pulse. Function: PR / code-change explainer.
git-pr-workflows-git-workflow
Guide changes through code checks, testing, commits, and pull request preparation. Use when coordinating a complete Git workflow and verifying readiness for collaboration.