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 UI5/plugins-coding-agents --skill fix-xml-globalsgit clone --depth 1 https://github.com/UI5/plugins-coding-agentsWrote 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/ui5/plugins-coding-agents/fix-xml-globals)<a href="https://agentmods.dev/skills/ui5/plugins-coding-agents/fix-xml-globals"><img src="https://agentmods.dev/badge/skills/ui5/plugins-coding-agents/fix-xml-globals/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/ui5/plugins-coding-agents/fix-xml-globals"><img src="https://agentmods.dev/badge/skills/ui5/plugins-coding-agents/fix-xml-globals.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Prompt Injection · line 54 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
- high Prompt Injection · line 287 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
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.00231 | $0.06011 |
| Opus 5.5 | $0.00092 | $0.02404 |
| Sonnet 5.5 | $0.00046 | $0.01202 |
| Haiku 4.5 | $0.00023 | $0.00601 |
Grade A, and why
fix-xml-globals 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 1mo 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 — 490 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fix XML Views/Fragments Global Access
This skill fixes XML view and fragment issues that the UI5 linter detects but cannot auto-fix because they require understanding of module paths and handler locations.
Linter Rules Handled
| Rule ID | Message Pattern | This Skill's Action |
|---|---|---|
no-globals |
Access of global variable '...' (...) | Add core:require and use local name |
no-ambiguous-event-handler |
Event handler '...' must be prefixed by a dot '.' or refer to a local name | Add . prefix for controller methods or add core:require for modules |
no-deprecated-api |
Usage of space-separated list '...' in template:require | Convert to object notation |
When to Use
Apply this skill when you see linter output like:
Main.view.xml:15:5 error Access of global variable 'formatter' (my.app.model.formatter) no-globals
Main.view.xml:20:5 warning Event handler 'onPress' must be prefixed by a dot '.' or refer to a local name no-ambiguous-event-handler
Main.view.xml:25:5 error Usage of space-separated list 'formatter helper' in template:require no-deprecated-api
Fix Strategy
1. no-globals - Fix Global Variable Access with core:require
When a formatter, type, or utility function is accessed via global namespace (e.g., my.app.formatter.formatDate), add a core:require declaration and use the local name.
Step 1: Add xmlns:core namespace if not present
<mvc:View
xmlns:mvc="sap.ui.core.mvc"
xmlns:core="sap.ui.core"
xmlns="sap.m">
Step 2: Add core:require on the nearest control that uses the module
Place core:require on the control that uses the global reference. If multiple controls use the same module, place it on their nearest common ancestor. See the "core:require Placement Rules" section below for details.
<!-- Single usage — core:require on the control itself -->
<Text core:require="{formatter: 'my/app/model/formatter'}"
text="{path: 'date', formatter: 'formatter.formatDate'}" />
What ships with it
18 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.
- references/placement-and-binding.md 12 KB
- scripts/__fixtures__/nested_function_shadow.js 158 B runs code
- scripts/__fixtures__/no_this.js 187 B runs code
- scripts/__fixtures__/not_found.js 91 B runs code
- scripts/__fixtures__/this_in_comment.js 181 B runs code
- scripts/__fixtures__/this_in_string.js 186 B runs code
- scripts/__fixtures__/uses_this_alias.js 138 B runs code
- scripts/__fixtures__/uses_this_arrow.js 126 B runs code
- scripts/__fixtures__/uses_this_bare.js 177 B runs code
- scripts/__fixtures__/uses_this_member.js 154 B runs code
- scripts/__fixtures__/uses_this_nested_in_if.js 263 B runs code
- scripts/__fixtures__/xml/has_bind.fragment.xml 257 B
- scripts/__fixtures__/xml/multi_line.fragment.xml 381 B
- scripts/__fixtures__/xml/needs_bind.fragment.xml 308 B
- scripts/__fixtures__/xml/no_this_no_bind.fragment.xml 216 B
- scripts/README.md 3.6 KB
- scripts/verify-this-bind.js 18 KB runs code
- scripts/verify-this-bind.test.js 11 KB runs code
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.
- 1mo ago First seen · 490 lines · 231 tokens per session scan A 0ac718028e37
fix-xml-globals is a skill published in the GitHub repository UI5/plugins-coding-agents (40 stars, last pushed yesterday), licensed Apache-2.0. It adds 231 tokens to every session and 6,011 once invoked, about $0.0009 per session on Opus 5.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-30.
Other skills, from other repositories
agenttrace-session-audit
Audit local AI coding-agent sessions with agenttrace for cost, tool failures, latency, anomalies, health, diffs, and CI gates.
octocode-research
Use when code must be checked, not assumed: trace connections (callers, imports, cross-repo wiring, what breaks if I change it), locate behavior, map a system, diagnose a failure, RCA. Also for external repositories, npm packages, upstream/prior art, and general research. Plan a coding flow before writing, validate it…
ask-codex
Consult OpenAI Codex for investigation, debugging, or code review. Use when user explicitly asks to "ask codex", "check with codex", "codex review", or as a last resort when stuck after 4+ failed attempts at debugging, investigation, or bug fix and completely out of ideas. Codex is slow (2-5 min), so only escalate…
root-cause-investigator
Systematic root cause analysis for errors, bugs, and unexpected behaviors using 5-Why methodology. Use when user reports errors, build failures, test failures, performance issues, integration problems, or any "it's not working" scenarios.
code-review-web
Review web application code for bugs, security issues, performance problems, and stack-specific anti-patterns. Use this skill whenever the user wants to review code, debug a production issue, investigate a build failure, audit security, or check a PR before merging. Triggers on code review, review my code, debug…
logic-lens
AI-powered Claude Code skill that performs deep code review using formal logic and reasoning frameworks to detect bugs, anti-patterns, and security risks beyond what linters catch.