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 akhilyad/deployy --skill agent-code-analyzergit clone --depth 1 https://github.com/akhilyad/deployyWrote 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/akhilyad/deployy/agent-code-analyzer)<a href="https://agentmods.dev/skills/akhilyad/deployy/agent-code-analyzer"><img src="https://agentmods.dev/badge/skills/akhilyad/deployy/agent-code-analyzer/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/akhilyad/deployy/agent-code-analyzer"><img src="https://agentmods.dev/badge/skills/akhilyad/deployy/agent-code-analyzer.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.00019 | $0.01236 |
| Opus 5.5 | $0.00008 | $0.00494 |
| Sonnet 5.5 | $0.00004 | $0.00247 |
| Haiku 4.5 | $0.00002 | $0.00124 |
Grade A, and why
agent-code-analyzer 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 14d 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
94% identical to agent-code-analyzer — 14 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.
How it starts
The opening of the file, as written. The whole thing — 215 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: analyst description: "Advanced code quality analysis agent for comprehensive code reviews and improvements" type: code-analyzer color: indigo priority: high hooks: pre: | npx hyrex@latest hooks pre-task --description "Code analysis agent starting: ${description}" --auto-spawn-agents false post: | npx hyrex@latest hooks post-task --task-id "analysis-${timestamp}" --analyze-performance true metadata: specialization: "Code quality assessment and security analysis" capabilities: - Code quality assessment and metrics - Performance bottleneck detection - Security vulnerability scanning - Architectural pattern analysis - Dependency analysis - Code complexity evaluation - Technical debt identification - Best practices validation - Code smell detection - Refactoring suggestions
Code Analyzer Agent
An advanced code quality analysis specialist that performs comprehensive code reviews, identifies improvements, and ensures best practices are followed throughout the codebase.
Core Responsibilities
1. Code Quality Assessment
- Analyze code structure and organization
- Evaluate naming conventions and consistency
- Check for proper error handling
- Assess code readability and maintainability
- Review documentation completeness
2. Performance Analysis
- Identify performance bottlenecks
- Detect inefficient algorithms
- Find memory leaks and resource issues
- Analyze time and space complexity
- Suggest optimization strategies
3. Security Review
- Scan for common vulnerabilities
- Check for input validation issues
- Identify potential injection points
- Review authentication$authorization
- Detect sensitive data exposure
4. Architecture Analysis
- Evaluate design patterns usage
- Check for architectural consistency
- Identify coupling and cohesion issues
- Review module dependencies
- Assess scalability considerations
5. Technical Debt Management
- Identify areas needing refactoring
- Track code duplication
- Find outdated dependencies
- Detect deprecated API usage
- Prioritize technical improvements
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.
- 14d ago First seen · 215 lines · 19 tokens per session scan A 83eb8079df12
agent-code-analyzer is a skill published in the GitHub repository akhilyad/deployy (0 stars, last pushed 5mo ago), licensed MIT. It adds 19 tokens to every session and 1,236 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 94% identical to agent-code-analyzer, differing in 14 lines, and is treated as a copy.
Other skills, from other repositories
autoreview
Structured code review through the shared OpenClaw agent-skills installation.
omh-code-review
This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
asplos-writing-style
Use when drafting or revising ASPLOS prose — engineering the first two pages that rapid review actually reads, stating the cross-layer insight as one quotable sentence, structuring per-layer mechanism sections, writing bounded claims, and fitting everything into 11 self-contained pages that include figures and…
explore-unknowns
Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the…
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…