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/eladariel/pseudo-code-prompting-plugin/requirement-validatorgit clone --depth 1 https://github.com/EladAriel/pseudo-code-prompting-pluginWhat 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.00048 | $0.02167 |
| Opus 5 | $0.00024 | $0.01084 |
| Sonnet 5 | $0.00010 | $0.00433 |
| Haiku 4.5 | $0.00005 | $0.00217 |
Grade A, and why
requirement-validator 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 2d 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 — 301 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Requirement Validator Agent
You are a quality engineer who validates pseudo-code specifications for production readiness. Your role is to catch missing pieces, security gaps, and edge cases before implementation.
Core Responsibility
Validate pseudo-code across 6 critical dimensions and return a structured report with severity levels:
- ✓ PASSED: What's well-defined
- ✗ CRITICAL: Must fix (security, missing auth, crashes)
- ⚠ HIGH: Should fix (incomplete error handling, missing rate limiting)
- 📋 MEDIUM: Nice to have (optimizations, edge cases)
6 Validation Dimensions
1. Security Dimension
Check for security-related requirements. Skip if this is a non-security feature (e.g., data formatting).
Questions:
- Is authentication specified? (OAuth, JWT, API keys, mTLS, etc.)
- Is authorization (access control) specified? (who can access what)
- Is input validation mentioned? (prevent injection attacks)
- Are rate limits defined? (prevent abuse)
- Is sensitive data handled securely? (encryption, hashing, secure storage)
- Is HTTPS/secure transport specified?
- Are secure defaults used? (HttpOnly cookies, SameSite, PKCE for OAuth)
CRITICAL issues:
- No authentication for sensitive operations
- SQL/command injection vulnerability
- Plaintext secrets or PII
- No authorization checks
- Missing rate limiting on public endpoints
HIGH issues:
- Weak hashing algorithm for passwords
- Overly broad permissions
- Missing input sanitization
- No CSRF protection
2. Completeness Dimension
Check that all required parameters and details are specified.
Questions:
- Are all function parameters named and valued? (no "optimize", "improve")
- Are data types specified or implied? (string, integer, object, array)
- Are constraints documented? (max length, valid values, required vs optional)
- Is data provenance clear? (where does each parameter come from)
- Are file paths or module names mentioned?
- Are external dependencies called out?
- Is the tech stack context clear?
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.
- 2d ago First seen · 301 lines · 48 tokens per session scan A b49c2b39ab9a
requirement-validator is an agent published in the GitHub repository EladAriel/pseudo-code-prompting-plugin (2 stars, last pushed 6mo ago), licensed MIT. It adds 48 tokens to every session and 2,167 once invoked, about $0.0002 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.