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 makigjuro/cloudstack-ai-plugins --skill lintgit clone --depth 1 https://github.com/makigjuro/cloudstack-ai-pluginsWrote 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/makigjuro/cloudstack-ai-plugins/lint)<a href="https://agentmods.dev/skills/makigjuro/cloudstack-ai-plugins/lint"><img src="https://agentmods.dev/badge/skills/makigjuro/cloudstack-ai-plugins/lint/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/makigjuro/cloudstack-ai-plugins/lint"><img src="https://agentmods.dev/badge/skills/makigjuro/cloudstack-ai-plugins/lint.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.00067 | $0.00931 |
| Opus 5.5 | $0.00027 | $0.00372 |
| Sonnet 5.5 | $0.00013 | $0.00186 |
| Haiku 4.5 | $0.00007 | $0.00093 |
Grade A, and why
lint 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lint
Run all project linters and report violations. Optionally fix auto-fixable issues.
Configuration
Read cloudstack.json from the project root at the start of execution. Extract relevant fields:
SOLUTION=backend.solutionPath(default: find*.sln)FRONTEND_PATH=frontend.path(default:web)CHARTS_PATH=infrastructure.chartsPath(default:deploy/charts)TF_PATH=infrastructure.terraformPath(default:infra/terraform/modules)
If cloudstack.json does not exist, auto-detect by scanning the project structure.
Arguments
--fixorfix-- Apply auto-fixes (default: report only)backend-- Only lint C# codefrontend-- Only lint frontend codehelm-- Only lint Helm chartsterraform-- Only lint Terraform/Terragrunt code
If no argument is given, lint everything in report-only mode.
Backend (.NET)
Check formatting violations (report only):
dotnet format {SOLUTION} --verify-no-changes --verbosity normal
Fix formatting violations:
dotnet format {SOLUTION} --verbosity normal
Frontend (React/TypeScript)
Check lint violations (report only):
cd {FRONTEND_PATH} && npm run lint
Fix auto-fixable violations:
cd {FRONTEND_PATH} && npm run lint:fix
Check TypeScript types:
cd {FRONTEND_PATH} && npm run type-check
Helm Charts
Lint all charts in {CHARTS_PATH}/:
# Discover and lint all charts
for chart in $(ls {CHARTS_PATH}/); do
helm lint {CHARTS_PATH}/$chart
done
Template render check (catches template errors without deploying):
for chart in $(ls {CHARTS_PATH}/); do
helm template test {CHARTS_PATH}/$chart > /dev/null
done
Terraform / Terragrunt
Determine the Terraform root directory from {TF_PATH} (e.g., if TF_PATH is infra/terraform/modules, the root for format checks is infra).
Validate Terraform modules:
# Find all Terraform module directories and validate each
for dir in $(find {TF_ROOT} -name "*.tf" -exec dirname {} \; | sort -u); do
echo "=== Validating $dir ==="
terraform -chdir="$dir" init -backend=false -input=false 2>/dev/null
terraform -chdir="$dir" validate
done
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 · 121 lines · 67 tokens per session scan A 1451beb931f9
lint is a skill published in the GitHub repository makigjuro/cloudstack-ai-plugins (1 stars, last pushed 3mo ago), licensed MIT. It adds 67 tokens to every session and 931 once invoked, about $0.0003 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-31.
Other skills, from other repositories
linux
Linux administration and networking diagnostics — DNS, load balancing, VPCs, kernel tuning, and connectivity troubleshooting.
chaos
Design, run, and debug Chaos Engineering experiments on Kubernetes using Litmus Chaos v3 and Chaos Mesh v2. Covers fault injection (pod-delete, network-loss, CPU stress, node-drain), steady-state hypothesis probes, GameDay runbooks, scheduled experiments, DORA feedback loop, and RBAC setup. Use when asked to "inject a…
azure-diagnostics
Investigate AKS, VM, App Service, Functions and messaging incidents using scoped evidence.
debug
Structured platform troubleshooting — classifies the problem layer, collects evidence, forms a root-cause hypothesis, and proposes a fix with validation and rollback steps.
ia-verification-before-completion
Enforces fresh verification evidence before any completion claim. Use when about to claim "tests pass", "bug fixed", "done", "ready to merge", handing off work, or before editing when a request has ambiguous scope.
ia-c-systems
C patterns for systems code, libraries, and native extensions: module layout, function decomposition, status-enum errors, memory safety, undefined behavior, and performance measurement. Use when writing, reviewing, refactoring, or debugging C, working with malloc lifetimes, buffer overflows, sanitizers, or Valgrind…