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 instructions/cyberboyayush/zenox/agents-mdgit clone --depth 1 https://github.com/CyberBoyAyush/zenoxWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/instructions/cyberboyayush/zenox/agents-md)<a href="https://agentmods.dev/instructions/cyberboyayush/zenox/agents-md"><img src="https://agentmods.dev/badge/instructions/cyberboyayush/zenox/agents-md.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.01940 | $0.01940 |
| Opus 5 | $0.00970 | $0.00970 |
| Sonnet 5 | $0.00388 | $0.00388 |
| Haiku 4.5 | $0.00194 | $0.00194 |
Grade A, and why
zenox AGENTS.md 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Zenox - Project Guidelines
Overview
Zenox is an OpenCode plugin that provides intelligent agent orchestration with specialized subagents (explorer, librarian, oracle, ui-planner, inspector), background tasks for parallel execution, and smart delegation.
Tech Stack
- Runtime: Bun
- Language: TypeScript (strict mode)
- Package Manager: Bun (
bun.lock) - Build:
bun build+tsc --emitDeclarationOnly - Dependencies:
@opencode-ai/plugin,@opencode-ai/sdk,zod,commander,picocolors,@clack/prompts
Project Structure
src/
├── index.ts # Plugin entry point
├── agents/ # Subagent definitions (explorer, librarian, oracle, ui-planner, inspector)
├── background/ # Background task system for parallel execution
├── cli/ # CLI commands (install, config)
├── config/ # Configuration loading and schema
├── features/ # Feature modules (task-toast)
├── hooks/ # Event hooks (auto-update, keyword-detector, todo-enforcer)
├── mcp/ # MCP server integrations (exa, grep_app, sequential-thinking)
├── orchestration/ # System prompt injection for delegation
├── shared/ # Shared utilities (variants, gates)
└── tools/ # Tool definitions (session, code-intelligence, project-guidelines)
Commands
bun run build # Build the plugin
bun run clean # Remove dist folder
bun run typecheck # Type check without emitting
Code Conventions
- No
anytypes - Always use proper typing - Zod for validation - All config schemas use Zod
- ESM only -
"type": "module"in package.json - Minimal comments - Only document non-obvious logic
- No hardcoded API keys - Always use environment variables
Agent Types
| Agent | Purpose | Default Model |
|---|---|---|
| explorer | Codebase search, file discovery | claude-haiku-4-5 |
| librarian | Library research, docs lookup | claude-sonnet-4-6 |
| oracle | Architecture decisions, debugging | gpt-5.6-sol |
| ui-planner | Frontend design, CSS, animations | claude-opus-4-8 |
| inspector | Runs checks, reports PASS/FAIL ground truth | claude-sonnet-5 |
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.
- 4d ago First seen · 107 lines · 1,940 tokens per session scan A c513a3e5e15e
zenox AGENTS.md is an instructions file published in the GitHub repository CyberBoyAyush/zenox (45 stars, last pushed 1mo ago), licensed MIT. It adds 1,940 tokens to every session, about $0.0097 per session on Opus 5. 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-08-30.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.