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 ivanhoinacki/team-exp-claude-config --skill codereviewgit clone --depth 1 https://github.com/ivanhoinacki/team-exp-claude-configWrote 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/ivanhoinacki/team-exp-claude-config/codereview)<a href="https://agentmods.dev/skills/ivanhoinacki/team-exp-claude-config/codereview"><img src="https://agentmods.dev/badge/skills/ivanhoinacki/team-exp-claude-config/codereview/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/ivanhoinacki/team-exp-claude-config/codereview"><img src="https://agentmods.dev/badge/skills/ivanhoinacki/team-exp-claude-config/codereview.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.00080 | $0.11791 |
| Opus 5 | $0.00040 | $0.05895 |
| Sonnet 5 | $0.00016 | $0.02358 |
| Haiku 4.5 | $0.00008 | $0.01179 |
Grade A, and why
codereview 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 8d 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 — 913 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Review — Full Spectrum
Phase 0: Vault RAG (MANDATORY, BEFORE ANYTHING ELSE)
Before ANY file reads, grep, or codebase exploration, call query_vault with relevant keywords and service_filter. This is non-negotiable and must be the FIRST action after reading the task. The vault contains pitfalls, business rules, review learnings, and patterns that prevent rework. Skip = rework.
Working Directories
- Obsidian workspace (docs, plans, features):
__VAULT_ROOT__ - Codebase (all LE services):
__CODEBASE_ROOT__
References
| File | Content |
|---|---|
references/dimension-details.md |
Full 18-dimension definitions with tier/severity for each |
references/known-gotchas.md |
Recurring bug patterns to check against every diff |
references/learnings.md |
Lessons from past reviews (grows over time) |
Mode Detection
PR mode (argument is a PR URL, number, or ticket with open PR): Review a pull request with inline GitHub comments. Branch mode (no argument, no open PR, or merged/closed PR): Self-review current branch diff against main. Includes local CI checks.
Quick Reference Flow
Step 0: Detect PR and review mode
Step 0.5: CI checks (BRANCH MODE ONLY)
Step 1: Get the diff (detect PR vs branch)
Step 1.5: Diff triage (classify files, assess risk) → PRESENT triage summary
Step 2: Context gathering (intent + full code read + deep search)
2.1 Understand intent (PR body / git log / vault feature doc)
2.2 Read code (full files + callers + tests)
2.3 Deep context (vault RAG + git history + PR history + Slack + Confluence)
2.4 Previous review round (PR mode: inline comments + review verdicts)
GATE: Context self-check → PRESENT checklist (all items must be [x])
Step 3: Analyze ALL 18 dimensions + read known-gotchas.md + feature flag + dep analysis + D6 test checklist
→ PRESENT "Known gotchas checked" section (mandatory, even if all N/A)
→ PRESENT "D6 test checklist" results (if test files in diff)
Step 4: Draft comments (human tone, no labels, max 2 sentences, actionable)
→ PRESENT Verification checklist with [x] marks (mandatory, not prose)
Step 5: Present findings for approval (STOP and WAIT)
Step 6: Post comments (PR mode only)
Step 7: Approve or request changes (PR mode only)
Step 8: Summary + workflow compliance
Step 9: Save learnings
Step 10: Export for other instance
What ships with it
2 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.
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.
- 8d ago First seen · 913 lines · 80 tokens per session scan A 59ba7bf7e97e
codereview is a skill published in the GitHub repository ivanhoinacki/team-exp-claude-config (2 stars, last pushed 1mo ago), licensed MIT. It adds 80 tokens to every session and 11,791 once invoked, about $0.0004 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
sdd-tasks
Break an SDD change into implementation tasks. Trigger: orchestrator launches task planning for a change.
pr-blocker-summarizer
Summarizes open pull requests into a blockers-first standup digest. Activates when the user asks to summarize open PRs, find blocked pull requests, generate a PR standup, or triage review backlog from a PR export.
review-work
Post-implementation gate review: run manual QA on the real surface yourself, then launch ONE gate reviewer (never a panel) to audit goal, constraints, code quality, security, missed context, and QA evidence. Use before a PR handoff or when the user explicitly asks to review completed work.
ijfw-cross-audit
Generate a cross-platform multi-model audit (Trident) on a diff, brief, or artifact. Trigger: 'cross audit', 'Trident', 'second opinion', 'check with other models', 'check with other AIs', 'cross-check this', 'get another perspective', /cross-audit.
doc-drift
Use this skill when the user wants to audit the memory and documents Claude Code loads into context — CLAUDE.md (user global + project + nested), MEMORY.md, @imports, .claude/skills, .claude/agents, .claude/commands, installed plugins — and detect four kinds of issues: outdated claims, mutually contradictory…
ponytail-lazy-senior-dev
Applies the "lazy senior developer" mindset. Use this skill whenever generating, modifying, reviewing code, or fixing bugs to prioritize code reuse, minimalism, YAGNI principles, and root-cause fixes. Also use whenever the user says "ponytail", "be lazy", "lazy mode", "simplest solution", "minimal solution", "yagni"…