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 create-prgit 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/create-pr)<a href="https://agentmods.dev/skills/makigjuro/cloudstack-ai-plugins/create-pr"><img src="https://agentmods.dev/badge/skills/makigjuro/cloudstack-ai-plugins/create-pr/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/create-pr"><img src="https://agentmods.dev/badge/skills/makigjuro/cloudstack-ai-plugins/create-pr.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.00046 | $0.01003 |
| Opus 5.5 | $0.00018 | $0.00401 |
| Sonnet 5.5 | $0.00009 | $0.00201 |
| Haiku 4.5 | $0.00005 | $0.00100 |
Grade A, and why
create-pr 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Pull Request
Create a pull request for the current branch with a structured description.
Configuration
Read cloudstack.json from the project root at the start of execution. Extract relevant fields:
REPO_OWNER/REPO_NAME=repository.owner/repository.name(default: detect fromgit remote -v)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 and parsing the GitHub remote URL.
Arguments
{issue}-- GitHub issue number to link (optional). If not provided, attempt to extract from the branch name.
Prerequisites
- You must be on a feature branch (not main)
- All changes should be committed (warn if working tree is dirty)
- Branch should have at least one commit ahead of main
Process
-
Gather context:
git status-- check for uncommitted changes, warn if dirty.git log origin/main..HEAD --oneline-- list all commits on this branch.git diff origin/main...HEAD --stat-- summary of changed files.- Extract issue number from branch name or argument.
-
Analyze changes:
- Identify which layers were modified (Domain, Application, Infrastructure, Host, Frontend, Tests).
- Detect affected services by checking paths against known service directories:
git diff origin/main...HEAD --name-only | grep -oP 'src/\K[^/]+' | sort -u - Detect what was added vs changed vs removed from the diff stat.
- Check if documentation may need updating (new endpoints, entities, or events).
-
Push and create PR:
- Push the branch to origin with
-uflag. - Create the PR using MCP.
- Push the branch to origin with
PR Body Format
## Summary
{1-3 bullet points describing what this PR does}
Closes #{issue-number}
## Affected Services
{List only services that were actually modified}
## Changes
- **Domain:** {changes or "No changes"}
- **Application:** {changes or "No changes"}
- **Infrastructure:** {changes or "No changes"}
- **Endpoints:** {changes or "No changes"}
- **Frontend:** {changes or "No changes"}
- **Tests:** {changes or "No changes"}
## Test Plan
- [ ] Unit tests pass
- [ ] Integration tests pass (if applicable)
- [ ] Frontend lint clean (if applicable)
- [ ] Frontend type-check clean (if applicable)
- [ ] Helm lint clean (if applicable)
- [ ] Terraform validate clean (if applicable)
- [ ] Architecture check passes
- [ ] {Any feature-specific manual verification steps}
Generated with [Claude Code](https://claude.com/claude-code)
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 · 119 lines · 46 tokens per session scan A 68c124338ed3
create-pr is a skill published in the GitHub repository makigjuro/cloudstack-ai-plugins (1 stars, last pushed 3mo ago), licensed MIT. It adds 46 tokens to every session and 1,003 once invoked, about $0.0002 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
renovate
Generate renovate.json covering all dependency file types used in a repo, emit a GitHub Actions workflow that validates renovate.json on every PR, or generate a pre-commit hook for local validation.
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…
gitops
Flux CD and Argo CD — two modes. debug: five structured debug workflows for live clusters (installation, source, HelmRelease, Kustomization, ResourceSet) producing a five-section report. audit: six-phase read-only repo analysis (discovery, validation, API compliance, best practices, security) producing a prioritised…
commit
Analyze git diffs or staged changes and generate conventional commit messages that explain WHY a change was made. Supports auto-detecting type and scope, intelligent file staging, and interactive overrides. Use when asked to "write a commit message", "generate a commit", "describe my changes", "commit this"…
secrets-scan
Scans git-tracked files for leaked secrets. Triggers - secrets scan, find credentials, leaked keys, security audit.
pr-sweep
Use when you want to sweep all open pull requests across all repos, triage their status, run code reviews on unreviewed PRs, merge what's ready, fix quick blockers, and produce a full status report. Trigger when the user says "check my PRs", "close out open PRs", "what's the status of my PRs", "sweep my PRs", "PR…