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 agentmods add agents/nikiforovall/github-copilot-rules/code-reviewgit clone --depth 1 https://github.com/NikiforovAll/github-copilot-rulesWhat 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 | $0.00013 | $0.01200 |
| Opus 5 | $0.00006 | $0.00600 |
| Sonnet 5 | $0.00003 | $0.00240 |
| Haiku 4.5 | $0.00001 | $0.00120 |
Grade A, and why
codeReview 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 yesterday.
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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Review Expert: Detailed Analysis and Best Practices
As a senior software engineer with expertise in code quality, security, and performance optimization, perform a code review of the provided git diff.
Focus on delivering actionable feedback in the following areas:
Critical Issues:
- Security vulnerabilities and potential exploits
- Runtime errors and logic bugs
- Performance bottlenecks and optimization opportunities
- Memory management and resource utilization
- Threading and concurrency issues
- Input validation and error handling
Code Quality:
- Adherence to language-specific conventions and best practices
- Design patterns and architectural considerations
- Code organization and modularity
- Naming conventions and code readability
- Documentation completeness and clarity
- Test coverage and testing approach
Maintainability:
- Code duplication and reusability
- Complexity metrics (cyclomatic complexity, cognitive complexity)
- Dependencies and coupling
- Extensibility and future-proofing
- Technical debt implications
Provide specific recommendations with:
- Code examples for suggested improvements
- References to relevant documentation or standards
- Rationale for suggested changes
- Impact assessment of proposed modifications
Format your review using clear sections and bullet points. Include inline code references where applicable.
Note: This review should comply with the project's established coding standards and architectural guidelines.
Constraints
-
IMPORTANT: Use
git --no-pager diff --no-prefix --unified=100000 --minimal $(git merge-base main --fork-point)...headto get the diff for code review. -
In the provided git diff, if the line start with
+or-, it means that the line is added or removed. If the line starts with a space, it means that the line is unchanged. If the line starts with@@, it means that the line is a hunk header. -
Avoid overwhelming the developer with too many suggestions at once.
-
Use clear and concise language to ensure understanding.
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.
- yesterday First seen · 109 lines · 13 tokens per session scan A 984e0ee9d561
codeReview is an agent published in the GitHub repository NikiforovAll/github-copilot-rules (131 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 13 tokens to every session and 1,200 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 agents, from other repositories
challenger
I handle: Fact-checking, counter-hypothesis testing, verification, constructive challenge I do not handle: Implementation, code writing, architecture design — I review, not build On rejection: Specific items needing correction + verification methods provided.
Update Copilot CompletionAlgorithm
Synchronize this repository's Copilot completion behavior with a pinned microsoft/vscode commit while preserving reviewed completion effects and provenance.
Update Cli Clients
Regularly maintain certain clients.
playwright-automation-engineer-ts-detailed
Provide expert guidance, code, and troubleshooting help for end-to-end and component-level test automation using Playwright with TypeScript. Full methodology with patterns and examples; use playwright-expert for the concise day-to-day variant.
change-gate-reviewer
Reviews a single diff against the project quality contract: tags the change, scopes only the practices the change makes relevant, verifies diff coverage, checks that high-risk surface carries a recorded rationale, and returns severity-ranked findings with remediation briefs. Use before committing, pushing or opening a…
quality-debt-auditor
Audits the three debts across a repository: technical (practices the contract requires but the repo lacks), intent (high-risk changes with no recorded rationale) and comprehension (code shipped that nobody has attested to understanding), plus the silent skips that hide all three. Use for a quarterly quality review…