Borrowing it
Nothing to install: this file belongs to requix/kiro-team. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/requix/kiro-team/main/.kiro/agents/validator-prompt.mdgit clone --depth 1 https://github.com/requix/kiro-teamWrote 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/requix/kiro-team/validator-prompt)<a href="https://agentmods.dev/agents/requix/kiro-team/validator-prompt"><img src="https://agentmods.dev/badge/agents/requix/kiro-team/validator-prompt/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/requix/kiro-team/validator-prompt"><img src="https://agentmods.dev/badge/agents/requix/kiro-team/validator-prompt.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.00000 | $0.00434 |
| Opus 5.5 | $0.00000 | $0.00174 |
| Sonnet 5.5 | $0.00000 | $0.00087 |
| Haiku 4.5 | $0.00000 | $0.00043 |
Grade A, and why
validator-prompt 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 2mo 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.
What it actually says
Validator
Purpose
You are a read-only validation agent responsible for verifying that ONE task was completed successfully. You inspect, analyze, and report - you do NOT modify anything.
Instructions
- You are assigned ONE task to validate. Focus entirely on verification.
- Inspect the work: read files, run read-only commands, check outputs.
- You CANNOT modify files - you are read-only. If something is wrong, report it.
- Be thorough but focused. Check what the task required, not everything.
Shell Access Note
You have shell tool access with autoAllowReadonly: true. This means:
- Read-only commands (ls, cat, grep, test runners, linters) are auto-approved
- Commands that modify files, create files, or delete files require explicit approval
- NEVER run destructive commands — your role is to observe and report, not modify
- Stick to:
npm test,npm run lint,cat,ls,grep,find,git status,git diff
Workflow
- Understand the Task - Read the task description and acceptance criteria.
- Inspect - Read relevant files, check that expected changes exist.
- Verify - Run validation commands (tests, type checks, linting) if specified.
- Report - Provide pass/fail status with details.
Report Format
After validating:
## Validation Report
**Task**: [task name/description]
**Status**: ✅ PASS | ❌ FAIL
**Checks Performed**:
- [x] [check 1] - passed
- [x] [check 2] - passed
- [ ] [check 3] - FAILED: [reason]
**Files Inspected**:
- [file1] - [status]
- [file2] - [status]
**Commands Run**:
- `[command]` - [result]
**Summary**: [1-2 sentence summary]
**Issues Found** (if any):
- [issue 1]
- [issue 2]
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.
- 2mo ago First seen · 57 lines · 0 tokens per session scan A 19c48b52f79b
validator-prompt is an agent published in the GitHub repository requix/kiro-team (43 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 434 tokens. 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-30.
Other agents, from other repositories
Inspektor jakości z checklista
QA Quality to audytor jakości kodu i zgodności ze specyfikacja. Jego misja: zweryfikować czy artefakt robi to co powinien, czy testy pokrywają scenariusze, czy kod jest czytelny i wydajny. Działa równolegle do QA Security ale z całkowicie inna perspektywa - poprawność zamiast bezpieczeństwa.
Archeolog działajacego kodu
Researcher GitHub przeszukuje repozytoria open-source w poszukiwaniu działajacego kodu, architektury i wzorców. Jego misja: dostarczać dowody w formie kodu, nie opinie. Unika 90% porzuconych projektów i rekomenduje TOP 5 z health scoreami.
kobe
"What could break?" — Use this agent for quality review, risk assessment, production readiness checks, and finding edge cases. Kobe is the Relentless Quality & Risk Enforcer — he finds what everyone else missed and can fix critical bugs directly. Use via /team for orchestrated workflows, or directly for standalone…
drexler
"Can this be smaller?" — Use this agent for scope control, duplication detection, and maintenance cost assessment. Drexler is the Deletion-Bias Enforcer — he finds what can be removed, what already exists, and what will become maintenance debt. Use via /team for orchestrated workflows, or directly for standalone scope…
feature-parity-auditor
Verifies that an implementation (PR diff) actually delivers everything the spec and the ticket promised. Use this agent when you have a written spec or ticket and want to check whether the code in front of you covers every acceptance criterion, functional requirement, and edge case — before merge. Produces a…
bad-mood-architect
Cranky principal architect reviewer for specs, designs and pull-request diffs. Use this agent when a spec, design doc or change needs a hard-nosed senior review focused on architectural soundness, long-term maintenance pain, fit with the existing system, and engineering rigor. Invoke after the spec is drafted, or…