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.
git clone --depth 1 https://github.com/tarujg/azure-support-ticketWrote 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/plugins/tarujg/azure-support-ticket/azure-support-ticket)<a href="https://agentmods.dev/plugins/tarujg/azure-support-ticket/azure-support-ticket"><img src="https://agentmods.dev/badge/plugins/tarujg/azure-support-ticket/azure-support-ticket.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
azure-support-ticket 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 7d 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.
What it actually says
{
"name": "azure-support-ticket",
"description": "File and manage Azure support tickets from the terminal via the az CLI support extension",
"version": "1.1.0",
"author": {
"name": "Taruj Goyal",
"url": "https://github.com/tarujg"
},
"homepage": "https://github.com/tarujg/azure-support-ticket",
"repository": "https://github.com/tarujg/azure-support-ticket",
"license": "MIT",
"keywords": [
"azure",
"support",
"ticket",
"az-cli",
"incident"
]
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 76 tokens a session between them. Each is measured on its own page, and each can be installed alone.
What ships with it
1 file beside plugin.json 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.
- 7d ago First seen · 20 lines scan A 7ee1343e2334
azure-support-ticket is a plugin published in the GitHub repository tarujg/azure-support-ticket (2 stars, last pushed 1mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
vanguard-frontier-agentic
Cloud and zero-trust agentic workflow marketplace for skills, agents, rules, MCP references, and compliance-aware architecture.
website-deploy
Deploy static websites to simple-host.app from your coding agent (inline JSON or tar.gz/zip). Each site gets a per-site backend (shared JSON state with atomic ops, append-only collections), built-in server-side visitor analytics, and can be connected to your own custom domain — subdomain via CNAME or apex via A record.
larouex-fullstack-builder
Complete Next.js + Azure/Railway full-stack website builder with 81 commands and 12 specialized agents including automated code review.
larouex-fullstack-builder
Complete Next.js + Azure/Railway full-stack website builder with 81 commands and 12 specialized agents including automated code review.
gcloud-gpu-agent
Launch Google Cloud GPU VMs (L4/A100/H100) and run code on them over SSH, straight from Claude Code.
azure-sdk-rust
Azure SDK patterns and best practices for Rust developers covering identity, Key Vault, storage, Cosmos DB, and Event Hubs.