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/fakoli/fakoli-plugins/gws-scriptnpx skills add fakoli/fakoli-plugins --skill gws-scriptgit clone --depth 1 https://github.com/fakoli/fakoli-pluginsWrote 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/fakoli/fakoli-plugins/gws-script)<a href="https://agentmods.dev/skills/fakoli/fakoli-plugins/gws-script"><img src="https://agentmods.dev/badge/skills/fakoli/fakoli-plugins/gws-script.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.00021 | $0.00521 |
| Opus 5 | $0.00010 | $0.00260 |
| Sonnet 5 | $0.00004 | $0.00104 |
| Haiku 4.5 | $0.00002 | $0.00052 |
Grade A, and why
gws-script 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.
What it actually says
gws script
Reference: See the
gws-sharedskill for auth, global flags, and security rules.
Deploy and manage Google Apps Script projects using the gws CLI.
Helper Command
+push — Upload local files to an Apps Script project
Replaces ALL files in the target Apps Script project with files from a local directory.
gws script +push --script SCRIPT_ID
gws script +push --script SCRIPT_ID --dir ./src
Supported file types: .gs, .js, .html, appsscript.json
Automatic behavior:
- Skips hidden files and
node_modules - Replaces the entire project content (not a merge)
Raw API Access
You can also use the Apps Script API directly:
# List script projects
gws script projects list
# Get project content
gws script projects getContent --params '{"scriptId": "SCRIPT_ID"}'
# Get project metadata
gws script projects get --params '{"scriptId": "SCRIPT_ID"}'
Examples
Deploy a script from current directory
# Check what files will be uploaded
ls *.gs *.html appsscript.json
# Push to the project
gws script +push --script 1BxTjDmEZcABxhVBmFLRfMXD4eHJB7k_g2r-example
Deploy from a specific directory
gws script +push --script SCRIPT_ID --dir ./apps-script-src
View current project content before pushing
gws script projects getContent --params '{"scriptId": "SCRIPT_ID"}'
Caution
+pushreplaces all files in the project — there is no merge or diff- Always verify the script ID before pushing
- Consider keeping a backup of the current project content:
gws script projects getContent --params '{"scriptId": "SCRIPT_ID"}' > backup.json
Tips
- Keep your Apps Script source files in a dedicated directory (e.g.,
./apps-script/) - Use version control (git) alongside
+pushfor change tracking - The
appsscript.jsonmanifest file controls runtime settings, scopes, and triggers
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.
- yesterday First seen · 82 lines · 21 tokens per session scan A ec8ee88160a9
gws-script is a skill published in the GitHub repository fakoli/fakoli-plugins (4 stars, last pushed 27d ago), licensed MIT. It adds 21 tokens to every session and 521 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
aws-cdk-knowledge-patch
Load this skill when changing, reviewing, debugging, or upgrading AWS CDK applications, construct libraries, CLI integrations, or synthesized CloudFormation templates.
deno-knowledge-patch
Use this skill when choosing current Deno runtime APIs, CLI options, configuration, dependency behavior, Node compatibility, or deployment workflows. Open the topic reference before changing a project because several commands, flags, APIs, and defaults changed more than once.
apache-flink-knowledge-patch
Use this skill when upgrading or operating Flink, writing DataStream or Table API jobs, changing SQL, implementing connectors, or diagnosing state, checkpoint, scheduling, and deployment behavior. Start with the quick checks, then open the topic reference that matches the work.
argo-cd-knowledge-patch
Use this skill when upgrading or configuring Argo CD, writing Applications or ApplicationSets, integrating repositories and Source Hydrator, operating the CLI or API, or updating security, health, and observability behavior. Start with the behavior changes below, then open the reference for the task at hand.
aws-sdk-knowledge-patch
Use this skill when upgrading an AWS SDK or CLI, changing a supported runtime, configuring shared SDK behavior, or implementing one of the service APIs in the reference index. Identify the language, SDK major version, runtime, service, and deployment environment before applying the guidance.
azure-knowledge-patch
Use this skill for Azure infrastructure, Azure CLI, Azure PowerShell, Terraform AzureRM or AzAPI, Bicep, identity SDK, Microsoft Entra, networking, compute, containers, data services, storage, Key Vault, governance, and service lifecycle work.