agentmods.dev

meta-cc: Instructions file for Codex

AGENTS.md

meta-cc AGENTS.md is an instructions file for Codex, OpenCode from yaleh/meta-cc. It costs 564 tokens per session, scanned A, original, MIT.

Repository-specific instructions for the `meta-cc` Go project, including its folder layout, commands, coding style, and testing rules. An `AGENTS.md` file gives coding agents the context they need to work in that repository.

In plain words
What is it for?
Use it when building, testing, formatting, linting, or adding capabilities to the `meta-cc` project.
Why use it?
It reduces guesswork about where code belongs and which commands and checks are required before changes are considered complete.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md.

This is yaleh/meta-cc's own configuration. It tells Codex and OpenCode how to work on meta-cc itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything meta-cc configures →

not rated 22repo changed 23d ago A scan 564 tokens original MIT
View source ↗ yaleh/meta-cc
Reuse

Borrowing it

Nothing to install: this file belongs to yaleh/meta-cc. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/yaleh/meta-cc/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/yaleh/meta-cc

Made for: Codex, OpenCode.

Wrote 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.

agentmods badge for meta-cc AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/yaleh/meta-cc/agents-md/github.svg)](https://agentmods.dev/instructions/yaleh/meta-cc/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/yaleh/meta-cc/agents-md"><img src="https://agentmods.dev/badge/instructions/yaleh/meta-cc/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.

agentmods 80×15 button for meta-cc AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/yaleh/meta-cc/agents-md"><img src="https://agentmods.dev/badge/instructions/yaleh/meta-cc/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 564 This file is loaded in full into every session.
When invoked 564 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00564 $0.00564
Opus 5.5 $0.00226 $0.00226
Sonnet 5.5 $0.00113 $0.00113
Haiku 4.5 $0.00056 $0.00056

Measured 23d ago against content hash 471d1d53dd73, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

meta-cc 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 23d 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.

AGENTS.md · 35 lines

How it starts

The opening of the file, as written. The whole thing — 35 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Repository Guidelines

Project Structure & Module Organization

  • cmd/ holds CLI and MCP entry points; main.go wires shared packages.
  • Core logic lives in internal/ (analysis, session parsing).
  • Plugin-facing content sits under plugin-src/ (commands, skills); docs and diagrams live in docs/.
  • Integration and regression suites live beside source code, with longer MCA workflows in tests/integration/; automation scripts are in scripts/.

Build, Test, and Development Commands

  • make dev formats code then builds both binaries for quick local iteration.
  • make build produces meta-cc and meta-cc-mcp; make install drops the CLI into your GOBIN.
  • make test runs short Go tests; make test-all includes slow E2E coverage; make test-coverage emits coverage.html.
  • Quality bundles: make pre-commit (full lint + tests), make ci (all checks).

Coding Style & Naming Conventions

  • Target Go toolchain go1.24.9; rely on gofmt, goimports, and golangci-lint via make fmt and make lint.
  • Follow Go idiomatic naming (MetaClient, parseSession); keep filenames snake_case.
  • Error handling leans on internal/errors; run make lint-errors to verify sentinel wrapping.
  • Prefer package-scoped docs for exported APIs; keep agent/spec markdowns concise and task-scoped.

Testing Guidelines

  • Use Go’s testing package with TestXxx naming; table tests live next to implementations in internal/.
  • Integration flows execute from tests/integration/ scripts; mark long-running tests with //go:build e2e and rely on make test-all.
  • Maintain ≥80% coverage (make test-coverage-check); attach new fixtures under tests/fixtures/ and register cleanup in tests.

Commit & Pull Request Guidelines

  • Commit messages follow Conventional Commits (type(scope): summary) as seen in history (docs(methodology): …).
  • Before pushing, run make pre-commit and confirm lint, vet, and sentinel error checks pass.
  • Pull requests should describe intent and link issues; add screenshots for UI/tooling output when relevant.
  • For release-ready changes, mention if sync-plugin-files needs to run.

Read the full file on GitHub · 35 lines

Changes

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.

  1. 23d ago Changed · -46 tokens per session 471d1d53dd73
  2. 1mo ago First seen · 35 lines · 610 tokens per session scan A bb478c305ee7

Subscribe to this mod's changes

meta-cc AGENTS.md is an instructions file published in the GitHub repository yaleh/meta-cc (22 stars, last pushed 23d ago), licensed MIT. It adds 564 tokens to every session, about $0.0023 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.

Related

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).

microsoft/vscode · 9,715 tokens

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.

vercel/next.js · 7,581 tokens

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).

microsoft/vscode · 5,262 tokens

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.

langchain-ai/langchain · 4,680 tokens

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).

microsoft/vscode · 2,731 tokens

deepseek-harness AGENTS.md

AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.

deepseek-ai/deepseek-harness · 4,261 tokens