Borrowing it
Nothing to install: this file belongs to kiali/openshift-servicemesh-plugin. 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/kiali/openshift-servicemesh-plugin/main/.claude/skills/track-ossm-acm-addon-backend-issues/SKILL.mdgit clone --depth 1 https://github.com/kiali/openshift-servicemesh-pluginWrote 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/kiali/openshift-servicemesh-plugin/track-ossm-acm-addon-backend-issues)<a href="https://agentmods.dev/skills/kiali/openshift-servicemesh-plugin/track-ossm-acm-addon-backend-issues"><img src="https://agentmods.dev/badge/skills/kiali/openshift-servicemesh-plugin/track-ossm-acm-addon-backend-issues/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/kiali/openshift-servicemesh-plugin/track-ossm-acm-addon-backend-issues"><img src="https://agentmods.dev/badge/skills/kiali/openshift-servicemesh-plugin/track-ossm-acm-addon-backend-issues.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00124 | $0.03790 |
| Opus 5 | $0.00062 | $0.01895 |
| Sonnet 5 | $0.00025 | $0.00758 |
| Haiku 4.5 | $0.00012 | $0.00379 |
Grade A, and why
track-ossm-acm-addon-backend-issues 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 11d 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 — 352 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Track OSSM-ACM Addon Controller Backend Issues for Fleet Service Mesh Plugin Impact
Analyze open backend controller issues in the OSSM-ACM addon (stolostron/multicluster-mesh-addon) and create or update GitHub tracking issues for any that affect the Fleet Service Mesh perspective plugin.
The plugin frontend lives in this repository under plugin/src/fleet-mesh/.
Tracking issues belong in
kiali/openshift-servicemesh-plugin
by default. Route work to
kiali/kiali when the required change is in
Kiali server code rather than the OSSMC fleet-mesh perspective.
Do NOT write to the stolostron repo. Access
stolostron/multicluster-mesh-addon read-only — use it only to list and read
backend controller issues and source code. Never create, edit, comment on, or
close issues (or PRs) in that repository. All tracking issues must be filed in
kiali/openshift-servicemesh-plugin or kiali/kiali.
When to use
Run this skill periodically — when new OSSM-ACM addon controller issues are filed in multicluster-mesh-addon, before sprint planning, or when the user asks to check for addon controller changes that might affect the fleet-mesh plugin. The skill is idempotent: running it multiple times will not create duplicate issues.
Prerequisites
ghCLI authenticated with access tostolostron/multicluster-mesh-addon,kiali/openshift-servicemesh-plugin, andkiali/kiali.- Read frontend source from the openshift-servicemesh-plugin repository root.
- Use
--repoon allghcommands — addon controller issues come from one repo, tracking issues are filed in another. - Read-only for stolostron: Only
gh issue listandgh issue view(and equivalent read commands) are permitted againststolostron/multicluster-mesh-addon. Do not rungh issue create,gh issue edit, orgh issue commentwith--repo stolostron/multicluster-mesh-addon.
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.
- 11d ago First seen · 352 lines · 124 tokens per session scan A 7f6b23cce5d1
track-ossm-acm-addon-backend-issues is a skill published in the GitHub repository kiali/openshift-servicemesh-plugin (8 stars, last pushed today), licensed Apache-2.0. It adds 124 tokens to every session and 3,790 once invoked, about $0.0006 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
systemic-issue-triage
Trigger: new issue, bug report, triage, backlog, issue flood, community report, root cause, dead-end, blocked user. Attack issues by root class, never one-by-one; fixes must shrink the system, not grow it.
triage-issue
Intelligently triage bug reports and error messages by searching for duplicates in Jira and offering to create new issues or add comments to existing ones. When an agent needs to: (1) Triage a bug report or error message, (2) Check if an issue is a duplicate, (3) Find similar past issues, (4) Create a new bug ticket…
bug-triage
Read all open bugs in production/qa/bugs/, re-evaluate priority vs. severity, assign to sprints, surface systemic trends, and produce a triage report. Run at sprint start or when the bug count grows enough to need re-prioritization.
browse-flows
Browse Power Automate environments and flows interactively. Use when the user wants to browse, list, or explore their flows and environments.
operating-cadence
Designs the rhythm an organization runs on — which reviews happen weekly, monthly and quarterly, what each one decides, who owns the numbers presented, and how a signal at the front line reaches the people who can act on it. Use this to set up a management operating system, fix a meeting calendar that produces no…
status
Display current FIRE project status and validate integrity of intents, work items, and runs.