Borrowing it
Nothing to install: this file belongs to Synerise/synerise-design. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Synerise/synerise-design/master/.claude/skills/push-mr/SKILL.mdgit clone --depth 1 https://github.com/Synerise/synerise-designWrote 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/synerise/synerise-design/push-mr)<a href="https://agentmods.dev/skills/synerise/synerise-design/push-mr"><img src="https://agentmods.dev/badge/skills/synerise/synerise-design/push-mr/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/synerise/synerise-design/push-mr"><img src="https://agentmods.dev/badge/skills/synerise/synerise-design/push-mr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 3 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00026 | $0.00762 |
| Opus 5 | $0.00013 | $0.00381 |
| Sonnet 5 | $0.00005 | $0.00152 |
| Haiku 4.5 | $0.00003 | $0.00076 |
Grade A, and why
push-mr 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 4d 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prerequisites
- The GitLab API token and project details are stored in the user's memory at
~/.claude/projects/-Users-biedronne-Documents-Work-DS2-synerise-design/memory/gitlab-credentials.md - GitLab URL: https://gitlab.synerise.com
- Project ID: 1171
- API Token: Read from the credentials file above (use
PRIVATE-TOKENheader)
Workflow
Step 1 — Push to origin
Push the current branch to origin:
git push -u origin HEAD
If the push fails (e.g., rejected), inform the user and stop.
Step 2 — Check for existing MR
Check if an MR already exists for the current branch:
BRANCH=$(git branch --show-current)
GET https://gitlab.synerise.com/api/v4/projects/1171/merge_requests?source_branch={BRANCH}&state=opened
If an MR already exists, skip to Step 4 (pipeline monitoring). Print the existing MR URL for the user.
Step 3 — Create the MR
If no MR exists, ask the user for a Jira task reference (e.g., STOR-1884). Use the AskUserQuestion tool — suggest a task reference extracted from the branch name if one is present.
Then analyze the changes on the branch to generate a summary of main changes. Use:
git log origin/master..HEAD --oneline
git diff origin/master..HEAD --stat
Create the MR via the GitLab API:
POST https://gitlab.synerise.com/api/v4/projects/1171/merge_requests
Body:
source_branch: current branch nametarget_branch:mastertitle: Use the conventional commit format from the latest commit message (or branch name)description: Use this template, filling in the changes and task reference:
Changes:
- <list main changes based on commits and diff>
Resolves task:
- <TASK_REFERENCE>
squash:trueremove_source_branch:true
Print the created MR URL for the user.
Step 4 — Monitor the pipeline
After push (whether MR was created or already existed), find the pipeline for the latest commit on the branch:
GET https://gitlab.synerise.com/api/v4/projects/1171/pipelines?ref={BRANCH}&order_by=id&sort=desc&per_page=1
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.
- 4d ago First seen · 106 lines · 26 tokens per session scan A 53b8279a4e40
push-mr is a skill published in the GitHub repository Synerise/synerise-design (96 stars, last pushed yesterday), licensed MIT. It adds 26 tokens to every session and 762 once invoked, about $0.0001 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-09-04.
Other skills, from other repositories
compiler-commit
Use when you want to verify compiler changes and commit with the correct convention. Runs tests, lint, and format, then commits with the [compiler] or [rust-compiler] prefix.
git-safety
Git safety rules. INVOKE WHEN: git push, force push, git reset, git clean, destructive git, push force, reset hard. NEVER force push or do destructive git operations.
release-safety
Release safety rules. INVOKE WHEN: yarn release, npm publish, release canary, release packages, publishing, skip checks, skip tests. NEVER skip checks or tests without explicit permission.
suanfish-design-system
A Chinese design system for creating and reviewing web interfaces, with multiple design perspectives working together. It focuses on React and Tailwind-based projects.
compiler-orchestrator
Orchestrate the Rust compiler port end-to-end. Discovers the current frontier, fixes failing passes, ports new passes, reviews, and commits in a loop.
migrate-radix-to-base
Migrates React projects and components from Radix UI to Base UI. Use when asked to migrate from radix, move to base-ui, convert radix primitives, or switch a shadcn project's base library. Handles single components ("migrate accordion") and whole projects.