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 babarot/gh-infra --skill file-manifestgit 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/skills/babarot/gh-infra/file-manifest)<a href="https://agentmods.dev/skills/babarot/gh-infra/file-manifest"><img src="https://agentmods.dev/badge/skills/babarot/gh-infra/file-manifest/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/babarot/gh-infra/file-manifest"><img src="https://agentmods.dev/badge/skills/babarot/gh-infra/file-manifest.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.00058 | $0.00764 |
| Opus 5 | $0.00029 | $0.00382 |
| Sonnet 5 | $0.00012 | $0.00153 |
| Haiku 4.5 | $0.00006 | $0.00076 |
Grade A, and why
file-manifest 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
File Manifest Reference
Use this skill for file-distribution manifests. Keep the main body small and open references only when the request needs them.
Core Rules
Fileis parsed as a one-repoFileSetinternally, but you still author the simpler shape- Each file entry requires
pathand exactly one ofcontentorsource viadefaults topushreconciledefaults toadditivepatchesare applied after template expansion
File
apiVersion: gh-infra/v1
kind: File
metadata:
owner: my-org
name: my-repo
spec:
files:
- path: .github/CODEOWNERS
content: |
* @username
- path: LICENSE
source: ./templates/LICENSE
via: push
commit_message: "ci: sync managed files"
Key fields:
files: requiredvia:pushorpull_requestcommit_message,branch,pr_title,pr_body: delivery controlsfiles[].vars: template variablesfiles[].patches: unified diff patchesfiles[].reconcile:additive,authoritative,create_only
Read these references as needed:
- Sources and templating: references/sources-and-templating.md
- Reconcile and delivery: references/reconcile-and-delivery.md
- Patches: references/patches.md
- FileSet and overrides: references/fileset.md
- Import-into behavior: use the dedicated
import-intoskill
FileSet
Use FileSet to distribute shared files to many repositories.
apiVersion: gh-infra/v1
kind: FileSet
metadata:
owner: my-org # no "name" field
spec:
repositories:
- gomi # simple string
- enhancd
- name: gh-infra # struct with overrides
overrides:
- path: .github/CODEOWNERS
content: |
* @username @co-maintainer
files:
- path: .github/CODEOWNERS
content: |
* @username
- path: LICENSE
source: ./templates/LICENSE
via: push
What ships with it
4 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 First seen · 110 lines · 58 tokens per session scan A e98af0f43c3b
file-manifest is a skill published in the GitHub repository babarot/gh-infra (134 stars, last pushed 3mo ago), licensed MIT. It adds 58 tokens to every session and 764 once invoked, about $0.0003 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-08-30.
Other skills, from other repositories
gh-attach
Uploads a local file (screenshot, image, PDF, zip, video) to GitHub user-attachments, downloads GitHub user-attachments, and embeds local files in a PR, issue, or comment. Use when asked to "attach a screenshot to the PR", "add an image to the issue", "embed before/after screenshots", "attach this file", or "download…
pkup-enchant
Enrich an existing PKUP report directory — group commits into tasks, filter out non-creative groups, and write Polish descriptions. Use when the user has already generated a PKUP report and wants to clean it up or add "Zaprojektowałem..." descriptions.
gh-stack
Manages stacked PRs and splits multi-part work into reviewable branches with gh-stack. Use for stack creation, viewing, edits, push, submit, sync, rebase, merge, or checkout; when asked to split or isolate work for review; whenever a user mentions a stack, branch layers, dependent PRs, or gh stack; or when a stack is…
github-operations
GitHub CLI operations for issues, PRs, milestones, and Projects v2. Covers gh commands, REST API patterns, and automation scripts. Use when managing GitHub issues, PRs, milestones, or Projects with gh.
vhs-e2e-gif
Record a test run, a TUI session, or any terminal command as a GIF with VHS and attach it to a GitHub PR as a release-hosted asset, never a repo commit. Use when asked to record an e2e run, demo a fix on a PR, attach a GIF or screen recording to a pull request, show a test passing visually, or produce a terminal…
check-linters-before-commit
Before any commit, run linters, vet, tests, and build verification; do not commit until checks pass.