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 skills/zexion7873/copilot-setting/code-reviewnpx skills add zexion7873/copilot-setting --skill code-reviewgit clone --depth 1 https://github.com/zexion7873/copilot-settingWhat 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.00080 | $0.01453 |
| Opus 5 | $0.00040 | $0.00727 |
| Sonnet 5 | $0.00016 | $0.00291 |
| Haiku 4.5 | $0.00008 | $0.00145 |
Grade A, and why
code-review 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 2d 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Review — Workflow
Structured code review.
Phase 0 — Load canonical rules
MANDATORY pre-load gate — do NOT render a verdict (Phase 5) until you have opened the instruction files for the layers under review. Your training data defaults to modern Java/Spring; these files are the version lock for Java 8 / Spring 3.2 / Hibernate 4.2. Open them first, every time — the negative lists in the agent body are a floor, not the full rules:
instructions/java.instructions.md— Java 8 language boundaryinstructions/spring-hibernate.instructions.md— Spring 3.2 + Hibernate 4.2instructions/sql.instructions.md— SQL injection, indexing, JDBC resourcesinstructions/sql-ddl.instructions.md— MySQL DDL & migration safety, stored proceduresinstructions/security.instructions.md— OWASP Top 10instructions/jsp.instructions.md— JSP / JSTL, XSSinstructions/xml-config.instructions.md— Spring XML, hbm.xml, Maven POMinstructions/testing.instructions.md— test conventions (test-class@Transactionalauto-rollback is sanctioned)
Read-back receipt (self-check, not machine-enforced): before leaving this step, NAME each instruction file you opened above and QUOTE the single most load-bearing rule from each that applies to this change — a generic restatement you could have written from memory means you skipped the file, so open it for real.
Phase 1 — Understand the Change
- Read the diff / files under review
- Understand the intent: what problem does this solve?
- Check if the approach matches existing patterns
Phase 2 — Review by Category
Correctness (check each):
- Shared mutable state accessed from multiple threads → synchronized or thread-local?
- JDBC resources (
Connection,PreparedStatement,ResultSet, streams) managed via try-with-resources; HibernateSessionfromgetCurrentSession()is never closed/flushed manually (Spring owns its lifecycle)
Security (check each):
- Every SQL query uses bind parameters (
?or:named) - Every JSP output wrapped in
<c:out>or equivalent encoding - Every endpoint has explicit access control check
- No hardcoded credentials, API keys, or secrets
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.
- 2d ago First seen · 113 lines · 80 tokens per session scan A 34d8564a0542
code-review is a skill published in the GitHub repository zexion7873/copilot-setting (1 stars, last pushed 29d ago), licensed MIT. It adds 80 tokens to every session and 1,453 once invoked, about $0.0004 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
jira-cli
Interact with Jira from the command line to create, list, view, edit, and transition issues, manage sprints and epics, and perform common Jira workflows. Use when the user asks about Jira tasks, tickets, issues, sprints, or needs to manage project work items.
azure-prices
Look up and compare Azure service pricing using the Azure Retail Prices API. Use this skill whenever the user asks about Azure costs, pricing, rates, or wants to compare prices across regions or services — even if they don't say "pricing" explicitly. Trigger for questions like "how much does a D2 v2 VM cost?"…
calculator
Performs arbitrary-precision arithmetic calculations including addition, subtraction, multiplication, division, and exponents. Use when the user asks to calculate, compute, or evaluate math expressions, or when precise decimal arithmetic is needed to avoid floating-point errors.
az-cli
Use the Azure CLI (az) to manage Azure resources from the command line. Trigger this skill whenever the user asks to create, configure, manage, deploy, or interact with any Azure resource — even if they don't explicitly mention "az cli". Also trigger when the user asks about Azure CLI commands, syntax, or wants to…
plan-task
Create a detailed implementation plan before coding. Use when starting a new feature, multi-step refactor, or complex task. Invoked by saying "plan", "create a plan", or "plan this task".
commit
Stage, commit, and push code changes with branch safety and explicit staging. Use when ready to commit work. Invoked by saying "commit", "push", or "commit and push".