my-commit-report AGENTS.md

Repository instructions for my-commit-report, a skill that creates a summary of Git commits by the configured user over a chosen time period. Git is a system for recording code changes.

In plain words
What is it for?
Use them when changing the skill, its documentation, or repository structure, while keeping the report in Traditional Chinese and avoiding history rewrites or remote changes.
Why use it?
They give contributors consistent rules for the skill's location, language, supported commands, and safety boundaries.

Instructions file for CodexOpenCode

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/maylogger/my-commit-report/agents-md
Clone the repo
git clone --depth 1 https://github.com/maylogger/my-commit-report

Made for: Codex, OpenCode.

Per session 461 This file is loaded in full into every session.
When invoked 461 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.00461 $0.00461
Opus 5 $0.00230 $0.00230
Sonnet 5 $0.00092 $0.00092
Haiku 4.5 $0.00046 $0.00046

Measured yesterday against content hash 50efa0a74137, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

my-commit-report 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 yesterday.

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 · 34 lines

What it actually says

AGENTS.md

本儲存庫是公開的 Agent Skill 套件,遵循 Agent Skills 開放格式,並以 .agents/skills/ 作為跨工具通用安裝路徑。

專案目的

提供 my-commit-report skill:讓 AI agent 依目前 git config 使用者,整理指定時間區間內的 commit 摘要報告(預設過去兩週)。

目錄約定

.agents/skills/my-commit-report/SKILL.md   # skill 本體(唯一必要檔)
AGENTS.md                                  # 本檔:給 agent / 貢獻者的常駐說明
README.md                                  # 給人類的安裝與使用說明
LICENSE                                    # MIT
  • Skill 目錄名稱必須與 SKILL.md frontmatter 的 name 一致。
  • 不要把 skill 放到 .cursor/skills-cursor/(Cursor 內建保留路徑)。
  • 若新增其他 skill,放在 .agents/skills/<skill-name>/SKILL.md

修改 Skill 時

  1. 先讀 .agents/skills/my-commit-report/SKILL.md
  2. 保持 frontmatter 的 namedescription 正確;description 需同時說明「做什麼」與「何時觸發」。
  3. 流程仍以跨平台 git 指令為準,不要改成依賴特定 shell(例如只在 PowerShell 能跑的腳本)。
  4. 報告輸出維持臺灣正體中文。
  5. 不修改使用者的 git config,不執行 destructive git 指令。

安全

  • 本 skill 僅讀取 git 歷史並產出摘要,不應新增會寫入遠端、改寫歷史、或略過 hook 的步驟。
  • 若未來加入 scripts/,必須在 README 與 skill 內標明會執行哪些指令。
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. yesterday First seen · 34 lines · 461 tokens per session scan A 50efa0a74137

Subscribe to this mod's changes

my-commit-report AGENTS.md is an instructions file published in the GitHub repository maylogger/my-commit-report (5 stars, last pushed 1mo ago), licensed MIT. It adds 461 tokens to every session, about $0.0023 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.

Related

Other instructions, from other repositories

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

buildNext

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

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

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

spec-kit 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,040 tokens

langchain 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