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 PBNZ/repo-kit --skill repo-standardgit clone --depth 1 https://github.com/PBNZ/repo-kitWrote 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/pbnz/repo-kit/repo-standard)<a href="https://agentmods.dev/skills/pbnz/repo-kit/repo-standard"><img src="https://agentmods.dev/badge/skills/pbnz/repo-kit/repo-standard/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/pbnz/repo-kit/repo-standard"><img src="https://agentmods.dev/badge/skills/pbnz/repo-kit/repo-standard.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.00061 | $0.01044 |
| Opus 5.5 | $0.00024 | $0.00418 |
| Sonnet 5.5 | $0.00012 | $0.00209 |
| Haiku 4.5 | $0.00006 | $0.00104 |
Grade A, and why
repo-standard 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 2mo 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
repo-standard — conventions for a RepoKit repo
You are working in a repository scaffolded to the RepoKit standard. This skill is the router to
the conventions. The full references live next to this skill; read the one you need from this
skill's base directory (you were given Base directory for this skill: <ABS> at load — read
<ABS>/standard/<doc>.md):
standard/the-standard.md— the type × tier model, per-tier file lists, the where-things-live map, the promotion path, and the do/don't list.standard/where-things-go.md— a placement guide: "I have X — where does it go, how do I create the place if it doesn't exist yet, and on what convention?" Use this for any "where does this go" question.standard/commit-conventions.md— Conventional Commits, SemVer, Keep a Changelog, and how release-please fits in at the Published tier.standard/pre-commit-checklist.md— run through this before every commit.standard/pre-pr-checklist.md— run through this before opening a PR.standard/session-end-checklist.md— run through this before ending a working session: unmerged-branch decisions, one-concern commits, resume-state currency.standard/testing-matrix.md— what to test, per repo type.standard/doc-style.md— deterministic formatting rules for docs (one table style, ISO dates, fixed status words) so many sessions/models write like one author.standard/living-docs.md— the living-docs add-on:docs/STATE.jsonas the single source for volatile facts, state blocks,scripts/check-docs.ps1, and the current-state-only runbook rules.standard/labels.md— the layered issue/PR label scheme: GitHub defaults as the base, opt-in namespaces (area:,agent:,campaign:), workflow-verdict labels, and the bootstrap commands.standard/agent-collaboration.md— humans + agents on a shared board: the real-time board rule, the pickup/handoff loop, closing-force gestures, agent-output signatures, and the session preflight.standard/fleet.md— multi-repo projects (hub-and-spoke): the hub as router, the scope test, sibling clones, three-line spoke inheritance, and docs-move-with-stub.standard/org-migration-checklist.md— moving repos into an org / rebuilding a project board: the six platform landmines as symptom → cause → fix, with doc citations.
What ships with it
13 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.
- standard/agent-collaboration.md 6.7 KB
- standard/commit-conventions.md 5.9 KB
- standard/doc-style.md 4.0 KB
- standard/fleet.md 3.2 KB
- standard/labels.md 2.6 KB
- standard/living-docs.md 7.0 KB
- standard/org-migration-checklist.md 4.5 KB
- standard/pre-commit-checklist.md 1.7 KB
- standard/pre-pr-checklist.md 1.8 KB
- standard/session-end-checklist.md 2.2 KB
- standard/testing-matrix.md 1.7 KB
- standard/the-standard.md 16 KB
- standard/where-things-go.md 4.0 KB
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.
- 2mo ago First seen · 59 lines · 61 tokens per session scan A 5f8205124153
repo-standard is a skill published in the GitHub repository PBNZ/repo-kit (1 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 61 tokens to every session and 1,044 once invoked, about $0.0002 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-08-31.
Other skills, from other repositories
github-pr-creation
Creates GitHub Pull Requests with automated validation and task tracking. Use when user wants to create PR, open pull request, submit for review, or check if ready for PR. Analyzes commits, validates task completion, generates Conventional Commits title and description, suggests labels. NOTE - for merging existing…
github-pr-merge
Merges GitHub Pull Requests after validating pre-merge checklist. Use when user wants to merge PR, close PR, finalize PR, complete merge, approve and merge, or execute merge. Runs pre-merge validation (tests, lint, CI, comments), confirms with user, merges with proper format, handles post-merge cleanup.
git-commit
Creates git commits following Conventional Commits format with type/scope/subject. Use when user wants to commit changes, create commit, save work, or stage and commit. Enforces project-specific conventions from CLAUDE.md.
ship-item
Ship a plan/todo item in a documentation-led repo — run the verify gate, integrate per the repo's model (fast-forward or PR), git mv todo→done with a shipped footer, advance the owning ADR(s) to Implemented, and regenerate INDEX. Use when the user says "ship this", "complete the plan item", "mark done", or "close out…
workspace-setup
Create or deliberately adopt a multi-repository Docflow WORKSPACE with a registry and portable memory. Use for workspace-setup or establishing a workspace home. NOT for bootstrapping a member repository, orientation, planning an outcome or executing assignments.
workspace-sync
Reconcile returned WORKSPACE receipts and maintain delivery observations from checked native evidence, observing member pull requests, merges, required checks, plan todo-to-done moves and branch heads, then refreshing INDEX. Use for workspace-sync or updating a workspace after native work, whether or not this…