Borrowing it
Nothing to install: this file belongs to Sunne927/Codex-CLI-Bridge-for-Lark-Feishu. 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/Sunne927/Codex-CLI-Bridge-for-Lark-Feishu/main/AGENTS.mdgit clone --depth 1 https://github.com/Sunne927/Codex-CLI-Bridge-for-Lark-FeishuWrote 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/sunne927/codex-cli-bridge-for-lark-feishu/agents-md)<a href="https://agentmods.dev/instructions/sunne927/codex-cli-bridge-for-lark-feishu/agents-md"><img src="https://agentmods.dev/badge/instructions/sunne927/codex-cli-bridge-for-lark-feishu/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.00901 | $0.00901 |
| Opus 5 | $0.00451 | $0.00451 |
| Sonnet 5 | $0.00180 | $0.00180 |
| Haiku 4.5 | $0.00090 | $0.00090 |
Grade A, and why
Codex-CLI-Bridge-for-Lark-Feishu 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 7d 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Router
The product is Codex CLI Bridge for Lark (Feishu). The repository/package compatibility name remains telegram-codex-bridge; do not treat that retained name or shared compatibility types as product positioning. The active Feishu direction is not yet fully shipped, so keep three categories separate:
- current truth in product, architecture, operations, generated docs, and code
- active Feishu plan in
docs/plans/2026-07-27-feishu-native-bridge-refactor.md - older Web, future, plan, and archive context
Default Retrieval
Read this file, then one domain router, then one leaf or narrow source owner. Expand only for a demonstrated cross-cutting dependency or conflict.
| Task | Read next |
|---|---|
| current behavior, architecture, operations, or planning | docs/AGENTS.md |
| implementation, refactor, tests, or bug fix | src/AGENTS.md |
| GitHub bootstrap scripts | scripts/AGENTS.md |
| bundled setup skills | skills/AGENTS.md |
Source Priority
- active user instruction
- current-truth docs
- current implementation and tests
- Codex protocol evidence
- active plan
- future and historical material
If code and current docs disagree, report and resolve the mismatch according to the task. Do not blend them.
Feishu Rule
For Feishu development, deployment, debugging, or fixes, use the workspace's local Feishu official-document mirror before changing platform fields, permissions, event names, callback shapes, limits, or release steps. Open the matched official raw Markdown. The local full mirror excludes some server API, client API, and Feishu CLI columns; explicitly supplement those gaps from official sources when required.
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.
- 7d ago First seen · 86 lines · 901 tokens per session scan A 7bec06bd27b4
Codex-CLI-Bridge-for-Lark-Feishu AGENTS.md is an instructions file published in the GitHub repository Sunne927/Codex-CLI-Bridge-for-Lark-Feishu (31 stars, last pushed 1mo ago), licensed MIT. It adds 901 tokens to every session, about $0.0045 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
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 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).
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.
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.