test-performance SKILL.md skillA
test-performance from seedcord/seedcord is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add seedcord/seedcord/test-performance@git:20261015.dc45e41Pins git:20261015.dc45e41 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- seedcord/seedcord
- Path
.agents/skills/test-performance/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261015.dc45e41, committed Oct 15, 2026
- Size
- 6,916 bytes
- Repository stars
- 26
- License
- Apache-2.0
Use this when writing or changing a test, a test helper, or a vitest config in seedcord, and when a test is slow or fails only in the full suite. Covers the shared-worker setup every package runs on, cleaning up state with Disposable handles, keeping expensive setup rare, and checking a change for leaks.
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 performance Every package's tests run in shared workers, inside a workspace run that already uses most of the machine. A test that leaks state breaks a file that runs after it. A test that boots, builds, or typechecks more than it needs keeps every core busy for longer. Both show up in `pnpm prePush` as flakes and spinning fans. ## How the workers run `@seedcord/vitest-config` sets these for every package. Leave them alone in a package's own config. apps/docs is the one exception, with `isolate: true` until its tests stop mocking its own modules. - `isolate: false`. A worker process runs many test files in turn. - A setup file calls `vi.resetModules()` before each file. Each file gets fresh instances of the modules vitest runs, so a static cache or a module-level singleton stays inside its file. - `maxWorkers: '25%'` when `CI` is unset, with `concurrency: "2"` in `turbo.json`. Together they keep about half of a dev machine's cores free. CI runners keep vitest's default. The reset covers only modules vitest runs itself. Everything below survives into the next file in the same worker: - `globalThis` slots, like the ones a built bot or baked ids use …
Read the whole file at its exact version.
How to install
mdr add seedcord/seedcord/test-performance@sha256:8c537388db1126c5The line at the top of this page pins the label git:20261015.dc45e41, 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_65ggjzvjy2rp7t7t)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Oct 15, 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 (6916 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
seedcord/seedcord · 26 stars · license Apache-2.0 · pushed 2026-10-22 · branch next
API
GET https://markdownregistry.com/api/v1/artifacts/art_65ggjzvjy2rp7t7t GET https://markdownregistry.com/api/v1/resolve?ref=seedcord/seedcord/test-performance GET https://markdownregistry.com/api/v1/blob/8c537388db1126c5a804372d0850056561815aec37fc8d83d2dddc92f47201ad
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.