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/applygit 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/apply)<a href="https://agentmods.dev/commands/babarot/gh-infra/apply"><img src="https://agentmods.dev/badge/commands/babarot/gh-infra/apply.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.00651 |
| Opus 5 | $0.00000 | $0.00326 |
| Sonnet 5 | $0.00000 | $0.00130 |
| Haiku 4.5 | $0.00000 | $0.00065 |
Grade A, and why
apply 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.
How it starts
The opening of the file, as written. The whole thing — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Apply changes to GitHub. By default, requires interactive confirmation before proceeding.
gh infra apply [path...]
Path
One or more paths can be given. When multiple paths are provided, manifests from all paths are collected and applied together.
| Argument | Example | Behavior |
|---|---|---|
(none) or . |
gh infra apply |
All *.yaml / *.yml in the current directory |
| File | gh infra apply repos/my-cli.yaml |
That file only |
| Directory | gh infra apply repos/ |
All *.yaml / *.yml directly under it (subdirectories are ignored) |
| Multiple | gh infra apply 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 |
--auto-approve |
Skip confirmation prompt |
--force-secrets |
Re-set all secrets (even existing ones) |
--fail-on-unknown |
Error on YAML files with unknown Kind (default: silently skip) |
Interactive Diff Viewer
After the plan is displayed, the confirmation prompt offers three options:
> Do you want to apply these changes? (y)es / (n)o / (d)iff
Press d to open a full-screen diff viewer before deciding:
| Key | Action |
|---|---|
↑/↓ or j/k |
Select file |
Tab |
Toggle apply/skip for the selected file |
d/u |
Scroll diff pane |
q/Esc |
Return to confirmation |
Each file defaults to apply. Use Tab to toggle a file to skip if you want to exclude it from the current run. Skipped files are shown dimmed in the viewer. The YAML manifest is not modified — this is a runtime-only decision.
When you return to the confirmation prompt, any skipped files are shown as a summary:
Skipped files (this run only):
go.mod
> Do you want to apply these changes? (y)es / (n)o / (d)iff
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 · 83 lines · 0 tokens per session scan A a075d36a5995
apply 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 651 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
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.
nyann:diff-profile
Compare two nyann profiles side-by-side and show what changes between them: hooks, branching, CI, documentation, extras, governance. Useful before switching profiles to understand the impact.