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 qubership-agent-support-prgit 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-agent-support-pr)<a href="https://agentmods.dev/skills/netcracker/qubership-ai-packages/qubership-agent-support-pr"><img src="https://agentmods.dev/badge/skills/netcracker/qubership-ai-packages/qubership-agent-support-pr/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-agent-support-pr"><img src="https://agentmods.dev/badge/skills/netcracker/qubership-ai-packages/qubership-agent-support-pr.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.00058 | $0.02330 |
| Opus 5 | $0.00029 | $0.01165 |
| Sonnet 5 | $0.00012 | $0.00466 |
| Haiku 4.5 | $0.00006 | $0.00233 |
Grade A, and why
qubership-agent-support-pr 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 — 264 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Qubership agent support PR
Use this skill when the user asks to onboard a repository to Qubership baseline
agent support, install qubership-essentials, or create a PR that adds
generated APM assets for Claude, Codex, Cursor, or another requested harness.
The PR should be small: APM configuration, generated assets, generated-file metadata, linter exclusions, and validation evidence.
Target selection
Default targets for a new repository are claude, codex, and cursor.
Treat an existing apm.yml targets list as repository intent only when the
repository already appears onboarded to APM, for example when it also has
apm.lock.yaml, committed/generated target assets (.claude/, .codex/,
.cursor/), or repository documentation that names the supported harnesses.
Do not treat a newly created or bootstrap-only apm.yml as a narrower harness
signal by itself. If the repository has no durable APM metadata and no clear
harness-specific signal, use the default targets: claude,codex,cursor.
If the repository has clear harness-specific signals such as .codex/,
.claude/, .cursor/, agent settings, or repository documentation that points
to a narrower harness set, preserve the detected harness set and ask the user
before adding or removing targets.
Ask the user before changing targets whenever durable target intent is ambiguous. Do not silently broaden an existing onboarded single-harness setup to the default target set.
Repository read
Before editing, inspect the target repository:
git status --short --branch
git remote -v
if command -v rg >/dev/null 2>&1; then
rg --files --hidden \
-g '!.git/**' \
-g '!node_modules/**' \
-g 'apm.yml' \
-g 'apm.lock.yaml' \
-g '.gitattributes' \
-g '.apm/**' \
-g '.agents/**' \
-g '.claude/**' \
-g '.codex/**' \
-g '.cursor/**' \
-g '.github/super-linter.env' \
-g '.github/linters/**' \
-g '.github/workflows/**'
else
find . \
\( -path './.git' -o -path './node_modules' \) -prune -o \
\( \
-name 'apm.yml' -o \
-name 'apm.lock.yaml' -o \
-name '.gitattributes' -o \
-path './.apm/*' -o \
-path './.agents/*' -o \
-path './.claude/*' -o \
-path './.codex/*' -o \
-path './.cursor/*' -o \
-path './.github/super-linter.env' -o \
-path './.github/linters/*' -o \
-path './.github/workflows/*' \
\) -print
fi
What ships with it
1 file 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 · 264 lines · 58 tokens per session scan A 102626a8a0c9
qubership-agent-support-pr is a skill published in the GitHub repository Netcracker/qubership-ai-packages (4 stars, last pushed 3d ago), licensed Apache-2.0. It adds 58 tokens to every session and 2,330 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…