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.
git clone --depth 1 https://github.com/Hahaxiong838383/open-feishu-mcp-serverWrote 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/rules/hahaxiong838383/open-feishu-mcp-server/dev-guidelines)<a href="https://agentmods.dev/rules/hahaxiong838383/open-feishu-mcp-server/dev-guidelines"><img src="https://agentmods.dev/badge/rules/hahaxiong838383/open-feishu-mcp-server/dev-guidelines/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/rules/hahaxiong838383/open-feishu-mcp-server/dev-guidelines"><img src="https://agentmods.dev/badge/rules/hahaxiong838383/open-feishu-mcp-server/dev-guidelines.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.00002 | $0.00398 |
| Opus 5 | $0.00001 | $0.00199 |
| Sonnet 5 | $0.00000 | $0.00080 |
| Haiku 4.5 | $0.00000 | $0.00040 |
Grade A, and why
dev-guidelines 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 8d 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.
This is a copy
100% identical to dev-guidelines — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
项目开发规范
仓库信息
- Repository URL: https://github.com/ztxtxwd/feishu-mcp-server.git
- Workflow: GitHub Flow
开发流程
- 创建 Issue
- 从
main创建功能分支，使用描述性名称 (如feature/add-new-component) - 在分支上进行代码修改
- 向
main提交 Pull Request - 通过 Code Review 并获得批准
- 合并 Pull Request
- 删除功能分支
- 关闭 Issue
Issue 管理
- 使用
.github/ISSUE_TEMPLATE中的模板创建 Issue - 可用模板:
- Bug report
- Feature request
- Custom issue
分支策略
- 分支命名规范:
feature/、bugfix/、hotfix/、release/或support/开头，后接描述性名称 - 所有分支均从
main创建
提交信息
- 遵循 Conventional Commits 格式:
feat: 新功能fix: Bug 修复docs: 文档修改style: 不影响代码含义的修改 (空格、格式化等)refactor: 既非修复 Bug 也非新增功能的代码重构test: 新增或更新测试chore: 构建过程或辅助工具的变更
Pull Request 流程
- 在 PR 描述中引用相关 Issue
- 确保所有测试通过
- 如有必要，更新文档
- 至少获得一次审批后再合并
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.
- 8d ago First seen · 48 lines · 2 tokens per session scan A cbdfc327ac2e
dev-guidelines is a cursor rule published in the GitHub repository Hahaxiong838383/open-feishu-mcp-server (0 stars, last pushed 1mo ago), licensed MIT. It adds 2 tokens to every session and 398 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to dev-guidelines, differing in 0 lines, and is treated as a copy.
Other cursor rules, from other repositories
git
Conventional commit message format for git commits.
git-commit-attribution
Git commits must use the human developer identity only; never Cursor Agent co-authorship.
commit-sponsors
Every git commit message must acknowledge BetterDesk supporters.
conventional-commits
Use the Conventional Commit Messages specification to generate commit messages.
git-commits
description: "Reference and apply the git commits skill for Conventional Commit formatting and pre-push checks." alwaysApply: true.
git-commit-standards
Enforce structured Git commit messages.