Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/katalalab/katala-osnpx agentmods add skills/katalalab/katala-os/repo-initWrote 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/katalalab/katala-os/repo-init)<a href="https://agentmods.dev/skills/katalalab/katala-os/repo-init"><img src="https://agentmods.dev/badge/skills/katalalab/katala-os/repo-init/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/katalalab/katala-os/repo-init"><img src="https://agentmods.dev/badge/skills/katalalab/katala-os/repo-init.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.00103 | $0.01451 |
| Opus 5 | $0.00051 | $0.00726 |
| Sonnet 5 | $0.00021 | $0.00290 |
| Haiku 4.5 | $0.00010 | $0.00145 |
Grade A, and why
repo-init 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 10d 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
repo-init — Katala OS repo scaffolding
This Skill scaffolds a new (or existing) repo with the agent-context style:
AGENTS.md— repo-specific delta, inherits global baseline (~/work/agent-context/AGENTS.MD) and constitution..gitattributes— LF for*.md/*.json/*.sh/*.py/*.tsetc., CRLF for*.ps1/*.cmd. Stops Windowsautocrlf=truefrom breaking hashes..gitignore— secrets, keys, backups, shell history, OS cruft, generic build/cache.NEEDS_REVIEW.md— multi-agent dissent log; append-only, operator ratifies.- Shared pre-commit hook wired via
git config core.hooksPath ~/work/agent-context/hooks. - Optional:
CONSTITUTION.md+manifest.lock.json+scripts/verify.shfor repos that need hash-locked artifacts.
When to use this Skill
Match against operator intent like:
- "新リポを Katala 標準で立てて"
- "scaffold an agent-context repo"
- "このリポに AGENTS.md 一式を足したい"
- "hash-locked な constitution も付けて"
- "set up the shared pre-commit hook here"
Do not use for:
- Editing the global baseline (
~/work/agent-context/AGENTS.MD) — that's a direct edit, not a scaffold. - One-off
.gitignoreadditions in an existing repo — just edit. - Pure GitHub repo creation (use
gh repo createdirectly).
How to invoke
macOS / Linux
~/work/agent-context/scripts/init-repo.sh <target-dir> \
--name <repo-name> \
--description "<one line>" \
--operator <name> \
[--with-constitution] \
[--no-hooks-path] \
[--dry-run]
Windows (PowerShell)
& "$env:USERPROFILE\work\agent-context\scripts\init-repo.ps1" `
-Target <target-dir> `
-RepoName <repo-name> `
-Description "<one line>" `
[-WithConstitution] `
[-NoHooksPath] `
[-DryRun]
Both are idempotent: existing files are backed up to *.bak.<yyyyMMdd-HHmmss> before being overwritten. Backups are pruned automatically when (a) a newer same-base backup exists AND (b) the older one is >30 days old. This matches the Hard Rule "every backup declares a retention rule and a matching prune step."
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.
- 10d ago First seen · 122 lines · 103 tokens per session scan A 452ba60ba5e7
repo-init is a skill published in the GitHub repository katalalab/katala-os (2 stars, last pushed 11d ago), licensed MIT. It adds 103 tokens to every session and 1,451 once invoked, about $0.0005 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-31.
Other skills, from other repositories
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.
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…
nvca-chart-release
Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.