testing

Detailed testing guidance for agents working in this repository. See AGENTS.md for project overview.

Agent

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add agents/jvgomg/podkit/testing
Clone the repo
git clone --depth 1 https://github.com/jvgomg/podkit
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 17,282 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 2 findings. Scan, not verified.
Origin unknown No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.17282
Opus 5 $0.00000 $0.08641
Sonnet 5 $0.00000 $0.03456
Haiku 4.5 $0.00000 $0.01728

Measured today against content hash 912bdcb43227, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade B, and why

testing scanned grade B with 2 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured today.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Asks for rootmediumPrivilege escalation

A mod that escalates privileges can change anything on the machine, not only the project.

o.error('Run: sudo podkit mount');

Runs shell commandslowCapability

Expected in a hook, worth knowing in a rule or an instructions file.

**Hard rule: never spawn the podkit CLI as a subprocess from a unit or integration test.** Subprocess invocation lives only in `test-packages/e2e-tests/`. The rule is enforced by an oxlint check (`no-restricted-imports`
agents/testing.md · 1,192 lines

How it starts

The opening of the file, as written. The whole thing — 1,192 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Testing

Detailed testing guidance for agents working in this repository. See AGENTS.md for project overview.

Also see docs/developers/testing.md for full testing strategy and conventions.

Quick Reference

Tests are classified by Depth (encoded in the filename suffix); E2E tests are additionally classified by Surface (encoded in the directory). Each Depth has a turbo task, a bunfig.toml pathIgnorePatterns gate, and a default position in the dev loop. See the canonical test taxonomy for the full Depth × Surface model and Test depths and pathIgnorePatterns below for the wiring.

Suffix Depth Runs by default? Requirements
*.test.ts Unit — fast, in-process, no external deps. Yes, in bun test / test:unit. None.
*.integration.test.ts Integration — real system deps (ffmpeg, gpod-tool, libgpod-node native bindings, fixtures). No — gated. Run via test:integration. Whatever the test declares at module load via requireFFmpeg() &c.
*.perf.test.ts Performance benchmark — timing-sensitive, generates synthetic load. (A modifier on Unit/Integration, not a depth of its own.) No — gated. Run via test:perf. Same as integration.
*.e2e.test.ts (in e2e-* packages) End-to-end — spawns the built CLI/image as a black box. Surface is the directory (default surface at package root; non-default surfaces in subdirs). No — separate task. Run via test:e2e / test:e2e:docker / test:vm. Built CLI/image + surface-specific deps.

Hard rule: integration / perf / e2e tests that depend on a tool or fixture call requireX() / ensureFixturesExist() at module load. Missing deps fail the suite loudly, not silently. See Module-load preflight and Test skip anti-patterns.

Per-OS Test Tagging

Read the full file on GitHub · 1,192 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. today First seen · 1,192 lines · 0 tokens per session scan B 912bdcb43227

Subscribe to this mod's changes

testing is an agent published in the GitHub repository jvgomg/podkit (39 stars, last pushed 8d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 17,282 tokens. A static security scan graded it B with 2 findings (asks for root, runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-01.