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
# Testing Rules
## Test Files
- Test files live next to the code they test: `internal/led/engine_test.go`
- Use standard `testing` package — no external test frameworks
- Table-driven tests preferred for multiple cases
## Running Tests
```bash
go test ./... # All tests
go test ./internal/led/... # Single package
go test -run TestFunctionName # Single test
go test -v ./... # Verbose output
go test -race ./... # Race detector
```
## Conventions
- Test function names: `TestMethodName_Scenario` (e.g. `TestEncodeColors_BufferLength`)
- Use `t.Errorf` or `t.Fatalf` — not `panic` or `log.Fatal` in tests
- Test exported behavior, not internal implementation details
- Mock external dependencies (shell commands, hardware), not internal services
The line at the top of this page pins the label git:20260324.7a91f3b, 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.
GET https://markdownregistry.com/api/v1/artifacts/art_njix5lgqevhognql
GET https://markdownregistry.com/api/v1/resolve?ref=autonomous-ai/autonomous-os/.cursor/rules/testing.mdc
GET https://markdownregistry.com/api/v1/blob/b9ac33acce96924373991e834b4ef42216ce6f9f2198cab1a7e0a2c959f8926b
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.
autonomous-ai/autonomous-os · integrations/companions/claude-desktop-buddy/claude-code-buddy/SKILL.md · Push Claude Code activity to the user's device (e.g. a lamp) over the LAN. The plugin POSTs semantic events to a…
autonomous-ai/autonomous-os · integrations/companions/claude-desktop-buddy/skill/SKILL.md · MOVED — canonical skill now lives in the platform skills tree.
autonomous-ai/autonomous-os · skills/agent-management/SKILL.md · Legacy Autonomous Buddy control for explicitly requested Buddy coding sessions. When the user asks a coding or research…
autonomous-ai/autonomous-os · skills/audio/SKILL.md · Low-level speaker and microphone hardware control — adjust volume, play test tones, record raw audio. Do NOT use for…
autonomous-ai/autonomous-os · skills/camera/SKILL.md · Camera control — snapshot, stream, and privacy toggle. Trigger on "what do you see", "look at this", "take a photo"…
davepoon/buildwithclaude · plugins/cc-best/skills/testing/SKILL.md · Testing strategies and methodologies including TDD, E2E testing, and multi-framework support
live-codes/livecodes · .agents/skills/livecodes/testing/SKILL.md · Write and run automated tests with Jest and Testing Library in the browser. Import code from script editor, use watch…
team-commonly/commonly · fleet-skills/testing/SKILL.md · Testing and code quality context for Jest, React Testing Library, ESLint, and test patterns. Use when writing tests or…
