mocking-strategy-roster SKILL.md skillA
mocking-strategy-roster from sebastiendegodez/skraft-plugin is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add sebastiendegodez/skraft-plugin/mocking-strategy-roster@git:20261011.2406fc7Pins git:20261011.2406fc7 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- sebastiendegodez/skraft-plugin
- Path
plugins/skraft-framework/skills/mocking-strategy-roster/SKILL.md- Versions recorded
- 4
- Latest version
- git:20261011.2406fc7, committed Oct 11, 2026
- First version recorded
- Aug 6, 2026
- Size
- 4,137 bytes
- Repository stars
- 12
- License
- GPL-3.0
Use when an agent must mock a downstream HTTP/event dependency for an integration test and needs to know WHICH mocking strategy and stack adapter to use. Resolves the mocking strategy (Microcks by default, overridable to an in-process library) and the stack, then points to the concrete `mocking-<strategy>-<stack>` adapter. Loaded by the mock-integration-worker. No agent hardcodes a mocking approach — it resolves it here.
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
# Mocking Strategy Roster (stack + strategy agnostic)
The single place that resolves **how** a downstream dependency is mocked for an
integration test. No agent and no worker hardcodes "spin up Microcks" or "use
Moq". They resolve the pair `(strategy x stack)` here, then load the matching
adapter.
This mirrors `resolving-stack-commands`: the roster owns the routing table; the
adapters own the concrete wiring.
## Two orthogonal axes
- **Strategy** — WHICH mocking approach. Exclusive choice:
- `microcks` (DEFAULT, overridable) — mock the downstream from its
OpenAPI/examples contract via a container.
- `inprocess` — an in-process test double injected into the test host DI.
- **Stack** — WHICH toolchain, detected via `resolving-stack-commands`.
The two axes never mix inside one file. Each `(strategy x stack)` pair is one
thin adapter.
## Resolving the strategy (override cascade)
Read the strategy by tool-call, never from recall. Precedence, first writer wins:
1. **Explicit prompt** — the run prompt names a strategy/library
(e.g. "mock with Moq", "mock with respx", "use Microcks here"). Highest priority.
2. **Repo instruction file** — read
…Read the whole file at its exact version.
How to install
mdr add sebastiendegodez/skraft-plugin/mocking-strategy-roster@sha256:e07c4f6a072ebb8fThe line at the top of this page pins the label git:20261011.2406fc7, 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_rwp4y6pyojwzisyc)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Aug 6, 2026 and Oct 11, 2026, about one every 22 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261011.2406fc7 latest | 2026-10-11 | 2406fc7 | 4,137 B | A | view · diff |
| git:20261009.700b6e2 | 2026-10-09 | 700b6e2 | 4,370 B | A | view · diff |
| git:20261008.193dd3e | 2026-10-08 | 193dd3e | 4,100 B | A | view · diff |
| git:20260806.b506b65 | 2026-08-06 | b506b65 | 3,790 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 (4137 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
sebastiendegodez/skraft-plugin · 12 stars · license GPL-3.0 · pushed 2026-10-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_rwp4y6pyojwzisyc GET https://markdownregistry.com/api/v1/resolve?ref=sebastiendegodez/skraft-plugin/mocking-strategy-roster GET https://markdownregistry.com/api/v1/blob/e07c4f6a072ebb8f9576c7d09755bd8d32fcc9da0b7819a7a6a69dfdec7159b7
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.