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 iamraven-tw/Learn-GAS --skill google-apps-script-debugginggit clone --depth 1 https://github.com/iamraven-tw/Learn-GASWrote 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/iamraven-tw/learn-gas/google-apps-script-debugging)<a href="https://agentmods.dev/skills/iamraven-tw/learn-gas/google-apps-script-debugging"><img src="https://agentmods.dev/badge/skills/iamraven-tw/learn-gas/google-apps-script-debugging/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/iamraven-tw/learn-gas/google-apps-script-debugging"><img src="https://agentmods.dev/badge/skills/iamraven-tw/learn-gas/google-apps-script-debugging.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.00093 | $0.01228 |
| Opus 5.5 | $0.00037 | $0.00491 |
| Sonnet 5.5 | $0.00019 | $0.00246 |
| Haiku 4.5 | $0.00009 | $0.00123 |
Grade A, and why
google-apps-script-debugging 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.
What it actually says
Google Apps Script 除錯
責任
本技能負責所有 Apps Script 教學與實際專案的重現、證據蒐集、錯誤分類、最小修正、回歸測試及遠端驗證。若錯誤屬於 Google Docs 固定版面、字體或分頁，使用 google-docs-layout 的版面基線與驗收規則判斷正確結果。
執行順序
- 先由
google-apps-script-project-development執行共用的首次使用環境關卡。即使使用者第一次就是要求除錯，也不得略過；先保存現有錯誤證據，再進行唯讀健檢，缺少工具時才補齊。 - 完整讀取並遵循初學者術語規則與 全域除錯工作流程。
- 讀取現有程式、文件與繁體中文紀錄檔(Log)，用簡短白話重述使用者希望製作的完整業務流程；取得使用者確認後，才把它當成除錯的正確預期。
- 確認預期結果、實際結果、執行入口、函式、時間、時區、執行身分及最近已知正常版本。
- 修改前保護 Git 與本機／遠端狀態，不覆蓋使用者既有變更。
- 先重現，優先使用既有「執行記錄」或「執行項目」還原實際流程，一次驗證一個假設。
- 建立最小失敗案例，完成最小修正並補回歸測試。
- 本機驗證通過後建立 Git commit；需要
clasp push、觸發器或部署時，轉由google-apps-script-project-development顯示摘要並取得確認。
強制原則
- 不把「請使用者自己改程式」當成除錯方式。
- 不因權限錯誤直接加入最大 OAuth scopes。
- 不因同步錯誤使用強制推送。
- 向使用者說明錯誤證據時，先用白話解釋用途，再使用「中文名稱(English)」；固定稱為「紀錄檔(Log)」，不得只使用英文術語或縮寫。
- 除錯流程需要再次同步遠端程式時，若先前尚未解釋，先說明它是把本機已修正並通過測試的程式與資訊清單同步到指定 Apps Script 專案，不等於執行程式、寄信、建立觸發器或部署；說明後稱為「推送到Apps Script(clasp push)」，不得只要求使用者確認英文命令。
- 不吞掉例外或永遠回傳成功。
- 每次除錯都要先重述完整業務邏輯並取得使用者確認；不得只根據目前程式推測需求。
- 優先使用專案原有的繁體中文紀錄檔(Log)判斷實際執行路徑。紀錄檔(Log)已足夠時不加入多餘訊息；不足時只補能驗證目前假設的最小診斷紀錄檔(Log)。
- 紀錄檔(Log)必須有繁體中文脈絡、失敗步驟與下一個檢查方向。
- 紀錄檔(Log)、測試、錯誤畫面與 Git 不得包含密碼、Token、OAuth 憑證、私人 ID、完整郵件或不必要個資。
- 除錯時只要要求使用者開啟、切換或操作任何網頁，就必須在同一則指示中提供已核對且可點擊的目標連結；尚未取得或無法核對連結時，先取得並核對，不要求使用者自行尋找頁面。
- 修正後至少重跑原失敗案例、正常案例、錯誤案例與重複執行案例。
- 觸發器、Web App 與 Webhook 必須核對實際執行項目與 deployment，不只看編輯器中的最新程式。
完成標準
只有使用者已確認完整業務邏輯、根因可說明、原失敗案例與回歸測試通過、中文紀錄檔(Log)足以診斷、暫時診斷紀錄檔(Log)已清理、權限沒有不必要擴張、Git 版本已建立，而且需要的遠端結果已查驗時，才能宣布完成。
使用者新增除錯、紀錄檔(Log)、測試或安全規則時，若沒有明確限定專案，預設更新為所有 Apps Script 專案共用規則。
What ships with it
2 files 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 First seen · 44 lines · 93 tokens per session scan A 3b6083222b21
google-apps-script-debugging is a skill published in the GitHub repository iamraven-tw/Learn-GAS (24 stars, last pushed 2mo ago), licensed MIT. It adds 93 tokens to every session and 1,228 once invoked, about $0.0004 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-30.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
cwv-optimizer
Diagnose and fix Core Web Vitals issues on AEM Edge Delivery Services pages. Goes deeper than generic CWV advice by understanding EDS-specific performance patterns including the 100KB LCP budget, E-L-D loading phases, block rendering behavior, and third-party script impact. Produces specific fixes for LCP, CLS, and…
incident-response-incident-response
Coordinate production incident triage, mitigation, investigation, recovery, and follow-up. Use when responding to outages or other incidents that require structured operational coordination.
ci-fixer
CI failures - read error, minimal fix, verify.