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.
npx agentmods add agents/jvgomg/podkit/device-testinggit clone --depth 1 https://github.com/jvgomg/podkitWhat 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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00000 | $0.06352 |
| Opus 5 | $0.00000 | $0.03176 |
| Sonnet 5 | $0.00000 | $0.01270 |
| Haiku 4.5 | $0.00000 | $0.00635 |
Grade A, and why
device-testing scanned grade A with 0 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 375 lines — stays where its author put it; the contents beside it link to each section on GitHub.
device-testing: Device Test Harness
Canonical reference for agents writing tests for device identification, doctor checks, and readiness pipelines. Read this before touching @podkit/device-testing, any file named *.e2e.test.ts, or tasks in milestone m-19.
Also see test-packages/device-testing/README.md for package-level API details, ADR-016 for the full architecture decision, and ADR-017 for the fixture registry design.
Quick start (developer)
First time:
bun install
bun run harness:setup
bun run test:vm
Subsequent runs:
bun run harness:start # if VM is stopped
bun run test:vm
bun run harness:stop # when done
bun run harness:status prints a single-screen health check of the VM, binaries, systemd unit, and kernel modules. bun run harness:install re-runs the turbo builds and re-transfers everything (cheap; sha256-skips no-op transfers). All harness:* scripts dispatch into test-packages/device-testing/scripts/harness.ts.
bun run test:vm is now self-orchestrating. It turbo-depends on two new tasks:
@podkit/device-testing#vm:install— cached fresh-binary install. Invalidates on changes to podkit/daemon/gpod-tool source globs ORscripts/harness.ts/runners/lima-test-vm-*.ts. Replays as a cache hit (~300ms) when nothing changed.@podkit/device-testing#vm:doctor— preflight drift check. Hashespodkit-device-harness.yaml+apply-state.shand compares against the baseline hash sealed inside the VM atharness:setup. No silent recovery — drift exits 1 with the exactharness:destroy && harness:setupremediation command.
You almost never need harness:install directly anymore; test:vm covers the binary-freshness contract. Force-refresh via bunx turbo run @podkit/device-testing#vm:install if needed (e.g. after a manual rebuild outside the test loop). Drift-check only: bunx turbo run @podkit/device-testing#vm:doctor.
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.
- today First seen · 375 lines · 0 tokens per session scan A e8e4825605ed
device-testing is an agent published in the GitHub repository jvgomg/podkit (39 stars, last pushed 9d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 6,352 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-01.
Other agents, from other repositories
AGENTS
Use uv for every Python command in this repo. Do not use bare python, pip, poetry, or conda.
CONTEXT
Agent "CONTEXT" from TheRealSavi/iOpenPod, covering iopenpod and language.
accessibility-reviewer
Reviews Android Compose / iOS SwiftUI changes for screen-reader and reduce-motion regressions. Use proactively after any UI change, before opening a PR that touches ui/ or iosApp/ Views, or when asked to check TalkBack/VoiceOver accessibility. A core user base is blind and visually impaired — accessibility is treated…
domain
How the engineering skills should consume this repo's domain documentation when exploring the codebase.
triage-labels
The skills speak in terms of five canonical triage roles. This file maps those roles to the actual label strings used in this repo's issue tracker.
issue-tracker
Issues and PRDs for this repo live as GitHub issues. Use the gh CLI for all operations.