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/the-void-ia/void-box/codexgit clone --depth 1 https://github.com/the-void-ia/void-boxWhat 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.01748 |
| Opus 5 | $0.00000 | $0.00874 |
| Sonnet 5 | $0.00000 | $0.00350 |
| Haiku 4.5 | $0.00000 | $0.00175 |
Grade A, and why
codex scanned grade A with 1 finding 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 yesterday.
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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
awk + curl + sha256sum/shasum are available. How it starts
The opening of the file, as written. The whole thing — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codex flavor — scripts/build_codex_rootfs.sh
Production OpenAI-Codex-capable rootfs/initramfs.
What it bundles
- The
codexCLI binary (Rust musl-static, no shared libraries needed). - SSL CA certificates for HTTPS API calls.
/etc/passwd+/etc/groupfor the sandbox user (uid 1000).
When to use
kind: workflowspecs that execcodexas a workflow step.kind: agentspecs withllm.provider: codex. RequiresOPENAI_API_KEYin the host environment or a valid~/.codex/auth.json(see Auth section below).
Discovery
The script locates the codex binary in priority order:
CODEX_BINenv var pointing at a Linux ELF binary — local dev only.codexon PATH (Linux host only — the macOS Mach-O binary cannot run inside the Linux guest) — local dev only.CODEX_VERSIONset → explicit override; requires a matchingCODEX_SHA256env var (SHA-256 of the downloaded tarball) so developers supply the hash they are asking the build to trust.- Default: download the version and URL pinned in
scripts/agents/manifest.tomland verify against the pinned SHA-256 (computed against the tarball as it lands on disk — the build then extracts the binary from the verified tarball).
Pinning and verification (R-B5c.1)
The default build path is hash-pinned. scripts/agents/manifest.toml
holds one table per (agent, platform, arch) tuple with a version, url
template, and sha256. build_codex_rootfs.sh fetches the URL, computes
SHA-256 of the downloaded tarball, and fails the build if the digest
does not match — the expected and observed digests are both printed on
failure.
Parser choice: shell + awk (scripts/lib/agent_manifest.sh). No Python or
Rust sidecar is required, which keeps the builder working anywhere bash +
awk + curl + sha256sum/shasum are available.
Hash updates are reviewed PRs, not silent upstream events. The weekly
workflow .github/workflows/bump-agents.yml (Mondays 09:00 UTC) checks for
new upstream versions and opens one PR per agent containing the bumped
arches, with per-arch SHA-256s listed in the PR body.
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.
- yesterday First seen · 160 lines · 0 tokens per session scan A b90e4a345e12
codex is an agent published in the GitHub repository the-void-ia/void-box (88 stars, last pushed 4d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,748 tokens. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
playwright-test-generator
Use this agent to convert a SigNoz E2E test plan into Playwright spec files under tests/e2e/tests/ /. Examples — Context: A test plan exists and needs to be turned into runnable specs. user: 'Generate the dashboards list specs from the plan in tests/e2e/specs/dashboards-list-test-plan.md' assistant: 'Using the…
playwright-test-healer
Use this agent to debug and fix failing SigNoz E2E Playwright tests. Examples — Context: A spec is red. user: 'tests/e2e/tests/dashboards/list.spec.ts is failing, fix it' assistant: 'Using the healer agent to debug each failing scenario and adjust the spec.' Context: After a frontend change a previously-green spec…
playwright-test-planner
Use this agent to create a comprehensive E2E test plan for a SigNoz frontend feature. Examples — Context: A new feature has shipped and we need test coverage. user: 'Plan E2E tests for the alerts list page' assistant: 'I'll use the planner agent to read the relevant frontend source, navigate the page in a real…
memex-keeper
Custodian of the agent's documentary persistent self — loads and logs the cross-session bias-log through the memex store, and maintains the memex companion repo (verify gate, milestone handoff).
trace-analyzer
Analyze trace files for cases using agent-based detection.
self-care/context-refiner
You are a context remediation agent for the Self-Care plugin. Your job is to propose and apply fixes for agent cases by editing project files — system prompts, tool descriptions, and context documents.