Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add makigjuro/cloudstack-ai-plugins/plugin install dev-workflowWrote 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/complete-task)<a href="https://agentmods.dev/skills/makigjuro/cloudstack-ai-plugins/complete-task"><img src="https://agentmods.dev/badge/skills/makigjuro/cloudstack-ai-plugins/complete-task/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/complete-task"><img src="https://agentmods.dev/badge/skills/makigjuro/cloudstack-ai-plugins/complete-task.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.00052 | $0.02799 |
| Opus 5.5 | $0.00021 | $0.01120 |
| Sonnet 5.5 | $0.00010 | $0.00560 |
| Haiku 4.5 | $0.00005 | $0.00280 |
Grade A, and why
complete-task scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -sf http://localhost:${FRONTEND_PORT} > /dev/null 2>&1 && echo "Frontend: UP" || echo "Frontend: DOWN" How it starts
The opening of the file, as written. The whole thing — 287 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Complete Task
Finalize the current feature branch by running all quality gates and creating a PR. This skill orchestrates multiple verification steps with parallel execution where possible, and dynamically composes review agents based on what changed.
Prerequisites
- You must be on a feature branch (not main)
- All implementation work should be complete
- Working tree should be clean (all changes committed)
Arguments
{issue}-- GitHub issue number (optional). If not provided, extract from branch name.--skip-integration-- Skip integration tests (faster, for WIP checks)--auto-fix-- Automatically fix lint issues before proceeding
Configuration
Read cloudstack.json from the project root at the start of execution. Extract:
SOLUTION=backend.solutionPath(default: find*.slninsrc/)FRONTEND_PATH=frontend.path(default:web)CHARTS_PATH=infrastructure.chartsPath(default:deploy/charts)TERRAFORM_PATH=infrastructure.terraformPath(default:infra/terraform/modules)SERVICES=backend.services[](default: discover fromsrc/*/directories containing.Application/subfolders)
If cloudstack.json does not exist, auto-detect by scanning the project structure.
Scripts
| Tool | Type | Purpose |
|---|---|---|
preflight.sh |
Bash (${CLAUDE_PLUGIN_ROOT}/scripts/) |
Branch check, clean tree, issue extraction |
State Machine
[start] -> pre-flight + detect-changes
|
parallel-build (backend || frontend)
|
pending-migrations (if HAS_BACKEND)
|
parallel-lint+tests (backend || frontend || infra)
|
integration-tests -> browser-verify
|
parallel-agents (reviewer || verifier || doc-checker? || infra-reviewer?)
|
[issues?] -> scoped-fix -> [restart affected tracks]
|
create-pr -> [done]
CRITICAL: Do not skip states. Do not proceed if a gate fails. Maximum 3 fix iterations before stopping.
Process
Phase 0: Pre-flight + Change Detection
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 · 287 lines · 52 tokens per session scan A f9463d0d37a5
complete-task is a skill published in the GitHub repository makigjuro/cloudstack-ai-plugins (1 stars, last pushed 3mo ago), licensed MIT. It adds 52 tokens to every session and 2,799 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
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…
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…
open-pr
Use when wrapping up a development task and getting a PR ready — runs local tests, creates a PR (if one doesn't exist) with a structured description template, conducts a code review via the review skill, and checks CI status with quick fixes. Trigger when the user says they're done with a feature, want to open a PR…
prune-sync-log
Prune stale Whetstone sync decision entries when asked to clean the sync log.
release
Run the Whetstone release workflow when explicitly asked to release this plugin.
sync-from-repos
Compare Whetstone with reference repositories when asked to sync cross-repository improvements.