Borrowing it
Nothing to install: this file belongs to Netcracker/qubership-ai-packages. 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/Netcracker/qubership-ai-packages/main/.agents/skills/qubership-workflow-conventions/SKILL.mdgit 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/qubership-workflow-conventions)<a href="https://agentmods.dev/skills/netcracker/qubership-ai-packages/qubership-workflow-conventions"><img src="https://agentmods.dev/badge/skills/netcracker/qubership-ai-packages/qubership-workflow-conventions/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/qubership-workflow-conventions"><img src="https://agentmods.dev/badge/skills/netcracker/qubership-ai-packages/qubership-workflow-conventions.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.00059 | $0.02009 |
| Opus 5 | $0.00030 | $0.01005 |
| Sonnet 5 | $0.00012 | $0.00402 |
| Haiku 4.5 | $0.00006 | $0.00201 |
Grade A, and why
qubership-workflow-conventions 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 — 197 lines — stays where its author put it; the contents beside it link to each section on GitHub.
qubership-workflow-conventions
Single source of truth for any GitHub Actions workflow that consumes the
Qubership ecosystem (netcracker/qubership-workflow-hub actions,
Netcracker/.github templates).
Companion skills (navigators)
qubership-templates-guide— fork-able Netcracker workflow-templates catalog.qubership-actions-guide— actions catalog, domain guides, and the Pin table for SHAs.
All rules live in this file.
Clarify before acting
Before designing any workflow, establish context with the minimum necessary questions. Never ask for information that can be read from a file.
Step 0 — one question first
Ask exactly one question:
"Do you have an existing workflow and/or
.qubership/config files, or are we starting from scratch?"
If the user has already provided a file or it is open in the IDE — skip this question and go straight to Path A.
Path A — existing workflow or configs
Read the workflow and any config files it references. Load the relevant domain guide from
qubership-actions-guide (docker.md, helm.md, security.md, release.md, notifications.md,
maven.md, cleanup.md, utilities.md, pr.md, cla.md) and use its migration table. Ask only about what
is missing after reading. Return the full updated workflow file — preserve existing structure, change only what needs changing.
Path B — starting from scratch
Hand off to qubership-actions-guide Step 1 — it routes to the relevant domain guide
(docker.md, helm.md, security.md, release.md, notifications.md, maven.md,
cleanup.md, utilities.md, pr.md, cla.md) or returns to the catalog for operations
without a guide (npm, Python).
Clarifying questions for catalog-only operations live in the catalog (see qubership-actions-guide → Publishing).
Infer the trigger from the request — do not ask unless truly ambiguous.
See workflow-patterns.md → Trigger rules for the three standard patterns.
Workflow design process
After Clarify before acting:
What ships with it
4 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.
- 12d ago First seen · 197 lines · 59 tokens per session scan A 4e73031615cf
qubership-workflow-conventions is a skill published in the GitHub repository Netcracker/qubership-ai-packages (4 stars, last pushed 3d ago), licensed Apache-2.0. It adds 59 tokens to every session and 2,009 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
import-prom-rule
Bulk import of a Prometheus alert rule YAML file (create a whole set of rules at once). Dedicated to handling a remote URL or local YAML text, automatically parsing the three formats groups / a plain rules array / a single rule. ⚠️ Do not use this skill for single-rule creation — when the user describes a single alert…
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.
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…
atmos-profiles
Atmos profiles: profile directories, --profile and ATMOSPROFILE activation, profile merge behavior, environment switching, and routing profile-specific auth/toolchain/config overrides.
managing-github-actions-secrets
Creates and updates GitHub Actions secrets for PostHog workflows. Use when adding a new CI secret, rotating an existing secret, wiring a workflow to an API token, package registry credential, deploy key, or any value referenced via ${{ secrets. }} in .github/workflows/.
webhook-management
Configure and validate CCAM webhook targets across supported chat, incident, automation, and generic providers. Use when listing provider requirements, creating or updating a target, scoping it to alert rules, sending a test notification, reviewing delivery history, or deleting a target.