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/askie/grix/grix-code-reviewnpx skills add askie/grix --skill grix-code-reviewgit clone --depth 1 https://github.com/askie/grixWhat 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.00070 | $0.00634 |
| Opus 5 | $0.00035 | $0.00317 |
| Sonnet 5 | $0.00014 | $0.00127 |
| Haiku 4.5 | $0.00007 | $0.00063 |
Grade A, and why
grix-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 — 43 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Grix Code Review
Review behavior, not formatting. Do not modify the change unless the user also asks for fixes.
Establish the review scope
- Read the repository
AGENTS.md,CONTRIBUTING.md, and any narrower instructions. - Use the user-specified base when present. Otherwise use the pull request base, or the merge base with
origin/mainfor local work. Include staged, unstaged, and relevant untracked files. - Classify changed files by subsystem and identify contracts that cross subsystem boundaries.
- Read only the implementation paths, tests, migrations, and documentation needed to verify changed behavior.
Audit the change
Trace each changed behavior from entry point to durable side effect and cleanup. Check:
- Correctness on success, error, retry, cancellation, timeout, and empty-state paths.
- Authentication, authorization, owner/session scope, input validation, secret handling, and sensitive logging.
- Concurrency, ordering, idempotency, reconnects, goroutine or subscription cleanup, Flutter disposal, and Python session shutdown.
- Backward compatibility for APIs, stored data, clients, agents, deployments, and rolling upgrades.
- Tests that exercise the actual entry path and at least one meaningful failure or negative-control path.
Apply subsystem-specific scrutiny only where relevant:
backend: request boundaries, transactions, migrations, NATS subscriptions, resource ownership, and service-to-service failures.frontendandadmin: state isolation, mounted/disposal safety, stale async results, platform differences, user-visible failure states, and payload compatibility.voicebridge: call-to-node ownership, start/mute/unmute/stop semantics, duplicate sessions, reconnects, and cleanup.k8s: credential safety, selectors, probes, configuration defaults, rollout compatibility, and rendered manifests.
For REST, WebSocket, NATS, database, agent-adapter, or voice changes, inspect every producer and consumer. Verify field meaning, optionality, defaults, ordering, error behavior, and version skew on both sides. Treat this as part of the review; do not create a separate protocol-review process.
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.
- 2d ago First seen · 43 lines · 70 tokens per session scan A b7f77d1153e3
grix-code-review is a skill published in the GitHub repository askie/grix (130 stars, last pushed 3d ago), licensed Apache-2.0. It adds 70 tokens to every session and 634 once invoked, about $0.0003 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 skills, from other repositories
skill-packager
Authors Agent Skills v1.0 packages (SKILL.md plus references/scripts), runs packageskill to produce a standards-compliant zip, and uses installskill to add skills from HTTPS, registry, workspace, or an uploaded archive. Use when the user wants to turn documentation, workflows, or code into a portable skill, export a…
document-processor
Guidance for processing documents, extracting content, and transforming structured information. Use when the user asks to process, parse, extract, or transform document content such as PDFs, Word files, or spreadsheets.
workflow-helper
Guidance for creating, managing and executing workflow automations that chain multiple tools and agents together. Use when the user asks about building, listing, running or composing workflows and automated task pipelines.
attendance-signin-sheet
Generate printable attendance / 签到表 spreadsheets from name lists. Use when the user asks for 签到表, attendance sheet, meeting sign-in table, or similar printable roster tables (not full payroll attendance scoring unless asked).
data-analyzer
Guidance for analyzing structured data, generating statistics and producing data-driven insights. Use when the user asks to analyze data, compute statistics, find patterns, or generate analytical reports.
procurement-audit
Review procurement contracts and purchase packages against uploaded compliance rules (招标/采购制度). Use for 采购审核, contract compliance checklists, or procurement statistics rollups.