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 sordi-ai/skill-everything --skill review-deploymentgit clone --depth 1 https://github.com/sordi-ai/skill-everythingWrote 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/sordi-ai/skill-everything/review-deployment)<a href="https://agentmods.dev/skills/sordi-ai/skill-everything/review-deployment"><img src="https://agentmods.dev/badge/skills/sordi-ai/skill-everything/review-deployment/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/sordi-ai/skill-everything/review-deployment"><img src="https://agentmods.dev/badge/skills/sordi-ai/skill-everything/review-deployment.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.00029 | $0.00663 |
| Opus 5 | $0.00015 | $0.00331 |
| Sonnet 5 | $0.00006 | $0.00133 |
| Haiku 4.5 | $0.00003 | $0.00066 |
Grade A, and why
review-deployment 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 10d 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sub-Skill: Review & Deployment Process
Purpose: Prevents deployment accidents and ensures reviews are more than rubber-stamping. Concrete checklists the agent runs through before every PR and deployment.
PR Review Checklist (Agent runs this before opening a PR)
Correctness
- All new functions have tests
- Existing tests pass (
npm test/pytest/ etc.) - Edge cases covered: null/undefined, empty arrays, negative numbers
- No TODO comments without a linked ticket
Security
- No secrets or API keys in code (not even in comments)
- User input is validated before flowing into DB queries or shell commands
- New endpoints have authentication/authorization
- No
eval(),exec(), or dynamic SQL strings without prepared statements
Performance
- No N+1 queries (database queries in loops)
- Large datasets are paginated, not loaded entirely
- New indexes for new WHERE clauses in queries
Maintainability
- Complex logic is commented (the why, not the what)
- No duplicated code blocks (DRY)
- Dependencies updated in
package.json/requirements.txt
Deployment Checklist
Before Deployment
- Check migrations: Are all DB migrations backward-compatible? (No DROP COLUMN without prior deprecation cycle)
- Feature flags: New features behind a feature flag? Especially for large changes.
- Rollback plan: How to roll back if something goes wrong? Documented?
- Monitoring: Are alerts set up for new critical paths?
Deployment Order (for microservices)
- First: Database migrations (additive changes)
- Then: Backend services (new version)
- Last: Frontend (new version)
- Never: Frontend before backend when there are API changes
After Deployment
- Health check endpoint responds with 200
- Error rate in monitoring not elevated (observe for 5 minutes)
- Critical user flows manually tested (login, main feature, checkout)
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.
- 10d ago First seen · 86 lines · 29 tokens per session scan A e6a66d2c16b5
review-deployment is a skill published in the GitHub repository sordi-ai/skill-everything (20 stars, last pushed 3mo ago), licensed MIT. It adds 29 tokens to every session and 663 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-30.
Other skills, from other repositories
github
Scan GitHub for open PRs, stale reviews, failing CI checks, and team activity. Produce a code activity digest. Use this skill when the user wants GitHub digest only.
tech-debt-audit
Thorough, file-cited technical debt audit across 9 dimensions using AST-grep (tree-sitter), grep, LSP, and language-native tooling. Produces TECHDEBTAUDIT.md with severity, effort estimates, and prioritized fixes. Use when asked for codebase health check, tech debt audit, architecture review, code quality assessment…
code-review-web
Review web application code for bugs, security issues, performance problems, and stack-specific anti-patterns. Use this skill whenever the user wants to review code, debug a production issue, investigate a build failure, audit security, or check a PR before merging. Triggers on code review, review my code, debug…
suede-code-review
Suede Labs AI findings-only code review with full context: changed files, callers, contracts, and deploy surface. Covers TypeScript, React, Next.js, database, Swift/iOS, OWASP, accessibility, SEO, observability, commit hygiene, and deploy risk, ranked P0-P3 with file:line evidence and a fix path. Use when asked to…
refactor
Refactors code for quality and maintainability. Triggers: refactor, clean up, restructure, improve code, modernize.
clean-code
Code quality: meaningful names, SRP, DRY, small functions, guard clauses, refactoring. Triggers: clean code, naming, code smell, SRP, DRY, long function, god class, dead code.