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-pre-push-checksnpx skills add askie/grix --skill grix-pre-push-checksgit clone --depth 1 https://github.com/askie/grixWrote 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/askie/grix/grix-pre-push-checks)<a href="https://agentmods.dev/skills/askie/grix/grix-pre-push-checks"><img src="https://agentmods.dev/badge/skills/askie/grix/grix-pre-push-checks.svg" alt="Measured on agentmods" 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 | $0.00064 | $0.00716 |
| Opus 5 | $0.00032 | $0.00358 |
| Sonnet 5 | $0.00013 | $0.00143 |
| Haiku 4.5 | $0.00006 | $0.00072 |
Grade A, and why
grix-pre-push-checks 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 5d 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 — 35 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Grix Pre-push Checks
Choose checks from the changed paths. Start with a focused check and broaden only when the change crosses packages, services, clients, or contracts.
Determine the change set
- Read the repository
AGENTS.mdandCONTRIBUTING.md. - Use the user-specified or pull request base when available; otherwise compare with the merge base of
origin/mainand include local staged, unstaged, and relevant untracked files. - Group changed files by subsystem and select checks below. A cross-component contract change requires checks for every affected producer and consumer.
Select checks
backend/**: Frombackend, rungo testfor the changed package first. For cross-package changes, runAIBOT_TEST_NATS_URL=nats://127.0.0.1:1 go test ./...; addgo vet ./...andgo build ./...when shared contracts or command entrypoints change.frontend/**: Fromfrontend, run the closestflutter test <test-file-or-directory>. For shared state, navigation, protocol, or multi-feature changes, addflutter analyze --no-fatal-infosandflutter test --timeout 90s.admin/**: Fromadmin, run the closestflutter test <test-file-or-directory>. Addflutter analyze --no-fatal-infosand the fullflutter testwhen shared code or multiple features change.voicebridge/**: Fromvoicebridge, run the changed module'spython -m unittest <test_module> -v. For shared bridge behavior, run the non-network unit-test set documented invoicebridge/README.md.k8s/**: Render each affected base withkubectl kustomize <directory>whenkubectlis available. Inspect the output for secrets, selectors, probes, ports, image references, and missing configuration. Never apply manifests as a validation step..agents/skills/**: Run the skill creator'squick_validate.pyagainst each changed skill directory and inspect its metadata for accurate triggering.- Documentation and decision notes only: check links, paths, commands, and consistency with current code. Do not run application-wide tests solely for prose changes.
- Repository scripts or workflows: run the narrow script test or syntax check that exercises the changed path. Do not invoke publishing, deployment, release, upload, or credentialed jobs.
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.
- 5d ago First seen · 35 lines · 64 tokens per session scan A 324f31293842
grix-pre-push-checks is a skill published in the GitHub repository askie/grix (137 stars, last pushed today), licensed Apache-2.0. It adds 64 tokens to every session and 716 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
vigilante-create-issue
Help a human author write an implementation-ready GitHub issue that Vigilante can execute reliably.
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.
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…
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.