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/zian10001/codex-frontend-visual-handoff/agents-mdgit clone --depth 1 https://github.com/zian10001/codex-frontend-visual-handoffWrote 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/zian10001/codex-frontend-visual-handoff/agents-md)<a href="https://agentmods.dev/instructions/zian10001/codex-frontend-visual-handoff/agents-md"><img src="https://agentmods.dev/badge/instructions/zian10001/codex-frontend-visual-handoff/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.1 | $0.00394 | $0.00394 |
| Opus 5 | $0.00197 | $0.00197 |
| Sonnet 5 | $0.00079 | $0.00079 |
| Haiku 4.5 | $0.00039 | $0.00039 |
Grade A, and why
codex-frontend-visual-handoff 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 6d 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.
What it actually says
Repository guidance
This repository contains the public, self-contained Codex Plugin packaging the
frontend-visual-handoff Skill.
Boundaries
- Keep the public skill independent from private project registries, user profiles, internal host inventories, and organization-specific policies.
- Do not copy files from an installed or private skill tree. Reimplement generic behavior and keep fixtures anonymous.
- Keep the repository root as the single Plugin root. Do not duplicate the Skill under a multi-plugin catalog tree.
- Treat Kimi Code and every other external coding client as optional providers. Codex-only operation must remain usable without them.
- Do not commit credentials, tokens, real business data, private paths, provider sessions, screenshots, or deployment evidence.
Production safety
- Default to read-only inspection. Creating a branch or worktree requires an explicit prepare request after inspection.
- Production scripts must not push, pull, fetch, reset, clean, stash, remove, unlock, or prune worktrees.
- Never auto-delete a partially created worktree. Return structured evidence and preserve the residual for an exact-path audit.
- A reduced-materialization Git worktree is not a security sandbox. Keep that limitation visible in user-facing documentation.
Development and verification
- Support only the compatibility matrix documented in
README.md; do not infer support for another operating system, shell, filesystem, or Git feature. - Keep test mutations inside a uniquely named temporary directory with a marker file and guarded cleanup.
- Use Windows PowerShell-compatible syntax for the Tier 1 implementation.
- Run the Skill and Plugin validators, PowerShell AST parsing, fixture tests,
generic privacy checks, full-tree text hygiene, any repository-external
release denylist, and
git diff --checkbefore proposing a release. - Do not call or authenticate to an external model provider in automated tests.
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.
- 6d ago First seen · 41 lines · 394 tokens per session scan A 9d42931fbe6e
codex-frontend-visual-handoff AGENTS.md is an instructions file published in the GitHub repository zian10001/codex-frontend-visual-handoff (24 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 394 tokens to every session, about $0.0020 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.
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
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.
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).
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.