Borrowing it
Nothing to install: this file belongs to KimYx0207/Meta_Kim. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/KimYx0207/Meta_Kim/main/AGENTS.mdgit clone --depth 1 https://github.com/KimYx0207/Meta_KimWrote 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/kimyx0207/meta_kim/agents-md)<a href="https://agentmods.dev/instructions/kimyx0207/meta_kim/agents-md"><img src="https://agentmods.dev/badge/instructions/kimyx0207/meta_kim/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/kimyx0207/meta_kim/agents-md"><img src="https://agentmods.dev/badge/instructions/kimyx0207/meta_kim/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.08078 | $0.08078 |
| Opus 5.5 | $0.03231 | $0.03231 |
| Sonnet 5.5 | $0.01616 | $0.01616 |
| Haiku 4.5 | $0.00808 | $0.00808 |
Grade A, and why
Meta_Kim 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 24d 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 — 459 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Meta_Kim for Codex
This file is the Codex entrypoint for maintaining Meta_Kim. Read it as the resident operating guide for this repository, not as a marketing overview.
Fast Read
If you only keep five rules in mind:
- Meta_Kim is one cross-runtime governance system. Claude Code, Codex, OpenClaw, and Cursor are projections of the same canonical layer.
- Its core is general agent governance: understand the current user goal, compare evidenced feasible routes, discover capabilities, orchestrate execution and verify outcomes across domains. Industry packages are optional capability sources; framework acceptance must never replace the user's outcome.
meta-wardenis the normal public front door. Other meta agents are backstage specialists.- Dispatch is capability-first: describe the capability, search agents / skills / tools / capability indexes, then choose the best owner.
- Long-term behavior lives in
canonical/,config/contracts/, andconfig/capability-index/. Runtime trees (.claude/,.codex/,.cursor/,openclaw/) are gitignored projections — runnpm run meta:syncafter clone to generate them locally. - User-visible run-scoped worker labels may be coarse English role-family names such as
frontend,backend, ortest, but Meta_Kim does not project those execution labels as durable agents. Durable governance files stay with the ninemeta-*owners.
Codex Output Rules
- On Windows, do not output raw Windows paths in normal Markdown text. Wrap paths in backticks and prefer forward slashes, for example
D:/path/to/project. - Do not paste full diffs or patches into chat after GitHub submit.
- After GitHub submit, report only the branch name, commit hash, PR URL when present, and a short summary.
What This Repository Is
Do not read Meta_Kim as a folder full of unrelated prompt files.
Read it as:
a cross-runtime architecture pack for intent amplification, governed through small replaceable meta units and projected into multiple AI runtimes.
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.
- 24d ago Changed · +1 lines · +47 tokens per session 52733f3fec03
- 1mo ago First seen · 458 lines · 8,031 tokens per session scan A 155d75611201
Meta_Kim AGENTS.md is an instructions file published in the GitHub repository KimYx0207/Meta_Kim (286 stars, last pushed today), licensed Apache-2.0. It adds 8,078 tokens to every session, about $0.0323 per session on Opus 5.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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.