test-evidence-review SKILL.md skillA
test-evidence-review from furkantokkan/agent-foundry is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add furkantokkan/agent-foundry/test-evidence-review@git:20260907.501dbcaPins git:20260907.501dbca in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- furkantokkan/agent-foundry
- Path
plugins/agent-foundry/skills/test-evidence-review/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260907.501dbca, committed Sep 7, 2026
- Size
- 1,877 bytes
- Repository stars
- 11
- License
- MIT
Quality review of test files and manual evidence documents. Goes beyond existence checks — evaluates assertion coverage, edge case handling, naming conventions, and evidence completeness. Produces ADEQUATE/INCOMPLETE/MISSING verdict per story. Run before QA sign-off or on demand.
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
# Test Evidence Review Codex port of Claude Code Game Studios /test-evidence-review. Use this skill when the task matches the workflow described below. Keep the Codex version lightweight: load `references/claude-skill.md` only when the original detailed Claude workflow is needed. ## Codex Workflow 1. Read repository-local instructions first: `AGENTS.md`, `CLAUDE.md`, the nearest path-scoped instructions (`Assets/CLAUDE.md` for Unity when present), and any referenced project docs. 2. Use this workflow's intent, but follow Codex tool and collaboration rules. 3. Apply SOLID, Clean Code, clear English naming, dependency boundaries, and focused tests for new or changed expected behavior. 4. When a Claude workflow mentions a custom agent, treat it as a role reference. Do the work locally unless the user explicitly asks for sub-agents or parallel agent work. 5. For implementation tasks, make the change directly when the request is clear; ask only when a decision cannot be safely inferred from local context. 6. Verify with the repository's available checks and summarize changed files, tests run, and residual risk. ## Original Workflow Summary …
Read the whole file at its exact version.
How to install
mdr add furkantokkan/agent-foundry/test-evidence-review@sha256:482f4af6a8b6c375The line at the top of this page pins the label git:20260907.501dbca, 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_lqnrff5igizx3vfe)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Sep 7, 2026.
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 (1877 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
furkantokkan/agent-foundry · 11 stars · license MIT · pushed 2026-10-08 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_lqnrff5igizx3vfe GET https://markdownregistry.com/api/v1/resolve?ref=furkantokkan/agent-foundry/test-evidence-review GET https://markdownregistry.com/api/v1/blob/482f4af6a8b6c3752c879da5c16438e2bfb6f3fe24c0562fcb41e105ee5aca36
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.
More from furkantokkan/agent-foundry
Every file in furkantokkan/agent-foundry