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/xxxxxccc/devops-bot/code-review-analysisnpx skills add xxxxxccc/devops-bot --skill code-review-analysisgit clone --depth 1 https://github.com/xxxxxccc/devops-botWhat 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.00040 | $0.00478 |
| Opus 5 | $0.00020 | $0.00239 |
| Sonnet 5 | $0.00008 | $0.00096 |
| Haiku 4.5 | $0.00004 | $0.00048 |
Grade A, and why
code-review-analysis 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.
This is a copy
100% identical to code-review-analysis — 0 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.
What it actually says
Code Review Analysis
Table of Contents
Overview
Systematic code review process covering code quality, security, performance, maintainability, and best practices following industry standards.
When to Use
- Reviewing pull requests and merge requests
- Analyzing code quality before merging
- Identifying security vulnerabilities
- Providing constructive feedback to developers
- Ensuring coding standards compliance
- Mentoring through code review
Quick Start
Minimal working example:
# Check the changes
git diff main...feature-branch
# Review file changes
git diff --stat main...feature-branch
# Check commit history
git log main...feature-branch --oneline
Reference Guides
Detailed implementations in the references/ directory:
| Guide | Contents |
|---|---|
| Initial Assessment | Initial Assessment |
| Code Quality Analysis | Code Quality Analysis |
| Security Review | Security Review |
| Performance Review | Performance Review |
| Testing Review | Testing Review |
| Best Practices | Best Practices |
Best Practices
✅ DO
- Be constructive and respectful
- Explain the "why" behind suggestions
- Provide code examples
- Ask questions if unclear
- Acknowledge good practices
- Focus on important issues
- Consider the context
- Offer to pair program on complex issues
❌ DON'T
- Be overly critical or personal
- Nitpick minor style issues (use automated tools)
- Block on subjective preferences
- Review too many changes at once (>400 lines)
- Forget to check tests
- Ignore security implications
- Rush the review
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 · 83 lines · 40 tokens per session scan A b50b9b7f06a8
code-review-analysis is a skill published in the GitHub repository xxxxxccc/devops-bot (47 stars, last pushed 4mo ago), licensed MIT. It adds 40 tokens to every session and 478 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to code-review-analysis, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
setup
Add or remove notification channels (telegram, slack, teams, lark, webhook).
add-adapter
Add a vendor-official or community adapter to the Chat SDK catalog and docs — adapters.json registry, chat/adapters catalog entry, the docs MDX page, meta.json, integration-test lists, and a changeset. Use when a developer wants to add, list, register, or submit a third-party (vendor-official or community) adapter to…
chat-sdk
Build multi-platform chat bots with Chat SDK (chat npm package). Use when developers want to scaffold a bot with create-chat-sdk, build a Slack, Teams, Google Chat, Discord, Telegram, GitHub, Linear, or WhatsApp bot, handle mentions, direct messages, subscribed threads, reactions, slash commands, cards, modals, files…
update-model-pricing
Verify and refresh AgentConnect's daemon-side public OpenAI fallback pricing, exact model aliases, long-context and cache rules, and regression tests. Use when OpenAI model prices or IDs change, fallback cost becomes missing or stale, codex-acp changes its token mapping, or someone asks to audit or update…
agentconnect-setup
Guide users through installing, configuring, and verifying the complete self-hosted AgentConnect OSS stack as an interactive tutorial. Use for Docker Compose setup, local no-auth evaluation, the bundled local Logto overlay, Logto Cloud authentication, Cloudflare Tunnel or reverse-proxy exposure, custom production…
meegle
飞书项目（Meego/Meegle）操作工具。支持查询和管理工作项、节点流转、视图查询、个人待办、排期统计等功能。 Use when user needs to work with Feishu/Lark Meego project management — including querying work items, creating/updating work items, completing workflow nodes, checking views, listing todos, analyzing schedules/workloads, or searching with MQL.…