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 AmariahAK/atlarix-skills --skill acr-github-code-quality-cursorrules-prompt-filegit clone --depth 1 https://github.com/AmariahAK/atlarix-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/amariahak/atlarix-skills/acr-github-code-quality-cursorrules-prompt-file)<a href="https://agentmods.dev/skills/amariahak/atlarix-skills/acr-github-code-quality-cursorrules-prompt-file"><img src="https://agentmods.dev/badge/skills/amariahak/atlarix-skills/acr-github-code-quality-cursorrules-prompt-file/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/amariahak/atlarix-skills/acr-github-code-quality-cursorrules-prompt-file"><img src="https://agentmods.dev/badge/skills/amariahak/atlarix-skills/acr-github-code-quality-cursorrules-prompt-file.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.01013 |
| Opus 5 | $0.00005 | $0.00507 |
| Sonnet 5 | $0.00002 | $0.00203 |
| Haiku 4.5 | $0.00001 | $0.00101 |
Grade A, and why
Cursor rules for GitHub development with code quality integration 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 9d 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cursor rules for GitHub development with code quality integration
When to use this skill
Cursor rules for GitHub development with code quality integration.
Source
Synced from https://github.com/PatrickJS/awesome-cursorrules/tree/main/rules/github-code-quality-cursorrules-prompt-file.mdc.
{ "rules": [ { "name": "Verify Information", "pattern": "(?i)\b(assume|assumption|guess|speculate)\b", "message": "Always verify information before presenting it. Do not make assumptions or speculate without clear evidence." }, { "name": "File-by-File Changes", "pattern": "// MULTI-FILE CHANGE:", "message": "Make changes file by file and give me a chance to spot mistakes" }, { "name": "No Apologies", "pattern": "(?i)\b(sorry|apologize|apologies)\b", "message": "Never use apologies" }, { "name": "No Understanding Feedback", "pattern": "(?i)\b(understand|understood|got it)\b", "message": "Avoid giving feedback about understanding in comments or documentation" }, { "name": "No Whitespace Suggestions", "pattern": "(?i)\b(whitespace|indentation|spacing)\b", "message": "Don't suggest whitespace changes" }, { "name": "No Summaries", "pattern": "(?i)\b(summary|summarize|overview)\b", "message": "Don't summarize changes made" }, { "name": "No Inventions", "pattern": "(?i)\b(suggest|recommendation|propose)\b", "message": "Don't invent changes other than what's explicitly requested" }, { "name": "No Unnecessary Confirmations", "pattern": "(?i)\b(make sure|confirm|verify|check)\b", "message": "Don't ask for confirmation of information already provided in the context" }, { "name": "Preserve Existing Code", "pattern": "(?i)\b(remove|delete|eliminate|destroy)\b", "message": "Don't remove unrelated code or functionalities. Pay attention to preserving existing structures." }, { "name": "Single Chunk Edits", "pattern": "(?i)\b(first|then|next|after that|finally)\b", "message": "Provide all edits in a single chunk instead of multiple-step instructions or explanations for the same file" }, { "name": "No Implementation Checks", "pattern": "(?i)\b(make sure|verify|check|confirm) (it's|it is|that) (correctly|properly) implemented\b", "message": "Don't ask the user to verify implementations that are visible in the provided context" }, { "name": "No Unnecessary Updates", "pattern": "(?i)\b(update|change|modify|alter)\b.\bno changes\b", "message": "Don't suggest updates or changes to files when there are no actual modifications needed" }, { "name": "Provide Real File Links", "pattern": "(?i)\b(file|in)\b.\b(x\.md)\b", "message": "Always provide links to the real files, not x.md" }, { "name": "No Previous x.md Consideration", "pattern": "(?i)\b(previous|earlier|last)\b.*\bx\.md\b", "message": "Do not consider any previous x.md files in your memory. Complain if the contents are the same as previous runs." }, { "name": "No Current Implementation", "pattern": "(?i)\b(current|existing)\s+(implementation|code)\b", "message": "Don't show or discuss the current implementation unless specifically requested" }, { "name": "Check x.md Content", "pattern": "(?i)\b(file|content|implementation)\b", "message": "Remember to check the x.md file for the current file contents and implementations" } ] }
What ships with it
1 file 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.
- 9d ago First seen · 102 lines · 10 tokens per session scan A d1e9b749d7c0
Cursor rules for GitHub development with code quality integration is a skill published in the GitHub repository AmariahAK/atlarix-skills (2 stars, last pushed 2d ago), licensed Apache-2.0. It adds 10 tokens to every session and 1,013 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
sol-luna-router
Route substantial coding or repository-review work through a two-stage Sol commander/verifier and separate Luna Max CLI worker. Use when the user explicitly asks Sol to direct or supervise Luna, explicitly requests this router, needs an isolated auditable Luna-owned implementation with a Sol review loop, or asks to…
idea-team
A structured group discussion for exploring a product idea through three roles: researcher, critic, and analogy finder. The roles look for evidence, weaknesses, and useful comparisons.
codebase-audit
A read-only method for auditing an entire codebase across contracts, data integrity, errors, security, architecture, technical debt, configuration, and caching. It produces prioritized findings and a repair roadmap.
codex-agent
Use when you want a second-opinion review via Codex CLI, cross-verification after another agent implements changes, debugging help, or alternative implementation proposals. Requires Codex CLI to be installed and authenticated.
project-health-auditor
Comprehensive codebase health analysis. Use when reviewing code quality, identifying technical debt, checking dependencies, or assessing project structure.
review-gate
Use before an agent-produced diff is committed, pushed, opened as a PR, merged, landed, or applied to user files when explicit implementation approval is missing. Trigger for review gate, review pack, approve before landing, diff first then land, human approval, merge gate, commit gate, push gate, or PR readiness.…