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-repository-compliancegit 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-repository-compliance)<a href="https://agentmods.dev/skills/netcracker/qubership-ai-packages/qubership-repository-compliance"><img src="https://agentmods.dev/badge/skills/netcracker/qubership-ai-packages/qubership-repository-compliance/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-repository-compliance"><img src="https://agentmods.dev/badge/skills/netcracker/qubership-ai-packages/qubership-repository-compliance.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.00042 | $0.03868 |
| Opus 5 | $0.00021 | $0.01934 |
| Sonnet 5 | $0.00008 | $0.00774 |
| Haiku 4.5 | $0.00004 | $0.00387 |
Grade A, and why
qubership-repository-compliance 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 9d 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 — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Qubership repository compliance
Prerequisite
Require gh on PATH. Derive the GitHub host from the target repository remote and require
gh auth status --active --hostname <host> to succeed. Never use --show-token. If gh is missing or authentication
fails, stop and tell the user to install or authenticate GitHub CLI.
Do not query the repository Actions-permissions API (repos/{owner}/{repository}/actions/permissions*); none of the
catalog checks depends on it. If a tool reports a 403 from this endpoint, ignore it and omit it from unavailable
evidence and the user report.
If any other gh operation fails because the active token lacks permission, stop that operation and tell the user
which repository operation needs additional access. Do not treat missing access as a compliance violation or request
broader permissions yourself.
Permission boundary
Default to Audit. Audit is read-only: do not edit files, change GitHub settings, create pull requests, commit, push,
merge, or close anything.
Apply reuses a complete Audit from the current task and rechecks only confirmed checks; run a full Audit only when
none exists. Show the descriptive check names, exact targets, proposed file and external changes, and unavailable
prerequisites. Apply only the checks or batch the user confirms, even if the initial request says to fix everything.
Permission for a target repository does not cover Netcracker/.github or Netcracker/qubership-workflow-hub.
README remediation is always separate from other Apply work. Never include FILE-001 in an Apply batch. When it
fails, ask whether the user wants the assistant to prepare a README change. After approval, edit only the README, show
its diff, and ask the user to accept or revert it before committing, publishing, or combining it with other changes.
If the user rejects it, revert only the assistant's README edit.
Keep finding IDs internal for catalog evaluation and fix routing. Outside the report table's ID column, use a clear
descriptive check name in the user's language in every report, question, status, and confirmation. Accept an ID supplied
by the user and map it to the descriptive name without asking them to remember the catalog.
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.
- 9d ago Changed 0d8f91ea7f2d
- 12d ago First seen · 144 lines · 42 tokens per session scan A d7547ec94724
qubership-repository-compliance is a skill published in the GitHub repository Netcracker/qubership-ai-packages (4 stars, last pushed 3d ago), licensed Apache-2.0. It adds 42 tokens to every session and 3,868 once invoked, about $0.0002 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
open-sourcing
This skill should be used when the user asks to "open source this project", "prepare this repository for public release", "make this repo public", "check open-source readiness", "choose a license for this project", or "set up release automation" ahead of a public launch. Provides a release-readiness workflow covering…
repo-prep
Interactively prepare a code repository for publication — LICENSE, NOTICE, AUTHORSHIP, README sections, package metadata, .gitignore, community docs (CONTRIBUTING/CODEOFCONDUCT/SECURITY/CHANGELOG), .github templates (issues/PR/CI/dependabot), a promo "more from the author" block, and conditional EU/Germany legal…
compliance-license-audit
Interactive open-source license compliance audit to identify all dependency licenses, flag risks, and detect license incompatibilities.
compliance-notice-generate
Generate NOTICE, ATTRIBUTION, or THIRD-PARTY-NOTICES files from detected dependency licenses to fulfill open-source license obligations.
open-source
Open source readiness best practices. Covers licensing, documentation, community health, CI/CD, compliance, legal, and packaging. USE WHEN: user mentions "open source", "license", "LICENSE", "CONTRIBUTING", "CODEOFCONDUCT", "CHANGELOG", "open source readiness", "community health", "OSS compliance", "SPDX", "CLA"…
community-health
Guide for setting up GitHub community health files for open source repositories. Use when preparing repos for public release, adding community standards files, or configuring issue/PR templates.