agentmods.dev

everything-analysis-agent AGENTS.md

Repository instructions for an analysis-agent project that stores skills, plugins, and integrations. They define communication, coding, error-handling, documentation, and file-organization rules for agents working in the repository.

In plain words
What is it for?
Use them when changing agent assets, skills, plugins, integrations, Python code, or project documentation so the work follows the repository's local rules.
Why use it?
They give coding agents project-specific expectations that may not be obvious from the source code. This reduces inconsistent language, style, error handling, and documentation decisions.

Instructions file for CodexOpenCode

2 4mo ago A scan 443 tokens original Apache-2.0
View the source file yellowbee686/everything-analysis-agent
Install

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.

agentmods
npx agentmods add instructions/yellowbee686/everything-analysis-agent/agents-md
Clone the repo
git clone --depth 1 https://github.com/yellowbee686/everything-analysis-agent

Made for: Codex, OpenCode.

Per session 443 This file is loaded in full into every session.
When invoked 443 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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 $0.00443 $0.00443
Opus 5 $0.00221 $0.00221
Sonnet 5 $0.00089 $0.00089
Haiku 4.5 $0.00044 $0.00044

Measured 2d ago against content hash ca4369015436, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

everything-analysis-agent 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 2d 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 · 44 lines

What it actually says

AGENTS.md

System Rules

  • Read this file and the relevant skill or submodule AGENTS.md before making changes.
  • Communicate with users in Chinese.
  • Write code, comments, docstrings, and command-facing text in English unless a domain term requires Chinese.
  • Python code must include type annotations.
  • Prefer readable, pythonic code.
  • Follow fail-fast behavior. When compatibility handling is needed, log with logger.error and return a clear error result instead of raising from user-facing helpers.
  • Prefer built-in collection types such as list and dict over List and Dict.

Repository Purpose

This repository stores analysis-agent assets such as skills, plugins, and MCP integrations.

Docs

  • Research and design notes live under docs/.
  • When the target reader is Chinese, docs/ research notes may be written in Chinese.
  • Include the investigation date and source references for comparative or external research notes.
  • QMD setup and usage notes live in docs/qmd_usage.md.

Skills

  • Skills live under skills/<skill-name>/.
  • Each skill must include SKILL.md with name and description frontmatter.
  • Keep SKILL.md concise. Put detailed workflows, tool maps, and setup notes in references/.
  • Put deterministic helper commands in scripts/.
  • Validate changed skills with:
python3 /Users/bytedance/.codex/skills/.system/skill-creator/scripts/quick_validate.py skills/<skill-name>

If the default python3 does not have PyYAML, use any project virtual environment that provides yaml.

CBETA MCP Submodule

  • mcp_servers/CbetaMCP is a git submodule pinned to a known commit.
  • Do not commit virtual environments, caches, logs, or generated Python bytecode from the submodule.
  • The default local MCP endpoint is http://localhost:18765/mcp/.
  • Start the CBETA MCP server only when a live CBETA query requires it. Check the endpoint first, then start it on demand.
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. 2d ago First seen · 44 lines · 443 tokens per session scan A ca4369015436

Subscribe to this mod's changes

everything-analysis-agent AGENTS.md is an instructions file published in the GitHub repository yellowbee686/everything-analysis-agent (2 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 443 tokens to every session, about $0.0022 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-31.

LanguagesWriting and docs
Related

Other instructions, from other repositories

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.

github/spec-kit · 7,104 tokens

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 · 6,785 tokens

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.

openai/codex · 5,182 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,345 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, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens

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.

vercel/next.js · 7,296 tokens