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 commands/babarot/gh-infra/plangit clone --depth 1 https://github.com/babarot/gh-infraWrote 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/commands/babarot/gh-infra/plan)<a href="https://agentmods.dev/commands/babarot/gh-infra/plan"><img src="https://agentmods.dev/badge/commands/babarot/gh-infra/plan.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.00000 | $0.00398 |
| Opus 5 | $0.00000 | $0.00199 |
| Sonnet 5 | $0.00000 | $0.00080 |
| Haiku 4.5 | $0.00000 | $0.00040 |
Grade A, and why
plan 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 4d 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.
What it actually says
Show diff between YAML and current GitHub state. No mutations are made.
gh infra plan [path...]
Path
One or more paths can be given. When multiple paths are provided, manifests from all paths are collected and planned together.
| Argument | Example | Behavior |
|---|---|---|
(none) or . |
gh infra plan |
All *.yaml / *.yml in the current directory |
| File | gh infra plan repos/my-cli.yaml |
That file only |
| Directory | gh infra plan repos/ |
All *.yaml / *.yml directly under it (subdirectories are ignored) |
| Multiple | gh infra plan repos/ files/ |
Manifests from all listed paths combined |
Overlapping paths (e.g., . and ./repos/) are rejected to prevent duplicate processing.
YAML files that are not gh-infra manifests are silently skipped. Use --fail-on-unknown to treat them as errors.
Flags
| Flag | Description |
|---|---|
-r, --repo <owner/repo> |
Target a specific repository |
--ci |
Exit with code 1 if changes detected (useful for CI drift detection) |
--fail-on-unknown |
Error on YAML files with unknown Kind (default: silently skip) |
Examples
# Plan all YAML files in a directory
gh infra plan ./repos/
# Plan multiple directories at once
gh infra plan ./repos/ ./files/
# Plan a single file
gh infra plan ./repos/my-cli.yaml
# Plan a specific repository
gh infra plan ./repos/ --repo babarot/my-cli
# CI drift detection
gh infra plan ./repos/ --ci
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.
- 4d ago First seen · 54 lines · 0 tokens per session scan A 12a293c611de
plan is a command published in the GitHub repository babarot/gh-infra (134 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 398 tokens. 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-08-30.
Other commands, from other repositories
billing
This API allows you to query billing related objects.
object
Command "object" from scaleway/scaleway-cli, covering documentation for scw object, manage s3 buckets, create an s3 bucket, delete an s3 bucket and get information about an s3 bucket.
account
This API allows you to manage your Scaleway Projects.
feedback
Command "feedback" from scaleway/scaleway-cli, covering documentation for scw feedback, send a bug-report and send a feature request.
oss
Daily OSS contribution check - uses CLI with --json for structured data.
canvas_account-content-migrations_get
Command "canvas_account-content-migrations_get" from jjuanrivvera/canvas-cli, covering canvas account-content-migrations get, options, options inherited from parent commands and see also.