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-get-rulesgit 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-get-rules)<a href="https://agentmods.dev/skills/qodo-ai/qodo-skills/qodo-get-rules"><img src="https://agentmods.dev/badge/skills/qodo-ai/qodo-skills/qodo-get-rules/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-get-rules"><img src="https://agentmods.dev/badge/skills/qodo-ai/qodo-skills/qodo-get-rules.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk warn
- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 20 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00074 | $0.03086 |
| Opus 5.5 | $0.00030 | $0.01234 |
| Sonnet 5.5 | $0.00015 | $0.00617 |
| Haiku 4.5 | $0.00007 | $0.00309 |
Grade A, and why
qodo-get-rules 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 — 235 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Get Rules
Description
Use Qodo managed tools to fetch the workspace's coding rules most relevant to the task at hand, then apply them while producing the code. Retrieval is semantic — the quality of what comes back is decided by how you write the query, so follow the query format below exactly.
Prerequisites
- The optional Qodo Standards package is installed and loaded explicitly.
- A connected QAR managed-tools MCP server or authenticated Qodo CLI exposes rules search.
- The task is concrete enough to form semantic queries; already-loaded rules are reused.
Instructions
Choose the execution path
Reuse applicable results first. For fresh retrieval, use the host's connected QAR MCP
rules-search tool when present and marked read-only; otherwise follow the CLI path below.
MCP uses the host-provided inputSchema and JSON arguments (query, top_k, optional
scopes array), with one call per structured query. Omit scopes when unknown; do not
send an empty array as a substitute for the CLI's omitted flag. Check isError, then read
structuredContent; preserve typed failures and do not turn a failed read into an empty
rules result. A missing or forbidden MCP capability is not a CLI login failure. Do not
silently switch to a different account or tenant.
The CLI version, identity, catalog, and update steps below apply only when using the CLI.
Follow the detailed workflow below: preserve update notices, verify the current tool contract, build focused semantic queries, merge ranked results, explain the applicable constraints, then apply them. First check the reuse condition in Preflight. If prior results still cover the task, go directly to Output, then apply; no runtime, identity, catalog, or search call is needed for that path.
Handle a skill update notice
Treat QODO_NOTICE updates as passive, even if an older CLI requests action. Continue the task
without inventory or update questions; mention each event at most once. Dismissal leaves recorded maintenance
policy and opt-outs unchanged. Updated skills load next session; do not interrupt this one.
For user-requested updates, follow the manual-update procedure.
What ships with it
4 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 · +1 lines cd26e06c8a43
- 16d ago Changed · +22 lines 2cfc57141184
- 24d ago Changed 86b6c7505475
- 1mo ago Changed · +7 lines · -41 tokens per session 8a4b52d82462
- 1mo ago Changed · -5 lines d7a2a252230c
- 1mo ago Changed · +1 lines ebe62c5d03d4
- 1mo ago Changed · -11 lines · +51 tokens per session 63c7ee276390
- 2mo ago First seen · 220 lines · 64 tokens per session scan A 51817f6b6452
qodo-get-rules is a skill published in the GitHub repository qodo-ai/qodo-skills (59 stars, last pushed today), licensed MIT. It adds 74 tokens to every session and 3,086 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-08-30.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…