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/srstomp/pokayokay/agents-mdgit clone --depth 1 https://github.com/srstomp/pokayokayWrote 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/srstomp/pokayokay/agents-md)<a href="https://agentmods.dev/instructions/srstomp/pokayokay/agents-md"><img src="https://agentmods.dev/badge/instructions/srstomp/pokayokay/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.01756 | $0.01756 |
| Opus 5 | $0.00878 | $0.00878 |
| Sonnet 5 | $0.00351 | $0.00351 |
| Haiku 4.5 | $0.00176 | $0.00176 |
Grade B, and why
pokayokay AGENTS.md scanned grade B 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 3d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
Note: Codex installs in two steps — `codex plugin marketplace add` registers the source under `[marketplaces.pokayokay]` in `~/.codex/config.toml`, and `codex plugin add pokayokay@pokayokay` installs the plugin (recorded How it starts
The opening of the file, as written. The whole thing — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
This file provides guidance to Codex when working with code in this repository.
Project Overview
pokayokay is a development-orchestration plugin built primarily for Claude Code, with additive Codex support. It integrates with ohno (task management via MCP) to provide structured workflows with configurable human oversight.
Important: the Codex and Claude Code surfaces differ. On Codex, the plugin provides skills, the ohno MCP server, and lifecycle hooks. The commands/ and agents/ directories are Claude Code-only — Codex has no Task-tool subagent dispatch, and the .codex-plugin/plugin.json manifest exposes only skills/ and .mcp.json. When a skill references dispatching a yokay-* agent, execute that agent's role inline instead: read the corresponding plugins/pokayokay/agents/yokay-<name>.md and follow its checklist and output contract directly.
Development Commands
# Register this checkout as a Codex plugin marketplace, then install the
# plugin from it (run from repo root)
codex plugin marketplace add .
codex plugin add pokayokay@pokayokay
# Run the CLI setup wizard locally (wires ohno MCP + Codex hooks)
npm --prefix cli install
node cli/bin/cli.js
# Run specific shell tests
bash plugins/pokayokay/tests/<test-name>.test.sh
# Run the full test suite (shell + node, per-test PASS/FAIL, non-zero exit on failure)
npm test
# or directly:
bash plugins/pokayokay/tests/run-tests.sh
# Codex-specific test suites
bash plugins/pokayokay/tests/codex-compatibility.test.sh
node --test plugins/pokayokay/tests/cli-dual-runtime.test.mjs
Note: Codex installs in two steps — codex plugin marketplace add registers the source under [marketplaces.pokayokay] in ~/.codex/config.toml, and codex plugin add pokayokay@pokayokay installs the plugin (recorded under [plugins."pokayokay@pokayokay"]). The marketplace step alone does not install anything. The command is add, not install, and there is no codex plugin validate.
Architecture
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.
- 3d ago First seen · 130 lines · 1,756 tokens per session scan B a476f31bc729
pokayokay AGENTS.md is an instructions file published in the GitHub repository srstomp/pokayokay (9 stars, last pushed 2mo ago), licensed MIT. It adds 1,756 tokens to every session, about $0.0088 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
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.