Runtime Validation SKILL.md skillA
Runtime Validation from nxtg-ai/forge-plugin is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add nxtg-ai/forge-plugin/Runtime Validation@git:20260714.4fd0952Pins git:20260714.4fd0952 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- nxtg-ai/forge-plugin
- Path
plugins/nxtg-forge/skills/runtime-validation/SKILL.md- Versions recorded
- 3
- Latest version
- git:20260714.4fd0952, committed Jul 14, 2026
- First version recorded
- Feb 7, 2026
- Size
- 9,426 bytes
- Repository stars
- 6
- License
- MIT
Catch the bugs a green test suite misses by observing REAL runtime behavior — tail application logs during test/server runs, validate API responses against their schema contracts, and assert data-integrity invariants (density ≤ 1.0, %≤100, referential integrity). Use when unit tests pass 100% but the running app still errors, when a Pydantic/Zod/serde validation error or schema drift shows up only at runtime, when reviewing whether a test suite actually exercises the running system, or when…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Runtime Validation Unit tests assert on **mocked inputs and isolated functions**. Runtime validation asserts on the **actual running system** — logs, real HTTP responses, and cross-layer data. A suite can be 100% green while the product is broken, because the mocks never hit the code path that fails. This skill is the discipline that closes that gap. ## Why this exists (real forge incident, not hypothetical) `hooks/scripts/smoke-test-reminder.sh` in this plugin carries the origin verbatim: > On 2026-02-06, an agent spent an entire day writing **2326 mock unit tests** while the > actual product was broken. A duplicate placeholder route intercepted all real requests. > Nobody caught it because **nobody started the actual server**. That is the whole thesis: *a passing mock suite is not evidence the running system works.* The three techniques below are how you get that evidence. ## The three techniques | Technique | What it observes | Catches | |-----------|------------------|---------| | **Log monitoring** | app logs during a test/server run | validation errors, stack traces, swallowed exceptions the assertion never saw | …
Read the whole file at its exact version.
How to install
mdr add nxtg-ai/forge-plugin/Runtime Validation@sha256:6345aae690ee917bThe line at the top of this page pins the label git:20260714.4fd0952, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_ojm4hbbvulzlotqc)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Feb 7, 2026 and Jul 14, 2026, about one every 78 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260714.4fd0952 latest | 2026-07-14 | 4fd0952 | 9,426 B | A | view · diff |
| git:20260714.061716b | 2026-07-14 | 061716b | 10,658 B | A | view · diff |
| git:20260207.88c1f6e | 2026-02-07 | 88c1f6e | 10,631 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (9426 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
nxtg-ai/forge-plugin · 6 stars · license MIT · pushed 2026-10-15 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ojm4hbbvulzlotqc GET https://markdownregistry.com/api/v1/resolve?ref=nxtg-ai/forge-plugin/Runtime Validation GET https://markdownregistry.com/api/v1/blob/6345aae690ee917bb705ecdc78761022353fcf7b2dc92a11265695706e62aa2f
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.