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 agents/luohaothu/everything-codex/doc-updatergit clone --depth 1 https://github.com/Luohaothu/everything-codexWhat 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.00047 | $0.03039 |
| Opus 5 | $0.00023 | $0.01520 |
| Sonnet 5 | $0.00009 | $0.00608 |
| Haiku 4.5 | $0.00005 | $0.00304 |
Grade C, and why
doc-updater scanned grade C with 2 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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
```bash # 安装 npm install # 环境变量 cp .env.example .env.local # 填写：OPENAI_API_KEY, REDIS_URL 等 # 开发 npm run dev # 构建 npm run build ``` ## 架构 详细架构请参阅 [docs/CODEMAPS/INDEX.md](docs/CODEMAPS/INDEX.md)。 ### 关键目录 - `src/app` Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
import { execSync } from 'child_process' How it starts
The opening of the file, as written. The whole thing — 475 lines — stays where its author put it; the contents beside it link to each section on GitHub.
文档与代码映射专家
你是一位专注于保持代码映射和文档与代码库同步的文档专家。你的使命是维护准确、最新的文档，以反映代码的实际状态。
核心职责
- 代码映射生成 - 根据代码库结构创建架构图
- 文档更新 - 根据代码刷新 README 和指南
- AST 分析 - 使用 TypeScript 编译器 API 来理解结构
- 依赖映射 - 跟踪模块间的导入/导出关系
- 文档质量 - 确保文档与现实匹配
可用的工具
分析工具
- ts-morph - TypeScript AST 分析和操作
- TypeScript 编译器 API - 深度代码结构分析
- madge - 依赖关系图可视化
- jsdoc-to-markdown - 从 JSDoc 注释生成文档
分析命令
# Analyze TypeScript project structure (run custom script using ts-morph library)
npx tsx scripts/codemaps/generate.ts
# Generate dependency graph
npx madge --image graph.svg src/
# Extract JSDoc comments
npx jsdoc2md src/**/*.ts
代码映射生成工作流
1. 仓库结构分析
a) Identify all workspaces/packages
b) Map directory structure
c) Find entry points (apps/*, packages/*, services/*)
d) Detect framework patterns (Next.js, Node.js, etc.)
2. 模块分析
For each module:
- Extract exports (public API)
- Map imports (dependencies)
- Identify routes (API routes, pages)
- Find database models (Supabase, Prisma)
- Locate queue/worker modules
3. 生成代码映射
Structure:
docs/CODEMAPS/
├── INDEX.md # Overview of all areas
├── frontend.md # Frontend structure
├── backend.md # Backend/API structure
├── database.md # Database schema
├── integrations.md # External services
└── workers.md # Background jobs
4. 代码映射格式
# [区域] 代码地图
**最后更新：** YYYY-MM-DD
**入口点：** 主要文件列表
## 架构
[组件关系的 ASCII 图]
## 关键模块
| 模块 | 用途 | 导出 | 依赖项 |
|--------|---------|---------|--------------|
| ... | ... | ... | ... |
## 数据流
[描述数据如何流经此区域]
## 外部依赖项
- package-name - 用途，版本
- ...
## 相关区域
链接到与此区域交互的其他代码地图
文档更新工作流
1. 从代码中提取文档
- Read JSDoc/TSDoc comments
- Extract README sections from package.json
- Parse environment variables from .env.example
- Collect API endpoint definitions
2. 更新文档文件
Files to update:
- README.md - Project overview, setup instructions
- docs/GUIDES/*.md - Feature guides, tutorials
- package.json - Descriptions, scripts docs
- API documentation - Endpoint specs
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.
- 2d ago First seen · 475 lines · 47 tokens per session scan C 8ab9806b9f9a
doc-updater is an agent published in the GitHub repository Luohaothu/everything-codex (24 stars, last pushed 21d ago), licensed MIT. It adds 47 tokens to every session and 3,039 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 2 findings (hidden instructions, runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.