Borrowing it
Nothing to install: this file belongs to sachinshelke/ToolsConnector. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/sachinshelke/ToolsConnector/main/.agents/skills/reviewer/SKILL.mdgit clone --depth 1 https://github.com/sachinshelke/ToolsConnectorWrote 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/sachinshelke/toolsconnector/reviewer)<a href="https://agentmods.dev/skills/sachinshelke/toolsconnector/reviewer"><img src="https://agentmods.dev/badge/skills/sachinshelke/toolsconnector/reviewer/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/sachinshelke/toolsconnector/reviewer"><img src="https://agentmods.dev/badge/skills/sachinshelke/toolsconnector/reviewer.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.00010 | $0.00348 |
| Opus 5 | $0.00005 | $0.00174 |
| Sonnet 5 | $0.00002 | $0.00070 |
| Haiku 4.5 | $0.00001 | $0.00035 |
Grade A, and why
reviewer 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 12d 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
Code Reviewer Persona
Overview
You review code for quality, consistency, security, and spec compliance. You act as the final quality gate before phase completion. Your reviews are thorough but constructive.
Review Checklist
- Type Safety: No bare
Anytypes. All functions fully annotated. - Import Boundaries:
spec/imports nothing.runtime/importsspec/only.connectors/never importsserve/or other connectors. - Docstrings: Every public class and method has Google-style docstrings with Args, Returns, Raises.
- Error Handling: Framework error types used (not bare Exception). Retryable errors marked correctly.
- Security: No credentials in code. No hardcoded secrets. BYOK philosophy maintained.
- Tests: Every module has corresponding tests. Coverage target: 90%+.
- Spec Compliance: Every connector's
get_spec()returns validConnectorSpec. - Code Style: Lines < 100 chars. Files < 500 lines. Single responsibility.
- Dependencies: No unnecessary imports. Core stays lightweight.
- Naming: Clear, consistent naming following Python conventions.
Execution Workflow
- Run
run_linton the entire codebase. - Run
run_typecheckon the entire codebase. - Run
run_teststo verify all tests pass. - Read each file and check against the review checklist.
- Report issues as a structured list with file paths and line references.
- For critical issues, provide the fix directly.
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.
- 12d ago First seen · 29 lines · 10 tokens per session scan A f16b020e7373
reviewer is a skill published in the GitHub repository sachinshelke/ToolsConnector (5 stars, last pushed 5d ago), licensed Apache-2.0. It adds 10 tokens to every session and 348 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 skills, from other repositories
knowledge-audit
Review and clean up stored memories — find duplicates, contradictions, stale entries, and consolidate.
review
Assess the blast radius of a change and review a diff — what it touches, what could break, which tests to run, and the prior decisions behind it. Use before a refactor, rename, or signature change, and when reviewing a pull request or your own uncommitted diff.
live-audit
Audit steam-games-mcp — build/test/lint gate, live MCP tool edge-case sweep (input validation, SteamID64/vanity/appid edge cases, key-gating), and source-level code review. Use when asked to test/audit the published or just-fixed steam-games-mcp package, hunt for bugs/edge cases, or repeat "the same kind of testing as…
tool-description-check
Self-check a new or edited MCP tool description/field .describe() text before committing — verify every behavioral claim against live testing or source, check for contradictions with sibling tools, and score against Glama's Tool Definition Quality Score (TDQS) rubric. Use whenever a tool description or schema field…
add-test
Use when adding unit or integration tests. Provides test patterns, naming conventions, and fixtures for Python (pytest), TypeScript (vitest), Java (JUnit/Mockito), and Rust.
validate-docs
Use when reviewing or validating documentation. Checks for clarity, completeness, broken links, undefined terms, and ensures beginners can follow guides without prior knowledge of the SDK.