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/therealsavi/iopenpod/domaingit clone --depth 1 https://github.com/TheRealSavi/iOpenPodWhat 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.00412 |
| Opus 5 | $0.00000 | $0.00206 |
| Sonnet 5 | $0.00000 | $0.00082 |
| Haiku 4.5 | $0.00000 | $0.00041 |
Grade A, and why
domain 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 2d ago.
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.
This is a copy
75% identical to domain — 48 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Domain Docs
How the engineering skills should consume this repo's domain documentation when exploring the codebase.
Before exploring, read these
CONTEXT.mdat the repo root, orCONTEXT-MAP.mdat the repo root if it exists - it points at oneCONTEXT.mdper context. Read each one relevant to the topic.docs/adr/- read ADRs that touch the area you're about to work in. In multi-context repos, also checksrc/<context>/docs/adr/for context-scoped decisions.
If any of these files don't exist, proceed silently. Don't flag their absence; don't suggest creating them upfront. The producer skill (/grill-with-docs) creates them lazily when terms or decisions actually get resolved.
File structure
Single-context repo:
/
|-- CONTEXT.md
|-- docs/adr/
| |-- 0001-event-sourced-orders.md
| `-- 0002-postgres-for-write-model.md
`-- src/
Multi-context repo, indicated by CONTEXT-MAP.md at the root:
/
|-- CONTEXT-MAP.md
|-- docs/adr/
`-- src/
|-- ordering/
| |-- CONTEXT.md
| `-- docs/adr/
`-- billing/
|-- CONTEXT.md
`-- docs/adr/
Use the glossary's vocabulary
When your output names a domain concept, use the term as defined in CONTEXT.md. Don't drift to synonyms the glossary explicitly avoids.
If the concept you need isn't in the glossary yet, that's a signal: either you're inventing language the project doesn't use, or there's a real gap to note for /grill-with-docs.
Flag ADR conflicts
If your output contradicts an existing ADR, surface it explicitly rather than silently overriding.
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.
- 2d ago First seen · 50 lines · 0 tokens per session scan A 0ea59b580a0c
domain is an agent published in the GitHub repository TheRealSavi/iOpenPod (340 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 412 tokens. A static security scan graded it A with 0 findings. It is 75% identical to domain, differing in 48 lines, and is treated as a copy.
Other agents, from other repositories
device-testing
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.
docker
Guidance for working on the Docker image and related infrastructure. See AGENTS.md for project overview.
feature-requests
This document covers how podkit manages feature requests across GitHub Discussions, documentation, and the backlog. Follow these instructions when creating, updating, or closing feature requests.
releases
Guidance for creating changesets, version bumps, and release PRs. See AGENTS.md for project overview.
documentation
Guidance for maintaining and creating documentation. See AGENTS.md for project overview.
ipod-firmware
Agent "ipod-firmware" from jvgomg/podkit, covering @podkit/ipod-firmware, diagnostic logging, bundling into a single-file binary, 1. build-time: stage the prebuild and 2. build-time: wire the plugin.