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 gke-labs/kube-agents --skill submit-suggestiongit clone --depth 1 https://github.com/gke-labs/kube-agentsWrote 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/gke-labs/kube-agents/submit-suggestion)<a href="https://agentmods.dev/skills/gke-labs/kube-agents/submit-suggestion"><img src="https://agentmods.dev/badge/skills/gke-labs/kube-agents/submit-suggestion/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/gke-labs/kube-agents/submit-suggestion"><img src="https://agentmods.dev/badge/skills/gke-labs/kube-agents/submit-suggestion.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 25 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00091 | $0.07837 |
| Opus 5.5 | $0.00036 | $0.03135 |
| Sonnet 5.5 | $0.00018 | $0.01567 |
| Haiku 4.5 | $0.00009 | $0.00784 |
Grade A, and why
submit-suggestion 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.
How it starts
The opening of the file, as written. The whole thing — 543 lines — stays where its author put it; the contents beside it link to each section on GitHub.
submit-suggestion - Secure GitOps Pull Request Orchestrator
This skill equips the Platform Agent to propose declarative file updates, GKE infrastructure adjustments, or configuration changes securely by committing local repository changes and submitting pull requests (PRs; merge requests on GitLab) for human review. The repository is named as owner/name on github.com, <host>/owner/name on a GitHub Enterprise Server, or <host>/<path> — gitlab.com/<group>/<subgroup>/<project> — for one on another forge, exactly as it appears in the managed repository list.
When to Use
- Declarative File Provisioning: Triggered when new GKE manifests or configs are requested.
- Configuration Upgrades: Triggered when upgrading version configurations, security patches, or network policies.
- Governance Policy Syncs: Triggered when compliance playbooks or settings require updates.
- Any change in the GitOps repository reaches review through this skill, but a Terraform, Config Connector or Helm-chart change is written by its authoring skill first (Step 2's table).
- Deletions: Triggered when someone asks to delete a resource. See Deleting a resource before Step 1: a declared object is removed in a pull request, anything else is a stated stop.
Crucially, you are strictly forbidden from executing direct, manual mutations. All changes must flow through a secure PR path — this skill, or the fleet-audit skill for fixes of its findings (below).
When NOT to Use
- Answering a request that asked for a diagnosis, not a change. "Investigate
and report the root cause", "why is this crashlooping", "what would you
change" are questions; their answer is the finding and the proposed manifest
in the reply, marked as a recommendation. Open the pull request only when the
request asks for one, or for the change to be submitted or fixed;
SOUL.md§3, item 3 draws the line, and the unattended case isfleet-audit's own promotion, whichfinishdoes on a scheduled run, never this skill. A pull request nobody asked for is a write on their repository they now have to triage. - Fixing a fleet-audit finding. The bullets above match audit fixes too — a
security patch, a policy update — which is exactly why this warning exists. If
the change addresses a fleet-audit finding (it carries a finding id, or an
[audit]ledger issue lists that exact deviation as a finding), the fleet-audit skill opens that pull request itself, through itsremediatesubcommand — see/opt/data/profiles/platform/skills/fleet-audit/references/remediation.mdfor the invocation. That path keys the branch on the files the fix touches, so a rerun cannot open a duplicate: a live PR is left untouched rather than force-pushed over, and one the harness withdrew as stale is re-proposed on the same branch. It applies the audit labels, links the ledger, and closes the PR when the finding stops reproducing. A PR opened through this skill gets none of that — nothing dedupes it and nothing ever closes it, which is how one workload's findings once became five near-duplicate PRs.
What ships with it
1 file 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.
- yesterday Changed · +11 lines 20b6430d0b00
- 4d ago Changed · +37 lines dbed09b86edb
- 5d ago Changed · +92 lines · +12 tokens per session e57b8e0ff9a9
- 6d ago Changed e57f0ddb7656
- 7d ago Changed · +55 lines · +27 tokens per session b3d614c6a39e
- 8d ago Changed f251d41fe0d6
- 11d ago Changed cf5d82ae5a12
- 12d ago Changed 40e6192f8229
- 19d ago Changed · +1 tokens per session ebb84bab26ec
- 20d ago First seen · 348 lines · 51 tokens per session scan A d67c560a5b76
submit-suggestion is a skill published in the GitHub repository gke-labs/kube-agents (116 stars, last pushed today), licensed Apache-2.0. It adds 91 tokens to every session and 7,837 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-09-03.
Other skills, from other repositories
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.