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 qodo-ai/qodo-skills --skill qodo-review-notesgit clone --depth 1 https://github.com/qodo-ai/qodo-skillsWrote 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/qodo-ai/qodo-skills/qodo-review-notes)<a href="https://agentmods.dev/skills/qodo-ai/qodo-skills/qodo-review-notes"><img src="https://agentmods.dev/badge/skills/qodo-ai/qodo-skills/qodo-review-notes/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/qodo-ai/qodo-skills/qodo-review-notes"><img src="https://agentmods.dev/badge/skills/qodo-ai/qodo-skills/qodo-review-notes.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.00083 | $0.05418 |
| Opus 5.5 | $0.00033 | $0.02167 |
| Sonnet 5.5 | $0.00017 | $0.01084 |
| Haiku 4.5 | $0.00008 | $0.00542 |
Grade A, and why
qodo-review-notes 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 4d 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 — 391 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Development Tracks and PR Review Notes
Description
Keep the reasoning a reviewer needs in the platform, where other coding sessions and humans can find it. Development Track Notes explain the overall effort across issues, repositories and PRs. PR Review Notes explain one change and link to a track explicitly.
Prerequisites
Use an authenticated Qodo connection to the intended deployment and workspace. Notes tools must
be available in the live catalog. For CLI use, require Qodo CLI 2.0.0 or newer and the
PR commands' localGitCapture capability. A trusted MCP connection can supply the same operations.
Instructions
Discover the available tools, select the track explicitly, maintain revision-safe notes, publish the existing source HEAD before PR creation, then bind the returned notes ID after opening.
Handle a skill update notice
Treat QODO_NOTICE updates as passive. Continue the task and mention each notice at most once;
updated instructions load next session. For a requested update, follow
the manual maintenance procedure below without changing the organization's update origin.
Execution
- MCP: use live schema arguments; skip CLI shell steps.
- CLI: use complete UTF-8 files without a BOM (
--args-filefor tools,--context-filefor reviews); examples are POSIX. - Windows CLI: read shell guidance before the first call; launcher recovery only if invocation fails. Reuse the resolved invocation.
Choose the available tools
Use a trusted connected Qodo MCP server when available, otherwise the authenticated qodo CLI.
Discover the live schemas; the Tool access section below explains both transports and write
idempotency. Skills do not handle credentials, make HTTP requests, or use another account.
Read/discover without asking. Honor the host's write gate and the user's existing authorization
for note maintenance; a request to read or review notes alone does not authorize editing them.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago Changed · +10 lines 3d75fb462e7f
- 10d ago Changed · +16 lines 2e55f650df79
- 16d ago First seen · 365 lines · 83 tokens per session scan A 4abc71dbe740
qodo-review-notes is a skill published in the GitHub repository qodo-ai/qodo-skills (59 stars, last pushed today), licensed MIT. It adds 83 tokens to every session and 5,418 once invoked, about $0.0003 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-10-14.
Other skills, from other repositories
tech-debt
Track, categorize and prioritize technical debt across the codebase — scans for debt indicators, maintains a register.
OpenSourceManagement
Triages open issues, pull requests and GitHub Discussions across the principal's own open-source repos (the list in Config.md) via the gh CLI, ranks what needs attention with suggested replies, posts edit-in-place marker comments, diffs new Ollama library models against a local model box, and takes a private repo…
pr-review-triage
Watch open PRs, check CI status, review staleness, merge conflicts, and unanswered review comments. Produces a prioritized watchlist.
issue-creation
Trigger: issue creation, bug reports, feature requests, or issue approval. Create and triage GitHub issues from repository evidence.
systemic-issue-triage
Trigger: new issue, bug report, triage, backlog, issue flood, community report, root cause, dead-end, blocked user. Attack issues by root class, never one-by-one; fixes must shrink the system, not grow it.
spec-kitty-runtime-review
Review runtime-owned outputs using the Spec Kitty review workflow surface, then direct approval or rejection with structured feedback. Triggers: "review this work package", "check runtime output", "approve this step", "review WP", "is this WP ready to approve", "check this implementation". Does NOT handle: setup-only…