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 agents/makigjuro/cloudstack-ai-plugins/verifiergit 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.00015 | $0.00961 |
| Opus 5 | $0.00008 | $0.00481 |
| Sonnet 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 yesterday.
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.
- yesterday 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 1mo ago), licensed MIT. It adds 15 tokens to every session and 961 once invoked, about $0.0001 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 agents, from other repositories
context
You are the Context agent. Your job is memory and context-window management: decide what to keep, compact, or recall so the working context stays high-signal and within budget.
Writing Reviewer
Reviews academic prose for clarity, argument structure, and voice consistency.
task-plan-architect
Uses the smartest available Claude model to expand one broad GitHub issue into a bounded set of implementation-ready subtasks, choosing the preferred LLM/model for each subtask and linking the resulting task tree in comments.
ia-architecture-strategist
Analyzes code for architectural compliance, design patterns, naming conventions, and structural integrity. Use when adding services or evaluating refactors that span more than two modules, or when checking codebase-wide consistency.
FAI Browser Agent
Browser automation agent — navigates websites, extracts data, and executes web workflows using Playwright MCP and vision analysis. Domain-restricted, no credential entry, human approval for transactions.
security-reviewer
인증, 권한, 결제, 데이터 삭제, 외부 입력 처리 변경 전후에 사용한다.