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 Netcracker/qubership-ai-packages --skill enable-renovate-automergegit clone --depth 1 https://github.com/Netcracker/qubership-ai-packagesWrote 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/netcracker/qubership-ai-packages/enable-renovate-automerge)<a href="https://agentmods.dev/skills/netcracker/qubership-ai-packages/enable-renovate-automerge"><img src="https://agentmods.dev/badge/skills/netcracker/qubership-ai-packages/enable-renovate-automerge/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/netcracker/qubership-ai-packages/enable-renovate-automerge"><img src="https://agentmods.dev/badge/skills/netcracker/qubership-ai-packages/enable-renovate-automerge.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.00069 | $0.01499 |
| Opus 5 | $0.00034 | $0.00749 |
| Sonnet 5 | $0.00014 | $0.00300 |
| Haiku 4.5 | $0.00007 | $0.00150 |
Grade A, and why
enable-renovate-automerge 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 — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Enable Renovate automerge
Turn on Renovate automerge for a repository so dependency PRs merge themselves once CI is green — without lowering the bar for what "green" means.
Automerge is only as safe as the checks that gate it. The work here is
mostly about the gate: making sure a green PR means real tests and style
checks ran and passed, and registering exactly those checks as required.
Flipping automerge: true is the last and smallest step.
Apply this whether you configure one repository or sweep several: run the steps per repository.
Policy (read first)
- Automerge only behind a real gate. A green merge must mean tests (and style, where present) actually ran and passed. Never enable it where the only required checks are a PR-title linter, Conventional Commits, or a Docker-build smoke test.
- Renovate only. Dependabot has no platform-side automerge, so it is out of scope here; note it and move on, or treat migration to Renovate as separate work.
- Verify check names, don't guess them. A required status check matches
the check-run name GitHub reports exactly, and reusable workflows
report a compound
<caller-job> / <inner-job>name.
Step 1. Confirm the prerequisites
-
Bot is Renovate. Look for
renovate.json,.github/renovate.json, or arenovatekey inpackage.json. If the repository runs Dependabot (.github/dependabot.yml) instead, stop and report it as out of scope. -
You have admin. Editing rulesets and repository settings needs it:
gh api repos/<owner>/<repo> --jq .permissionsWithout
admin, prepare the changes as a PR plus a written ruleset instruction for the org owner instead of applying them. -
A real PR-triggered check exists. List the workflows that run on
pull_requestand find the jobs that run actual tests or style checks — not title validation, not a bare Docker build. If none exist, there is nothing to gate on: stop and report it. Creating a test workflow is separate work, out of scope here.
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 · 164 lines · 69 tokens per session scan A a1285379ee44
enable-renovate-automerge is a skill published in the GitHub repository Netcracker/qubership-ai-packages (4 stars, last pushed 3d ago), licensed Apache-2.0. It adds 69 tokens to every session and 1,499 once invoked, about $0.0003 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-08-31.
Other skills, from other repositories
github-release-management
Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management.
deployment-patterns
Deployment workflows, CI/CD pipeline patterns, Docker containerization, health checks, rollback strategies, and production readiness checklists for web applications. Use when setting up deployment infrastructure or planning releases.
agent-github-modes
Agent skill for github-modes - invoke with $agent-github-modes.
baby-sit
Monitor a GitHub pull request until CI is green, diagnose failures, and rerun only evidence-backed flaky GitHub Actions jobs.
chinese-git-workflow
A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.
atmos-hooks
Atmos hooks: lifecycle events, hook kinds, command/store/git/security hooks, step/steps hooks, when: conditions, scoping and overrides, toolchain integration, --skip-hooks, and Atmos Pro/local output.