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 ZaneL1u/cloud-cli-proxy --skill gsd-docs-updategit clone --depth 1 https://github.com/ZaneL1u/cloud-cli-proxyWrote 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/zanel1u/cloud-cli-proxy/gsd-docs-update)<a href="https://agentmods.dev/skills/zanel1u/cloud-cli-proxy/gsd-docs-update"><img src="https://agentmods.dev/badge/skills/zanel1u/cloud-cli-proxy/gsd-docs-update/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/zanel1u/cloud-cli-proxy/gsd-docs-update"><img src="https://agentmods.dev/badge/skills/zanel1u/cloud-cli-proxy/gsd-docs-update.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.00016 | $0.00726 |
| Opus 5 | $0.00008 | $0.00363 |
| Sonnet 5 | $0.00003 | $0.00145 |
| Haiku 4.5 | $0.00002 | $0.00073 |
Grade A, and why
gsd-docs-update 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 64 lines · 16 tokens per session scan A 64a389ac2acb
gsd-docs-update is a skill published in the GitHub repository ZaneL1u/cloud-cli-proxy (57 stars, last pushed 1mo ago), with no licence file. It adds 16 tokens to every session and 726 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
pm
Project Manager skill. One orchestrator session drives eight subagent roles -- planner, plan-reviewer, doer, reviewer, deployer, integ-test-runner, ci-watcher, harvester -- through cycles of Plan, Develop, Test, and Harvest across one or more parallel tracks in isolated git worktrees, running each task on a…
fleet-sprint-cli
How to launch and supervise apra-fleet's autonomous sprint workflow from the CLI (apra-fleet workflow fleet-sprint) -- the --issue/--members/--branch/--base flag contract, the preconditions to check first, how to launch it as a detached process, and how to watch it via its dashboard. Trigger before running apra-fleet…
auto-sprint-args
How to construct and pass correct arguments to the auto-sprint workflow -- the required issues+branch fields, optional goal/maxcycles/basebranch/requirementsFile, JSON-object (not string) shape, and common launch mistakes. Trigger when preparing to launch or invoke auto-sprint.
write-ticket-description
Voice guide for writing issue/ticket/task/epic descriptions. Use this skill for ALL issue creation — GitHub issues, Jira tasks, Monday tasks, Linear tasks, and epics. Contains section structure, voice rules, and anti-patterns. Never write ticket descriptions without invoking this skill first.
use-trekker
Full reference for the trekker task management workflow. Use when working with trekker issues, planning multi-step work, or managing task lifecycle.
use-beads
Full reference for the beads task management workflow. Use when working with beads issues, planning multi-step work, or managing task lifecycle.