Borrowing it
Nothing to install: this file belongs to williamzujkowski/standards. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/williamzujkowski/standards/master/.claude/commands/github/repo-analyze.mdgit clone --depth 1 https://github.com/williamzujkowski/standardsWrote 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/williamzujkowski/standards/repo-analyze)<a href="https://agentmods.dev/commands/williamzujkowski/standards/repo-analyze"><img src="https://agentmods.dev/badge/commands/williamzujkowski/standards/repo-analyze/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/commands/williamzujkowski/standards/repo-analyze"><img src="https://agentmods.dev/badge/commands/williamzujkowski/standards/repo-analyze.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.00000 | $0.00157 |
| Opus 5.5 | $0.00000 | $0.00063 |
| Sonnet 5.5 | $0.00000 | $0.00031 |
| Haiku 4.5 | $0.00000 | $0.00016 |
Grade A, and why
repo-analyze 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 2d 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.
This is a copy
100% identical to repo-analyze — 3 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
repo-analyze
Deep analysis of GitHub repository with AI insights.
Usage
npx claude-flow github repo-analyze [options]
Options
--repository <owner/repo>- Repository to analyze--deep- Enable deep analysis--include <areas>- Include specific areas (issues, prs, code, commits)
Examples
# Basic analysis
npx claude-flow github repo-analyze --repository myorg/myrepo
# Deep analysis
npx claude-flow github repo-analyze --repository myorg/myrepo --deep
# Specific areas
npx claude-flow github repo-analyze --repository myorg/myrepo --include issues,prs
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.
- 2d ago First seen · 29 lines · 0 tokens per session scan A 67cc719ed833
repo-analyze is a command published in the GitHub repository williamzujkowski/standards (18 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 157 tokens. A static security scan graded it A with 0 findings. It is 100% identical to repo-analyze, differing in 3 lines, and is treated as a copy.
Other commands, from other repositories
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
git-workflow
Run review, tests, and commit steps, then prepare a pull request.
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
session-report
Capture what changed this session and why, scoped to the current branch. Read by ship verbs when synthesizing the commit message; deleted after a successful commit.
feat
Quick feature commit. Use for new feature, add feature, implement, create new.
close-track
Close a completed track — run quality gate, update conductor state, commit, and optionally handle the git branch.