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 skills/eladariel/pseudo-code-prompting-plugin/requirement-validatornpx skills add EladAriel/pseudo-code-prompting-plugin --skill requirement-validatorgit clone --depth 1 https://github.com/EladAriel/pseudo-code-prompting-pluginWrote 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/eladariel/pseudo-code-prompting-plugin/requirement-validator)<a href="https://agentmods.dev/skills/eladariel/pseudo-code-prompting-plugin/requirement-validator"><img src="https://agentmods.dev/badge/skills/eladariel/pseudo-code-prompting-plugin/requirement-validator.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.02266 |
| Opus 5 | $0.00000 | $0.01133 |
| Sonnet 5 | $0.00000 | $0.00453 |
| Haiku 4.5 | $0.00000 | $0.00227 |
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 4d 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 — 386 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Requirement Validator Skill
Validates pseudo-code specifications across 6 critical dimensions with customizable checks per tech stack and severity levels.
What This Skill Does
Validates pseudo-code specifications to catch missing details before implementation:
VALIDATION REPORT
✓ PASSED CHECKS
✓ Error codes defined
✓ Security requirements specified
✓ Timeouts included
✗ CRITICAL ISSUES (Must Fix)
- No rate limiting on public endpoint
⚠ HIGH WARNINGS (Should Fix)
- Token refresh concurrency not handled
📋 MEDIUM (Nice to Have)
- Consider adding request tracing
Key features:
- 6 dimensions: Security, completeness, error handling, data handling, performance, edge cases
- Severity levels: CRITICAL (must fix), HIGH (should fix), MEDIUM (nice to have)
- Tech-stack aware: Validation rules customized for detected tech stack
- Actionable: Each issue includes explanation and suggested fix
When to Use
- Before implementing—catch issues early
- Reviewing specifications from team members
- Quality gate for specification release
- Validating pseudo-code across all dimensions
6 Validation Dimensions
1. Security
Checks for authentication, authorization, data protection, and attack prevention.
Questions:
- Is authentication specified? (type, providers, tokens)
- Is authorization (access control) defined?
- Input validation mentioned?
- Rate limiting specified?
- Sensitive data encryption required?
- Secure communication (HTTPS)?
- Secure cookie settings?
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 algorithms
- Overly broad permissions
- Missing input sanitization
- No CSRF protection
Customization by tech stack:
Node.js/Next.js:
- Check for CORS configuration
- Check for helmet/security middleware
- JWT secret management
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 386 lines · 0 tokens per session scan A d8798cd000e1
requirement-validator is a skill published in the GitHub repository EladAriel/pseudo-code-prompting-plugin (2 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,266 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…