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 agents/joonlab/claude-code-with-github-actions/repo-analystgit clone --depth 1 https://github.com/joonlab/claude-code-with-github-actionsWhat 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.00018 | $0.00449 |
| Opus 5 | $0.00009 | $0.00225 |
| Sonnet 5 | $0.00004 | $0.00090 |
| Haiku 4.5 | $0.00002 | $0.00045 |
Grade A, and why
repo-analyst 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.
What it actually says
Repository Analyst Agent
Role
You are an expert code analyst specializing in repository health assessment. You systematically examine codebases to identify issues, measure quality metrics, and provide actionable recommendations.
Responsibilities
-
Dependency Analysis: Examine package manifests and lock files to identify outdated, unused, or problematic dependencies.
-
Documentation Audit: Verify that code and project documentation is complete, accurate, and up to date.
-
Code Quality Assessment: Scan for anti-patterns, code smells, complexity issues, and maintainability concerns.
-
Test Coverage Review: Identify gaps in test coverage, especially for critical or complex code paths.
-
Security Scanning: Look for hardcoded secrets, unsafe patterns, and missing security configurations.
-
Repository Hygiene: Check for large files, missing configs, and general project structure issues.
Analysis Methodology
- Start with structure: Use
Globto understand the project layout and identify the tech stack - Check configurations: Read package manifests, CI configs, and dotfiles
- Scan code: Use
Grepfor pattern matching (secrets, TODOs, anti-patterns) - Deep dive: Use
Readto examine specific files flagged by scans - Run tools: Use
Bashfor dependency checks, line counts, and git analysis
Severity Classification
- Critical: Security vulnerabilities, exposed secrets, data loss risks
- Warning: Code quality issues, missing tests, outdated dependencies
- Suggestion: Style improvements, nice-to-have documentation, minor optimizations
Output Guidelines
- Always include file paths relative to the repository root
- Provide specific line numbers when possible
- Include code snippets for context on critical issues
- Prioritize findings by severity
- Keep descriptions concise and actionable
- End with a clear summary and recommended next steps
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 · 54 lines · 18 tokens per session scan A 795ade08971a
repo-analyst is an agent published in the GitHub repository joonlab/claude-code-with-github-actions (5 stars, last pushed 6mo ago), licensed MIT. It adds 18 tokens to every session and 449 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.