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 plan-featuregit 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/plan-feature)<a href="https://agentmods.dev/skills/makigjuro/cloudstack-ai-plugins/plan-feature"><img src="https://agentmods.dev/badge/skills/makigjuro/cloudstack-ai-plugins/plan-feature/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/plan-feature"><img src="https://agentmods.dev/badge/skills/makigjuro/cloudstack-ai-plugins/plan-feature.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.00069 | $0.00846 |
| Opus 5.5 | $0.00028 | $0.00338 |
| Sonnet 5.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 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 — 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.
- 1mo 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 3mo ago), licensed MIT. It adds 69 tokens to every session and 846 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
alive:demo
Generate a believable, lived-in ALIVE world from a free-text persona description (custom path) or a deterministic sandbox preset. Routes the create/list/activate/deactivate/delete/status surface and orchestrates the 5-stage subagent generation pipeline.
alive:session-history
Revive sessions (quick or heavy), browse, and search — 'what happened recently?', 'find the session where we discussed X', 'revive yesterday's session'. For single-session recall and multi-session browsing. If the human needs to merge multiple sessions into one working context or detect conflicts between parallel…
alive:world
The human doesn't know what to work on, or wants to see everything at once. They need the big picture — what's active, what's stale, what needs attention. Renders a live world view grouped by ALIVE domain, then routes to open, tidy, find, history, or map.
triage
Triages a PR comment — from a bot (Copilot, CI) or a human reviewer. Routes to the triagehelper.py helper for identity checks, thread snapshotting, isolated-worktree fixes, and publish/reply/resolve mechanics; you classify the finding and apply a justified fix. --dry-run is fully read-only (investigation and a printed…
karpenter
Design, install, debug, review, plan capacity, audit scaling history, migrate from Cluster Autoscaler, and upgrade Karpenter v1.x on EKS. Covers NodePool, EC2NodeClass, NodeClaim, Spot diversity, disruption strategy, Pod Identity/IRSA, interruption queue, private clusters, AMI rotation, and GitOps integration. Use…
azure
Azure identity (Workload Identity, OIDC, Entra ID), resource tagging, AKS platform patterns, RBAC scoping, and production-readiness review — with Terraform generation.