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/run-testsnpx skills add makigjuro/cloudstack-ai-plugins --skill run-testsgit 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.00058 | $0.01148 |
| Opus 5 | $0.00029 | $0.00574 |
| Sonnet 5 | $0.00012 | $0.00230 |
| Haiku 4.5 | $0.00006 | $0.00115 |
Grade A, and why
run-tests 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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Run Tests -- Smart Change-Aware Test Selection
Run tests based on what changed. Auto-detects affected services from git diff and runs only their test projects instead of the full suite.
Configuration
Read cloudstack.json from the project root at the start of execution. Extract relevant fields:
SOLUTION=backend.solutionPath(default: find*.sln)SERVICES=backend.services[](default: discover from project structure)
If cloudstack.json does not exist, auto-detect by scanning the project structure.
1. Parse Arguments
Determine from user input:
- MODE:
unit(default),integration, orall - SERVICE: optional service name or slug
- Explicit
--allflag: runs both unit and integration for all projects
| User says | MODE | SERVICE |
|---|---|---|
/run-tests |
unit | (auto-detect) |
/run-tests {service} |
unit | {service} |
/run-tests --integration |
integration | (auto-detect) |
/run-tests --integration {service} |
integration | {service} |
/run-tests --all |
all | (auto-detect) |
/run-tests --all {service} |
all | {service} |
2. Resolve Test Projects
Auto-detection approach
Use git diff to identify changed files and map them to test projects:
# Get changed files relative to main
CHANGED_FILES=$(git diff origin/main...HEAD --name-only 2>/dev/null; git diff --name-only 2>/dev/null; git diff --name-only --cached 2>/dev/null)
Map changed source paths to their corresponding test projects:
- For each changed file under a service's source path, find matching test projects by convention (e.g.,
{ServicePath}.Tests.Unit,{ServicePath}.Tests.Integration,{ProjectPrefix}.Tests.*). - If shared/foundational code changed (shared domain, shared infrastructure), fall back to running the full test suite.
- If only non-source files changed (docs, config, CI), report "No tests affected" and offer to run the full suite.
Explicit service mode
When a service name is provided, look up its path from cloudstack.json and find test projects matching that service's project prefix.
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 · 139 lines · 58 tokens per session scan A 4457b0bd3433
run-tests is a skill published in the GitHub repository makigjuro/cloudstack-ai-plugins (1 stars, last pushed 1mo ago), licensed MIT. It adds 58 tokens to every session and 1,148 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.