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 inspect-repositorygit 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/inspect-repository)<a href="https://agentmods.dev/skills/gke-labs/kube-agents/inspect-repository"><img src="https://agentmods.dev/badge/skills/gke-labs/kube-agents/inspect-repository/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/inspect-repository"><img src="https://agentmods.dev/badge/skills/gke-labs/kube-agents/inspect-repository.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00065 | $0.01374 |
| Opus 5.5 | $0.00026 | $0.00550 |
| Sonnet 5.5 | $0.00013 | $0.00275 |
| Haiku 4.5 | $0.00006 | $0.00137 |
Grade A, and why
inspect-repository 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 11d 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.
How it starts
The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
inspect-repository - Read a repository this pod has no checkout of
This pod has no git of its own and no .git anywhere it can write. To read
somebody else's code, ask the credential broker to clone it and pull the file
content back. What lands locally is source without a repository around it: files
you can open, grep and reason about, and no .git/config for anything to
execute out of.
The script is /opt/data/profiles/platform/skills/inspect-repository/scripts/inspect_repository.py. Every subcommand prints one JSON
object on stdout.
When to Use
- Answering a question about code you do not have. "How does upstream implement this controller?", "which release added this flag?"
- Reading a dependency or an upstream project named in an issue, a design doc, or a user's question.
- Reading the GitOps repository for context when you are not editing it.
When NOT to Use
- Changing a repository. Use submit-suggestion (a pull request against the GitOps repo) or fleet-audit (fixes for its own findings). This skill opens read-only workspaces and the broker refuses to commit from one.
- Reading a file the GitOps workflow already handed you.
fleet-auditgives you a leased clone andsubmit-suggestionpreparegives you the copy it cloned; read theirs rather than opening a second view of the same repository.
Two shapes, and which to pick
Copy the tree when the repository is small enough to read on disk:
python3 /opt/data/profiles/platform/skills/inspect-repository/scripts/inspect_repository.py clone --repo kubernetes-sigs/kustomize --depth 1
Copies into /opt/data/scratch/repos/<owner>__<name> unless --into names
somewhere else, and prints written, bytes, skipped, stopped,
complete and, in content mode, sha, the commit the copy was taken from.
Narrow with --prefix api when only part of it matters.
Search first, take what it names when the repository is large — which is most of them:
What ships with it
2 files 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.
- 11d ago Changed d4dc248c4077
- 19d ago Changed · +12 tokens per session 548a3f1f1c69
- 29d ago Changed · +2 lines 6df303b47d9c
- 1mo ago Changed · +5 lines f6faac9e5ad6
- 1mo ago First seen · 96 lines · 53 tokens per session scan A 289be8f9d8d3
inspect-repository is a skill published in the GitHub repository gke-labs/kube-agents (116 stars, last pushed today), licensed Apache-2.0. It adds 65 tokens to every session and 1,374 once invoked, about $0.0003 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-06.
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.