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 bryanweaver/claude-agent-kit --skill team-repo-statusgit clone --depth 1 https://github.com/bryanweaver/claude-agent-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/bryanweaver/claude-agent-kit/team-repo-status)<a href="https://agentmods.dev/skills/bryanweaver/claude-agent-kit/team-repo-status"><img src="https://agentmods.dev/badge/skills/bryanweaver/claude-agent-kit/team-repo-status/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/bryanweaver/claude-agent-kit/team-repo-status"><img src="https://agentmods.dev/badge/skills/bryanweaver/claude-agent-kit/team-repo-status.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.00020 | $0.00427 |
| Opus 5 | $0.00010 | $0.00214 |
| Sonnet 5 | $0.00004 | $0.00085 |
| Haiku 4.5 | $0.00002 | $0.00043 |
Grade A, and why
team-repo-status 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.
What it actually says
Repository Status Report
Generate a comprehensive status report for the current repository.
Focus area: $ARGUMENTS
Execution
Gather and analyze the following information:
1. Git Repository Status
Run these commands to gather git state:
git branch --show-current— current branchgit status --short— working tree statusgit branch -v— all branchesgit remote -v— remote infogit log --oneline -10 --graph --decorate— recent commits
2. Development Activity
Analyze recent development patterns:
git log --since="7 days ago" --name-only --pretty=format:— files changed recentlygit log --since="30 days ago" --pretty=format:"%an"— contributors- File types modified recently
3. Action Items
Search the codebase for:
- TODO items with file:line context
- FIXME items requiring attention
- HACK/TEMP items needing proper implementation
4. Project Health
Evaluate project configuration:
- Configuration files present (package.json, requirements.txt, etc.)
- Test file coverage (test/spec files)
- Documentation status (README, docs/)
5. Summary Report
Provide actionable insights:
- Git Health: Branch status, uncommitted changes, remote sync
- Development Velocity: Activity patterns, file hotspots
- Technical Debt: Action items by priority
- Project Status: Config completeness, test coverage, doc gaps
If $ARGUMENTS specifies a focus area (git, todos, health, activity), provide an in-depth analysis for that area.
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 · 63 lines · 20 tokens per session scan A f5d189ae4494
team-repo-status is a skill published in the GitHub repository bryanweaver/claude-agent-kit (2 stars, last pushed 2mo ago), licensed MIT. It adds 20 tokens to every session and 427 once invoked, about $0.0001 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.