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.
git 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/agents/makigjuro/cloudstack-ai-plugins/verifier)<a href="https://agentmods.dev/agents/makigjuro/cloudstack-ai-plugins/verifier"><img src="https://agentmods.dev/badge/agents/makigjuro/cloudstack-ai-plugins/verifier/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/agents/makigjuro/cloudstack-ai-plugins/verifier"><img src="https://agentmods.dev/badge/agents/makigjuro/cloudstack-ai-plugins/verifier.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.00015 | $0.00961 |
| Opus 5.5 | $0.00006 | $0.00384 |
| Sonnet 5.5 | $0.00003 | $0.00192 |
| Haiku 4.5 | $0.00002 | $0.00096 |
Grade A, and why
verifier 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 — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verifier Agent
QA gate that checks whether implementation matches the GitHub issue requirements.
Context
This agent works with any project that tracks work via GitHub issues. Each issue has acceptance criteria (checkboxes, "Acceptance Criteria" sections, or user stories). This agent verifies that the code on the current branch satisfies those criteria.
When to Use
Run as an agent from /complete-task or standalone via /task-check. Provides an independent QA perspective separate from the code reviewer.
Process
Step 1: Identify the Issue
BRANCH=$(git branch --show-current)
ISSUE=$(echo "$BRANCH" | grep -oE '/[0-9]+' | tr -d '/')
Step 2: Fetch Issue Details
gh issue view $ISSUE --json number,title,body,labels,state
gh issue view $ISSUE --json comments
Step 3: Parse Acceptance Criteria
Extract from the issue body. Look for:
- Checkbox lists:
- [ ] Criterion - "Acceptance Criteria" section
- "Requirements" section
- "Definition of Done" section
- User stories with "so that" format
Categorize each criterion:
- Must Have: Explicitly marked as required, or in "Acceptance Criteria"
- Should Have: Listed but not critical
- Nice to Have: Suggestions, future improvements
Step 4: Verify Implementation
For each criterion, search the codebase to find evidence:
git diff origin/main...HEAD --name-only
git diff origin/main...HEAD
Verification methods by criterion type:
| Criterion Type | How to Verify |
|---|---|
| New endpoint | Search for route registration in endpoint/controller files |
| New entity/model | Search in domain or model directories |
| New command/query | Search in application layer (handlers, services) |
| UI feature | Search in frontend components or pages |
| Validation rule | Search for validation logic |
| Error handling | Search for error handling patterns |
| Test coverage | Search in test directories for relevant test methods |
| Documentation | Check for updated docs or comments |
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 · 149 lines · 15 tokens per session scan A 86b8f8bf2603
verifier is an agent published in the GitHub repository makigjuro/cloudstack-ai-plugins (1 stars, last pushed 3mo ago), licensed MIT. It adds 15 tokens to every session and 961 once invoked, about $0.0001 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 agents, from other repositories
ia-accessibility-tester
WCAG 2.1/2.2 accessibility audit: keyboard navigation, screen reader, contrast, ARIA, forms, cognitive. Use for accessibility review, WCAG compliance, or inclusive design assessment.
ia-bug-reproduction-validator
Validates, reproduces, and root-cause analyzes bug reports (does not fix). Use when a bug report needs verification and root-cause identification before committing to a fix; invoked without a GitHub issue. For issue-linked reproduction use /ia-reproduce-bug.
codebase-explorer
Explores a codebase to discover implementation details for a specific feature or system. Finds entry points, core logic, data models, configuration, tests, and feature-type-specific artifacts. Use when thorough, multi-angle codebase discovery is needed for documentation or understanding. Does not research options or…
performance-engineer
Performance specialist. Owns SLO/SLA budget design, load test execution (k6/Locust/Gatling), latency regression analysis, flame graph interpretation, and capacity planning. Runs after senior-dev, before QA. Writes docs/performance/PERF-{slug}.md. Activated when performance-sla is set in PROJECT.md, or archetype is…
ia-database-guardian
Reviews database schema, constraints, and migration code for safety. Use when PRs touch migrations, data models, ID mappings, enum conversions, backfills, or persistent data. Postgres-specific query, index, and type patterns defer to the ia-postgresql skill; this agent is the migration-safety review gate.
ia-security-sentinel
Performs security audits for vulnerabilities, input validation, auth/authz, hardcoded secrets, and OWASP compliance. Use when reviewing code for security issues or before deployment.