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/razaib-khan/forgeweave/validation-enginenpx skills add Razaib-khan/ForgeWeave --skill validation-enginegit clone --depth 1 https://github.com/Razaib-khan/ForgeWeaveWrote 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/razaib-khan/forgeweave/validation-engine)<a href="https://agentmods.dev/skills/razaib-khan/forgeweave/validation-engine"><img src="https://agentmods.dev/badge/skills/razaib-khan/forgeweave/validation-engine.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.00020 | $0.00582 |
| Opus 5 | $0.00010 | $0.00291 |
| Sonnet 5 | $0.00004 | $0.00116 |
| Haiku 4.5 | $0.00002 | $0.00058 |
Grade A, and why
Validation Engine 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 3d 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Validation Engine
Purpose
Systematically inspect outputs from any skill or agent for correctness, consistency, completeness, and compliance with project rules defined in AGENTS.md. Acts as a quality gate before outputs are presented to the user or used by downstream skills.
When to Use
- After any skill produces output that needs quality assurance
- Before presenting research results to the user
- When cross-checking claims across multiple sources
- After code generation, before presenting the code
When Not to Use
- The output is trivial and doesn't need validation
- The user is iterating quickly and doesn't want validation overhead
- The output is an intermediate step that will be further processed
Inputs
| Input | Type | Required | Description |
|---|---|---|---|
output |
string | Yes | The content to validate |
type |
enum | Yes | research, code, documentation, plan |
rules |
array | No | Specific rules to enforce (defaults from AGENTS.md) |
Expected Outputs
| Output | Description |
|---|---|
| Validation report | Pass/fail per rule, with details |
| Issues found | List of problems with severity and location |
| Suggestions | How to fix each issue |
Exact Workflow Steps
- Load validation rules from AGENTS.md and the specific skill's requirements
- For research: check every claim has a source URL, flag contradictions, check no blog sources
- For code: check syntax, check against project conventions, verify tests pass
- For documentation: check completeness, accuracy, clarity
- For plans: check steps are ordered, dependencies identified, risks documented
- Compile validation report with pass/fail per rule
Required Checks
- All required fields are present in the output
- No contradictions across the output
- Output follows applicable rules from AGENTS.md
- All claims are traceable to sources
Failure Modes
| Failure Condition | Response |
|---|---|
| Validation rules are ambiguous | Ask for clarification |
| Output fails critical rules | Reject and report specific failures |
| Output fails minor rules | Accept with warnings |
What ships with it
2 files 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.
- 3d ago First seen · 83 lines · 20 tokens per session scan A b0adc324d53d
Validation Engine is a skill published in the GitHub repository Razaib-khan/ForgeWeave (1 stars, last pushed 2mo ago), licensed MIT. It adds 20 tokens to every session and 582 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 skills, from other repositories
plugin-review
Review plugin quality with tiered checks and dependency scoping. Use for PR and pre-release audits.
Release Readiness Reviewer
Reviews a release candidate and produces a go/no-go readiness decision.
code-review
Systematic code review for bugs, security, style, and performance.
aap-lint
Skill "aap-lint" from automateyournetwork/netclaw, covering ansible lint operations, mcp server, available tools (9), key concepts and workflow: pre-deployment playbook validation.
fin-review-loop
经济金融论文的对抗性review循环。对草稿进行多轮严格评审，检查实证严谨性、方法正确性、理论贡献和写作质量，给出可操作的修改建议。（AI review 不能替代同行评审，草稿必须经研究者核实后投稿。）.
plugin-quality
审查和改进 Zhin.js 插件质量（Plugin Runtime）。Use when asked to review plugin code, audit structure, or improve before publishing. 检查 definePlugin、约定目录、发送链与安全。.