Swarms is a Python framework for coordinating multiple autonomous language-model agents into workflows such as sequential, concurrent, or hierarchical systems. It is used to build multi-step applications in which agents combine language models, tools, and memory. The catalogue entries provide agent-oriented skills, instructions, and an agent for working with Swarms.
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 kyegomez/swarms --skill code-reviewgit clone --depth 1 https://github.com/kyegomez/swarmsWrote 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/kyegomez/swarms/code-review)<a href="https://agentmods.dev/skills/kyegomez/swarms/code-review"><img src="https://agentmods.dev/badge/skills/kyegomez/swarms/code-review/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/kyegomez/swarms/code-review"><img src="https://agentmods.dev/badge/skills/kyegomez/swarms/code-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00021 | $0.00571 |
| Opus 5.5 | $0.00008 | $0.00228 |
| Sonnet 5.5 | $0.00004 | $0.00114 |
| Haiku 4.5 | $0.00002 | $0.00057 |
Grade A, and why
code-review 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 1mo 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Review Skill
When reviewing code, follow this systematic approach to ensure thorough evaluation:
Review Checklist
1. Code Quality
- Readability: Is the code easy to understand?
- Naming: Are variables, functions, and classes well-named?
- Structure: Is the code properly organized and modular?
- Comments: Are complex sections adequately documented?
- Complexity: Are there overly complex functions that should be simplified?
2. Security Analysis
Check for common vulnerabilities:
- SQL injection vulnerabilities
- XSS (Cross-Site Scripting) vulnerabilities
- Authentication and authorization flaws
- Insecure data handling (passwords, sensitive data)
- Input validation and sanitization
- OWASP Top 10 vulnerabilities
3. Performance Considerations
- Identify potential bottlenecks
- Check for inefficient algorithms or data structures
- Look for unnecessary database queries or API calls
- Evaluate caching opportunities
- Assess memory usage patterns
4. Best Practices
- DRY Principle: Eliminate code duplication
- SOLID Principles: Verify adherence to design principles
- Error Handling: Check for proper exception handling
- Testing: Evaluate test coverage and quality
- Dependencies: Review external dependencies and their versions
5. Maintainability
- Is the code easy to modify and extend?
- Are there proper abstractions?
- Is the architecture scalable?
- Are there technical debt concerns?
Review Format
Structure your review as follows:
- Summary: High-level overview of the changes
- Critical Issues: Security vulnerabilities or bugs that must be fixed
- Major Concerns: Significant issues affecting quality or performance
- Suggestions: Optional improvements and best practices
- Positive Feedback: Acknowledge good practices and improvements
Guidelines
- Be constructive and respectful
- Provide specific examples and suggestions
- Explain the "why" behind recommendations
- Prioritize issues by severity (critical, major, minor)
- Reference documentation or standards when applicable
- Consider the context and constraints of the project
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.
- 1mo ago First seen · 82 lines · 21 tokens per session scan A 2869a7c4a899
code-review is a skill published in the GitHub repository kyegomez/swarms (7,282 stars, last pushed yesterday), licensed Apache-2.0. It adds 21 tokens to every session and 571 once invoked, about $0.0001 per session on Opus 5.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-30.
Other skills, from other repositories
code-reviewer
Review code for best practices, potential bugs, security vulnerabilities, and performance issues.
find-security-vulnerabilities-in-code
Find security vulnerabilities in a codebase or repository with Strix — a white-box AI security review that reads your source, reasons about the actual data flow and authorization model, then exploits what it finds in a live sandbox so every reported issue has a working proof-of-concept instead of a noisy…
code-review
Review pull requests for repository fit, meaningful value, trustworthy provenance, differentiation, and maintainability in awesome-copilot.
deep-review
Parallel competency-based code review. Launches independent Agent reviewers per competency (security, performance, architecture, database, concurrency, error-handling, frontend, testing), each with a focused checklist and isolated context. Synthesizes findings into unified report with FIX/DEFER/ACCEPT triage. Use…
architecture-quality
Keep web applications, APIs and services readable as they grow: choose feature or domain seams, assign state ownership, enforce dependency direction, keep adapters thin, and verify file shape. Use when starting or extending a web app, backend, frontend, API or multi-page product; when a change makes a module hard to…
thermo-nuclear-code-quality-review
Run an opt-in strict maintainability review for giant files, spaghetti growth, misplaced logic, weak boundaries, unnecessary abstractions, and missed structural simplifications. Use for a thermonuclear review, harsh code-quality audit, code-judo review, or a file approaching 1000 lines. Do not use as an automatic…