test-reasoning skillA
test-reasoning is agent-read markdown (skill) from tailcallhq/forgecode: Validate that reasoning parameters are correctly serialized and sent to provider APIs. Use when the user asks to test reasoning serialization, run reasoning tests, verify reasoning config fields, or check that ReasoningConfig maps correctly to provider-specific JSON (OpenRouter, Anthropic, GitHub Copilot, Codex)..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified before it reaches your agent: the main file against the SHA-256 recorded here, the others against the git hashes of its source commit. The deterministic audit below grades the latest version, and the same checks always give the same file the same grade.
What the file says
# Test Reasoning Serialization Validates that `ReasoningConfig` fields are correctly serialized into provider-specific JSON for OpenRouter, Anthropic, GitHub Copilot, and Codex. ## Quick Start Run all tests with the bundled script: ```bash ./scripts/test-reasoning.sh ``` The script builds forge in debug mode, runs each provider/model combination, captures the outgoing HTTP request body via `FORGE_DEBUG_REQUESTS`, and asserts the correct JSON fields. ## Running a Single Test Manually ```bash FORGE_DEBUG_REQUESTS="forge.request.json" \ FORGE_SESSION__PROVIDER_ID=<provider_id> \ FORGE_SESSION__MODEL_ID=<model_id> \ FORGE_REASONING__EFFORT=<effort> \ target/debug/forge -p "Hello!" ``` Then inspect `.forge/forge.request.json` for the expected fields. ## Test Coverage | Provider | Model | Config fields | Expected JSON field | | ---------------- | ---------------------------- | ------------------------------------------------- | --------------------------------- | …
Read the whole file at its exact version.
How to install
mdr add tailcallhq/forgecode/test-reasoning@git:20260402.1e409famdr add tailcallhq/forgecode/test-reasoning@sha256:4f98815ab6654a4aPin to a label to follow the author's releases, or to a sha256 for exact bytes. Either way the resolved hash is written to mdr.lock, and mdr install fetches those bytes again and checks them, so it installs them exactly or fails.
[](https://markdownregistry.com/a/art_ssdbimkvqzckfutr)
2 badge views in 30 days
Versions
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 (4148 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
tailcallhq/forgecode · 7,637 stars · license Apache-2.0 · pushed 2026-09-26 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ssdbimkvqzckfutr GET https://markdownregistry.com/api/v1/resolve?ref=tailcallhq/forgecode/test-reasoning GET https://markdownregistry.com/api/v1/blob/4f98815ab6654a4abb81c1e44ec337cf4ec7e8bd487748eba425027cd98fac80
Your agent 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.