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 agentmods add skills/bryanweaver/claude-agent-kit/team-auditnpx skills add bryanweaver/claude-agent-kit --skill team-auditgit 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-audit)<a href="https://agentmods.dev/skills/bryanweaver/claude-agent-kit/team-audit"><img src="https://agentmods.dev/badge/skills/bryanweaver/claude-agent-kit/team-audit.svg" alt="Measured on agentmods" 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 | $0.00023 | $0.00771 |
| Opus 5 | $0.00012 | $0.00385 |
| Sonnet 5 | $0.00005 | $0.00154 |
| Haiku 4.5 | $0.00002 | $0.00077 |
Grade A, and why
team-audit 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 5d 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Audit Log Analysis: $ARGUMENTS
Analyze Claude Code audit logs to provide insights into tool usage, file operations, commands executed, and verify claims about what was accomplished during a session.
Parse Arguments and Execute
Extract action and options from arguments, then run the log analyzer:
ARGS="$ARGUMENTS"
ACTION="summary"
SESSION=""
LIMIT="50"
CLAIMS=""
# Parse action from first token only
FIRST_TOKEN=$(printf '%s\n' "$ARGS" | awk '{print $1}')
case "$FIRST_TOKEN" in
report|metrics|timeline|verify|anomalies) ACTION="$FIRST_TOKEN" ;;
esac
# Extract session ID (session:abc123)
SESSION=$(echo "$ARGS" | grep -o 'session:[^[:space:]]*' | cut -d':' -f2 || echo "")
# Extract limit (limit:25)
LIMIT=$(echo "$ARGS" | grep -o 'limit:[0-9]*' | cut -d':' -f2 || echo "50")
# Extract claims (claims:"claim1,claim2")
CLAIMS=$(echo "$ARGS" | grep -o 'claims:"[^"]*"' | sed 's/claims://; s/"//g' || echo "")
Build and run the log analyzer command:
HOOKS_DIR="${CLAUDE_HOOKS:-$HOME/.claude/hooks}"
set -- node "$HOOKS_DIR/log_analyzer.cjs"
case "$ACTION" in
"report") set -- "$@" --report ;;
"metrics") set -- "$@" --metrics ;;
"timeline") set -- "$@" --timeline --limit "$LIMIT" ;;
"verify")
if [ -n "$CLAIMS" ]; then
set -- "$@" --verify
IFS=',' read -ra CLAIM_ARRAY <<< "$CLAIMS"
for claim in "${CLAIM_ARRAY[@]}"; do
set -- "$@" "$(echo "$claim" | xargs)"
done
else
echo "Error: Claims required for verify action. Use: /team-audit verify claims:\"claim1,claim2\""
exit 1
fi
;;
"anomalies") set -- "$@" --anomalies ;;
esac
if [ -n "$SESSION" ]; then
set -- "$@" --session "$SESSION"
fi
"$@"
Available Actions
| Action | Description |
|---|---|
| summary (default) | Quick overview of session metrics |
| report | Comprehensive audit report with all details |
| metrics | Detailed metrics about tools, files, and performance |
| timeline | Chronological view of all events (use limit:N to control output) |
| verify | Verify specific claims about what was accomplished |
| anomalies | Detect unusual patterns or potential issues |
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.
- 5d ago First seen · 90 lines · 23 tokens per session scan A 446e70da80bb
team-audit is a skill published in the GitHub repository bryanweaver/claude-agent-kit (2 stars, last pushed 2mo ago), licensed MIT. It adds 23 tokens to every session and 771 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…