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 Bilal140202/the-lord-of-the-skills --skill larry-kang__antigravity-agent-configgit clone --depth 1 https://github.com/Bilal140202/the-lord-of-the-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/bilal140202/the-lord-of-the-skills/larry-kang__antigravity-agent-config)<a href="https://agentmods.dev/skills/bilal140202/the-lord-of-the-skills/larry-kang__antigravity-agent-config"><img src="https://agentmods.dev/badge/skills/bilal140202/the-lord-of-the-skills/larry-kang__antigravity-agent-config/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/bilal140202/the-lord-of-the-skills/larry-kang__antigravity-agent-config"><img src="https://agentmods.dev/badge/skills/bilal140202/the-lord-of-the-skills/larry-kang__antigravity-agent-config.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.00021 | $0.00620 |
| Opus 5 | $0.00010 | $0.00310 |
| Sonnet 5 | $0.00004 | $0.00124 |
| Haiku 4.5 | $0.00002 | $0.00062 |
Grade A, and why
gas-ops 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.
What it actually says
GAS Ops Skill
此技能規範 Google Apps Script (GAS) 開發的標準流程，結合 clasp 工具與 GitHub Actions 實現自動化部屬與版本控制。
環境依賴 (Dependencies)
- Node.js & npm (系統環境)
- @google/clasp (全域安裝:
npm install -g @google/clasp) - GitHub Actions (用於自動化部屬)
標準開發流程 (Workflow)
1. 本地開發與同步
在本地進行開發後，通過 Git 提交代碼。若需從 GAS 網頁工作區同步回本地：
clasp pull
2. 自動化部屬 (GitHub Actions)
專案應配置 .github/workflows/deploy.yml，在推送到特定分支（如 master 或 main）時自動執行部屬。
- 機制: GitHub Action 會安裝
clasp並利用CLASPRC_JSON_BASE64秘密金鑰進行授權。 - 指令:
clasp push --force
3. 手動急修 (Manual Emergency Push)
僅在 CI/CD 失效且需緊急修復時使用：
clasp push
CI/CD 配置規範
認證金鑰處理
- 執行
clasp login獲取本地~/.clasprc.json。 - 將該檔案內容轉換為 Base64 字串：
[Convert]::ToBase64String([IO.File]::ReadAllBytes("$HOME\.clasprc.json")) - 將結果存入 GitHub Repository Secrets，名稱為
CLASPRC_JSON_BASE64。
最佳實踐 (Best Practices)
- GitHub 為單一真相來源: 始終信任 Git 上的代碼。避免在 GAS 網頁工作區直接修改代碼，除非是為了快速測試並隨即
clasp pull回本地。 - 自動化優先: 儘量透過
git push觸發 Action 進行部屬，確保部署紀錄與 Git Commit 關聯。 - 強制更新: 線上環境部屬建議使用
clasp push --force以避免文件版本衝突。
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 · 50 lines · 21 tokens per session scan A 598223ebeef3
gas-ops is a skill published in the GitHub repository Bilal140202/the-lord-of-the-skills (4 stars, last pushed 6d ago), licensed MIT. It adds 21 tokens to every session and 620 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-09-03.
Other skills, from other repositories
integrating-sast-into-github-actions-pipeline
This skill covers integrating Static Application Security Testing (SAST) tools—CodeQL and Semgrep—into GitHub Actions CI/CD pipelines. It addresses configuring automated code scanning on pull requests and pushes, tuning rules to reduce false positives, uploading SARIF results to GitHub Advanced Security, and…
integrating-dast-with-owasp-zap-in-pipeline
This skill covers integrating OWASP ZAP (Zed Attack Proxy) for Dynamic Application Security Testing in CI/CD pipelines. It addresses configuring baseline, full, and API scans against running applications, interpreting ZAP findings, tuning scan policies, and establishing DAST quality gates in GitHub Actions and GitLab…
performing-sca-dependency-scanning-with-snyk
This skill covers implementing Software Composition Analysis (SCA) using Snyk to detect vulnerable open-source dependencies in CI/CD pipelines. It addresses scanning package manifests and lockfiles, automated fix pull request generation, license compliance checking, continuous monitoring of deployed applications, and…
securing-github-actions-workflows
This skill covers hardening GitHub Actions workflows against supply chain attacks, credential theft, and privilege escalation. It addresses pinning actions to SHA digests, minimizing GITHUBTOKEN permissions, protecting secrets from exfiltration, preventing script injection in workflow expressions, and implementing…
implementing-code-signing-for-artifacts
This skill covers implementing code signing for build artifacts to ensure integrity and authenticity throughout the software supply chain. It addresses signing binaries, packages, and containers using GPG, Sigstore, and platform-specific signing tools, establishing trust chains, and verifying signatures in deployment…
supply-chain-attack-recon
External recon for software supply-chain attack surface — package-namespace squatting candidates, dependency-confusion vulnerabilities, GitHub Actions injection openings, container image registry exposure, SBOM mining, internal-package-name leakage, and CI/CD configuration exposure. Reconnaissance and identification…