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 agentmods add skills/makigjuro/cloudstack-ai-plugins/lintnpx skills add makigjuro/cloudstack-ai-plugins --skill lintgit clone --depth 1 https://github.com/makigjuro/cloudstack-ai-pluginsWhat 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 | $0.00067 | $0.00931 |
| Opus 5 | $0.00034 | $0.00465 |
| Sonnet 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 2d 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.
- 2d 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 1mo ago), licensed MIT. It adds 67 tokens to every session and 931 once invoked, about $0.0003 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
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
azsdk-common-pipeline-analysis
Analyze Azure SDK CI/CD pipeline failures into a structured diagnosis, and define the required output format. Load this skill before calling azsdkanalyzepipeline, which returns raw failure data that this skill interprets and formats. USE FOR: "pipeline failed", "build failure", "CI check failing", "tests failing in…
omh-buzz
This is a Hermes-native buzz workflow skill.
redteam-api-detail-pack
Domain routing and boundary guidance for authorized API security testing, including BOLA/IDOR, authentication bypass, mass assignment, missing rate limits, and GraphQL issues. Use when a task belongs to the API testing domain and needs scope, evidence, pivot, or exit criteria.
android-pentest
安卓应用渗透测试 — APK分析、Hook、自动化测试、运行态驱动、签名恢复、抓包分析.
auditing-azure-active-directory-configuration
Auditing Microsoft Entra ID (Azure Active Directory) configuration to identify risky authentication policies, overly permissive role assignments, stale accounts, conditional access gaps, and guest user risks using AzureAD PowerShell, Microsoft Graph API, and ScoutSuite.