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 tnisizawa/clasp-skill --skill clasp-skillgit clone --depth 1 https://github.com/tnisizawa/clasp-skillWrote 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/tnisizawa/clasp-skill/clasp-skill)<a href="https://agentmods.dev/skills/tnisizawa/clasp-skill/clasp-skill"><img src="https://agentmods.dev/badge/skills/tnisizawa/clasp-skill/clasp-skill/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/tnisizawa/clasp-skill/clasp-skill"><img src="https://agentmods.dev/badge/skills/tnisizawa/clasp-skill/clasp-skill.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.00067 | $0.02155 |
| Opus 5 | $0.00034 | $0.01077 |
| Sonnet 5 | $0.00013 | $0.00431 |
| Haiku 4.5 | $0.00007 | $0.00215 |
Grade A, and why
clasp scanned grade A with 1 finding 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 12d 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
node -e "const{execSync}=require('child_process');try{execSync('clasp push --force',{stdio:'inherit'})}catch(e){process.exit(e.status||1)}" || push_status=$? How it starts
The opening of the file, as written. The whole thing — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Clasp（GAS プロジェクト管理）
Google Apps Script を CLI から操作するスキル。
リファレンス索引
用途に応じて該当ファイルを Read する。
| やりたいこと | 参照先 |
|---|---|
| コードをプッシュしたい | このファイル「push フロー」節（下） |
初めて使う・インストール・clasp login |
references/setup.md |
| GASプロジェクトと接続する（初回接続・ケースA/B 判定） | references/init.md |
Web エディタの変更を取り込む（clasp pull・日常同期） |
references/pull.md |
| マルチ環境（開発/リリース）の配布版 push | references/deploy-dist.md |
| デプロイ・ロールバック・バージョン戻し（ライブラリ・ウェブアプリ） | references/deploy.md |
| GAS ウェブアプリの iframe 問題・画像表示 | references/webapp.md |
clasp logs で実行ログを取得 |
references/logs.md |
push フロー（最頻出）
前提
.clasp.jsonが存在することclaspがインストールされていること
1. appsscript.json の確認・作成
なければ作成。既存ならスコープの過不足をチェック。
{
"timeZone": "Asia/Tokyo",
"dependencies": {},
"exceptionLogging": "STACKDRIVER",
"runtimeVersion": "V8",
"oauthScopes": [
"https://www.googleapis.com/auth/spreadsheets"
]
}
プロジェクトに必要なスコープのみ追加する。 実際には https://www.googleapis.com/auth/ プレフィックスを付ける。
よく使う権限一覧:
| 権限 | 用途 |
|---|---|
gmail.readonly |
Gmail の読み取り |
gmail.send |
メール送信 |
drive |
Google Drive 操作 |
documents |
Google Docs 操作 |
spreadsheets |
スプレッドシート操作 |
forms |
Google Forms の作成・編集 |
calendar |
Google Calendar 操作 |
script.scriptapp |
トリガー設定 |
script.external_request |
UrlFetchApp（外部 API 呼び出し） |
script.container.ui |
UI ダイアログ・サイドバー表示 |
2. .clasp.json の確認
ls .clasp*.json
複数ファイルがある場合（例: .clasp.dev.json, .clasp.prod.json）:
- ユーザーにどの環境へ push するか確認する
- 一時的に選択された設定ファイルを
.clasp.jsonにコピーし、push 後に元へ戻す .clasp.jsonを永続的に切り替える場合は、その意図をユーザーに確認してから行う
CLASP_BAK=".clasp.json.bak.$(date +%Y%m%d%H%M%S)"
node -e "const fs=require('fs');fs.existsSync('.clasp.json')&&fs.copyFileSync('.clasp.json',process.argv[1])" "$CLASP_BAK"
printf '%s\n' "$CLASP_BAK" > .clasp.json.bak-path
node -e "const fs=require('fs');fs.copyFileSync(process.argv[1],'.clasp.json')" ".clasp.<env>.json"
2.5. .claspignore の確認（push 対象の除外）
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.
- 12d ago First seen · 161 lines · 67 tokens per session scan A 2bf12f57438a
clasp is a skill published in the GitHub repository tnisizawa/clasp-skill (4 stars, last pushed 3mo ago), licensed MIT. It adds 67 tokens to every session and 2,155 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
deploy-site
Deploys an existing Power Pages code site to a Power Pages environment using PAC CLI. Handles tooling verification, authentication, environment confirmation, building, and uploading. Use when the user wants to deploy, upload, or publish their code site.
activate-site
Activates and provisions a Power Pages website in a Power Platform environment via the Power Platform REST API. Use when the user wants to activate, provision, turn on, or enable a Power Pages website or portal.
deploy
Builds and deploys a Power Apps code app to Power Platform. Use when deploying changes, redeploying an existing app, or pushing updates.
domain-monitoring
AI-powered domain and SSL certificate monitoring skill. Designs domain health checks, SSL expiry alerts, DNS anomaly detection, and security rating assessments for e-commerce websites.
public-status-page
AI-powered public status page design skill for e-commerce businesses. Creates status page architecture, incident communication templates, subscriber notification systems, and uptime reporting frameworks.
deploy
Render Quarto .qmd slides to HTML and sync to docs/ for GitHub Pages. Use when user says "deploy", "publish the slides", "ship to pages", "push the lecture live", "render and publish", or after Quarto edits that need to go public. NOT for local Quarto render only — use quarto render directly for that.