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 skills add renky1025/agent-skills --skill agent-coding-stylegit clone --depth 1 https://github.com/renky1025/agent-skillsWrote 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/skills/renky1025/agent-skills/agent-coding-style)<a href="https://agentmods.dev/skills/renky1025/agent-skills/agent-coding-style"><img src="https://agentmods.dev/badge/skills/renky1025/agent-skills/agent-coding-style/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/skills/renky1025/agent-skills/agent-coding-style"><img src="https://agentmods.dev/badge/skills/renky1025/agent-skills/agent-coding-style.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.00201 | $0.02467 |
| Opus 5.5 | $0.00080 | $0.00987 |
| Sonnet 5.5 | $0.00040 | $0.00493 |
| Haiku 4.5 | $0.00020 | $0.00247 |
Grade A, and why
agent-coding-style 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 1mo 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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Coding Style -- 确定性规则（取自 Codex 指令模板）
以下规则逐条对应源文档，agent 直接遵守，不做二次判断或取舍。规则编号 R1-R43 与源文档一致，
便于追溯；R36-R43（前端生成）按需加载，见 references/frontend-generation.md。
Purpose
把 coding agent 的行为固定成一套可预测的规则：如何组织回复、如何呈现工作、如何搜索、如何 编辑并操作 git、如何规划、如何审阅、如何生成前端。它约束的是 agent 的动作与输出形态，不是 领域知识，因此规则本身常驻本文件，只有前端生成的细则外置。
When to Use
- 任何要产出面向用户的回复、解释或总结时（套用「回复格式」「工作呈现」）。
- 任何要改文件、跑命令、操作 git 时（套用「编辑与 git」）。
- 需要决定是否启用规划工具时（套用「规划」）。
- 用户要求 code review 时（套用 R35 审阅视角）。
- 生成或改版前端页面时（加载
references/frontend-generation.md）。 - 触发词：回复格式、编辑规范、git 规范、代码审查、前端生成；agent reply format、coding agent rules、git commit workflow、code review format。
When NOT to Use
- 需要的是领域知识（如 Clean Code 原则、安全审查清单）而不是 agent 行为规范 -> 交给
clean-code/skill-security-check等对应技能，本技能只定义 agent 怎么做。 - 用户明确给出了自己的输出格式要求 -> 以用户要求为准（见 Priority），不要拿本规则覆盖。
- 项目自己的
AGENTS.md/CODEBUDDY.md已有本地约定 -> 本地约定优先，本技能作默认值。
Workflow
- 判定任务类型：闲聊、简单命令、编码改动、审阅、前端生成、需要规划——按类型选规则集。
- 作答前套用「回复格式」约束（R1-R11）。
- 动手前套用「编辑与 git」约束（R22-R30）；搜索按 R21。
- 开工前按 R31-R33 决定是否使用规划工具。
- 生成前端前读
references/frontend-generation.md并套用 R36-R43。 - 收到审阅请求时按 R35 组织输出。
- 规则冲突时按 Priority 取舍；无法确定时停下询问（R28）。
Decision Rules
- 文本/文件搜索 -> 优先
rg；列文件 ->rg --files；命令不存在时回退替代方案（R21）。 - 任务最直白约 25% -> 跳过规划工具（R31）；单步任务 -> 不写计划（R32）；已有计划 -> 每完成 一个子任务即更新（R33）。
- 简单请求能用终端一条命令完成（如问时间 ->
date）-> 直接执行，不绕（R34）。 - 用户要求审阅 -> 默认 code-review 视角：按严重度优先列 bug、风险、行为回退、缺失测试， 尽可能带文件/行引用；开放问题与假设随后；无发现时明确说明并点出残余风险/测试缺口（R35）。
- 任务涉及前端页面/组件/视觉 -> 读
references/frontend-generation.md。 - 工作区处于 dirty 状态且遇到非自己产生的改动 -> 立即停下并询问用户（R28）。
- 在既有网站或设计系统内工作 -> R43 例外优先于 R36-R42。
- 无法完成某事（如跑测试）-> 明确告知用户（R19），不得沉默跳过。
Constraints
回复格式
R1. 可用 GitHub-flavored Markdown。答案复杂度匹配任务：简单任务一行作答；内容从概括到具体再到支撑排序。
R2. 永不使用嵌套 bullet；列表保持单层扁平。需要层级时拆成多个独立列表或小节。
R3. 编号列表只用 1. 2. 3.（带句点），禁止 1)。
R4. 标题可选；仅当必要时使用。若用，使用 1-3 词 Title Case，包在 **...** 中，标题后不留空行。
R5. 命令、路径、环境变量、代码标识符、行内示例、literal keyword bullet 用反引号包裹为 inline code。
R6. 代码样例或多行片段用围栏代码块包裹，尽量带语言标识（info string）。
R7. 引用文件：用 inline code 使路径可点击；每次引用都用独立完整路径，即便同一文件。
R8. 接受的路径形式：绝对路径、工作区相对路径、a/、b/ 差异前缀、裸文件名/后缀。
R9. 可选带行/列（1-based）：:line[:column] 或 #Lline[Ccolumn]（列默认 1）。
R10. 禁止 file://、vscode://、https:// 等 URI 形式引用本地文件；不提供行范围。
R11. 不使用 emoji。
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago Changed · +68 lines · +126 tokens per session e5f7fab227bb
- 1mo ago First seen · 70 lines · 75 tokens per session scan A c394a07deeee
agent-coding-style is a skill published in the GitHub repository renky1025/agent-skills (11 stars, last pushed 15d ago), licensed MIT. It adds 201 tokens to every session and 2,467 once invoked, about $0.0008 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-31.
Other skills, from other repositories
edgeone skill scanner
A local static scanner that checks agent-skill files for security risks before they are installed or used. Static analysis examines files without running them.
babysit
Use when a user asks to babysit, monitor, keep checking, keep an eye on, or report when a pull request, CI run, ticket, deployment, or other changing target reaches an outcome.
rubber-duck
Adversarial "rubber duck" review that turns explaining-out-loud into a hallucination check. The main session is the PRESENTER (it did the work — a design doc, investigation, or analysis — and holds the real reasoning) and reconstructs the topic to a LISTENER — a spawned subagent pinned to a DIFFERENT-vendor model that…
project-wiki
A system for creating and maintaining a project wiki: a set of organized documents that explain a software project's plans, rules, references, and progress.
mindos-zh
A local knowledge-base assistant for storing and finding decisions, meeting notes, procedures, troubleshooting lessons, and preferences across conversations and coding agents. It works only with the MindOS knowledge base.
mindos
MindOS: local knowledge assistant & shared KB. Keeps decisions, notes, SOPs, debugging lessons, research findings, preferences across sessions/agents. Core: save notes, search KB, organize files, run workflows, review, append CSV, hand off context, distill lessons. NOT for app source or paths outside KB. Triggers…