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/plan-featurenpx skills add makigjuro/cloudstack-ai-plugins --skill plan-featuregit 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.00069 | $0.00846 |
| Opus 5 | $0.00034 | $0.00423 |
| Sonnet 5 | $0.00014 | $0.00169 |
| Haiku 4.5 | $0.00007 | $0.00085 |
Grade A, and why
plan-feature 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan Feature
When the user describes a feature they want to build, produce a structured feature plan. Explore the codebase first to ground the plan in what already exists.
Configuration
Read cloudstack.json from the project root at the start of execution. Extract relevant fields:
SERVICES=backend.services[](default: discover from project structure)
If cloudstack.json does not exist, auto-detect by scanning the project structure.
Process
Phase 0: Enter Plan Mode
Always start by calling EnterPlanMode before doing anything else. Feature planning is a planning activity -- it requires codebase exploration, scope clarification, and user alignment before producing the plan. Plan mode ensures you can explore freely and get user sign-off on the approach. Exit plan mode with ExitPlanMode only after the plan is complete and the user has approved it.
- Clarify scope -- Ask the user if the feature description is ambiguous. Identify which service(s) are affected.
- Explore existing code -- Search for related entities, handlers, endpoints, and tests that the feature touches or extends.
- Produce the plan -- Output a structured plan using the format below.
Plan Format
# Feature: {Title}
## Summary
One-paragraph description of the feature and the problem it solves.
## Affected Services
{List services from cloudstack.json or discovered from project structure, with checkboxes for each affected one}
## Acceptance Criteria
- [ ] AC1: ...
- [ ] AC2: ...
## Implementation Tasks
### Domain
- [ ] {task description} -- `{file path or new file}`
### Application
- [ ] {task description} -- `{file path or new file}`
### Infrastructure
- [ ] {task description} -- `{file path or new file}`
### Host / Endpoints
- [ ] {task description} -- `{file path or new file}`
### Frontend
- [ ] {task description} -- `{file path or new file}`
### Tests
- [ ] {task description} -- `{file path or new file}`
## Open Questions
- Any unresolved design decisions or trade-offs to call out.
## Out of Scope
- Anything explicitly excluded from this feature.
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 · 97 lines · 69 tokens per session scan A 39d2161b941c
plan-feature is a skill published in the GitHub repository makigjuro/cloudstack-ai-plugins (1 stars, last pushed 1mo ago), licensed MIT. It adds 69 tokens to every session and 846 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.