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 skills/stanshy/agenthub/gate-recordnpx skills add Stanshy/AgentHub --skill gate-recordgit clone --depth 1 https://github.com/Stanshy/AgentHubWrote 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/stanshy/agenthub/gate-record)<a href="https://agentmods.dev/skills/stanshy/agenthub/gate-record"><img src="https://agentmods.dev/badge/skills/stanshy/agenthub/gate-record.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 | $0.00015 | $0.00720 |
| Opus 5 | $0.00008 | $0.00360 |
| Sonnet 5 | $0.00003 | $0.00144 |
| Haiku 4.5 | $0.00002 | $0.00072 |
Grade A, and why
gate-record 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 5d 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.
What it actually says
Gate 審核紀錄
在開發計畫書第 10 節附加 Gate 審核紀錄。
使用方式
/gate-record <gate-type> <decision> [comment]
參數
$0: Gate 類型（G0 / G1 / G2 / G3 / G4 / G5 / G6）$1: 決策（見下方格式規範）$ARGUMENTS: 完整參數（含審核意見）
格式規範（系統解析依賴，務必遵守）
Gate 類型（第 1 欄）
必須為：G0 / G1 / G2 / G3 / G4 / G5 / G6
決策（第 3 欄）— 嚴格使用以下純文字值
| 決策值 | 對應系統狀態 | 說明 |
|---|---|---|
✅ 通過 |
approved | 審核通過 |
❌ 駁回 |
rejected | 審核不通過 |
⚠️ 附條件通過 |
approved | 有條件通過 |
禁止使用其他格式（如純文字「通過」、英文「approved」）。 系統解析器
decisionToStatus()依賴上述關鍵字判斷狀態。
日期（第 2 欄）
格式：YYYY-MM-DD（如 2026-03-26）
審核意見（第 4 欄）
自由文字，簡述審核理由。
執行步驟
-
找到當前 Sprint 的 dev-plan： 使用 Glob tool 搜尋
proposal/sprint*-dev-plan.md，取最新的檔案路徑。 -
讀取 dev-plan 找到第 10 節的 Gate 紀錄表： 使用 Read tool 讀取上述 dev-plan 完整內容，找到
Gate 紀錄表格區段。 -
找到對應的 Gate 行（如
| G0 |），更新該行而非新增：- 如果該行已有資料（日期/決策非空），直接覆蓋
- 如果該行是空的（
| G0 | | | |），填入資料
| $0 | {YYYY-MM-DD} | {決策值} | {審核意見} |
- 使用 Edit 工具精確替換該行，不改動其他內容。
範例
| G0 | 2026-03-26 | ✅ 通過 | 老闆確認需求，提案通過 |
| G1 | 2026-03-27 | ❌ 駁回 | 圖稿缺少手機版響應式設計 |
| G2 | 2026-03-28 | ✅ 通過 | 程式碼品質合格 |
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.
- 5d ago First seen · 67 lines · 15 tokens per session scan A 8dac31e9025c
gate-record is a skill published in the GitHub repository Stanshy/AgentHub (200 stars, last pushed 4mo ago), licensed MIT. It adds 15 tokens to every session and 720 once invoked, about $0.0001 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 skills, from other repositories
comet-native
Comet Native 工作流。当用户明确调用 /comet-native、要求启动或恢复 Native change，或入口路由到 Native 时使用。.
comet-classic
Comet Classic 工作流（OpenSpec + Superpowers）。当用户明确调用 /comet-classic、要求启动或恢复 Comet Classic，或 resume-probe 返回可无歧义恢复的 active Classic change 时使用。.
comet-build
Comet Classic 阶段 3 —— 恢复或创建实施计划并执行其任务。.
comet-github-idea-to-issue
基于当前代码库，将本地 Comet 想法、观察到的回归或改进提案整理为聚焦的 GitHub Issue 草稿。用户要求把本地调查转换为 Issue、后续 Issue、Bug、Feature 或维护任务时使用。.
create-request
Create, update, or scan per-task request tickets for progress tracking. These are date-prefixed non-lifecycle docs under requests/, NOT feature-level requirements (use /req-analyze for those). Use when: tracking task progress, updating completion status, scanning incomplete requests, checking request status dashboard.…
kn-handoff
Use when a feature crosses repository boundaries and one side must hand work to the other - generates a self-contained frontend-to-backend brief or backend-to-frontend API contract.