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 nexus-substrate/nexus-agents --skill pre-push-paritygit clone --depth 1 https://github.com/nexus-substrate/nexus-agentsWrote 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/nexus-substrate/nexus-agents/pre-push-parity)<a href="https://agentmods.dev/skills/nexus-substrate/nexus-agents/pre-push-parity"><img src="https://agentmods.dev/badge/skills/nexus-substrate/nexus-agents/pre-push-parity/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/nexus-substrate/nexus-agents/pre-push-parity"><img src="https://agentmods.dev/badge/skills/nexus-substrate/nexus-agents/pre-push-parity.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 69 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 80 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00130 | $0.01542 |
| Opus 5 | $0.00065 | $0.00771 |
| Sonnet 5 | $0.00026 | $0.00308 |
| Haiku 4.5 | $0.00013 | $0.00154 |
Grade A, and why
pre-push-parity 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pre-Push Parity Skill
Why
CI runs a strict superset of any local quality gate. When the local gate
(pnpm test, a make verify, etc.) is green but CI is red, the agent burns a
full ~3-minute cycle per discovery — push, wait, parse logs, fix, push — for a
check it could have run locally in seconds. On a multi-PR session that's hours.
The fix is to run the superset locally before git push.
Real failures that motivated this (#3073): ruff format --check (local gate
only ran ruff check) and a gitleaks false-positive on a *-Key-N test
fixture — neither was in the local gate, both cost CI cycles.
Principle
Whatever CI can fail you on, run it locally first. For the checks you can't run locally (SaaS / GitHub-native), know they exist and that they're the residual risk — don't be surprised by them.
Step 1 — Enumerate the repo's CI checks (do this first time in a repo)
# Job names + the commands each step runs:
grep -rEn 'name:|run:' .github/workflows/*.yml | grep -iv 'uses:'
Compare that list to your local gate. Anything CI runs that you don't is a parity gap. Write a memory pinning the delta so the next session starts informed (don't rediscover it):
ci-vs-local-gate-<repo>— CI runs these checks the local gate doesn't: X, Y, Z. Run them via<commands>before push. Z (CodeQL/Scorecard/Socket) can't run locally — residual risk.
Step 2 — Run the locally-runnable gates (nexus-agents)
In CI's order, fastest-feedback-first. Stop at the first failure, fix, restart.
| CI gate | Local command |
|---|---|
| Type Check | pnpm typecheck |
| Lint | pnpm lint |
| Test | pnpm test (CI uses pnpm test:coverage) |
| Build | pnpm build |
| Changeset Presence | pnpm exec tsx scripts/check-changeset.ts origin/main |
| Producer/Consumer (#3024) | pnpm exec tsx scripts/check-new-unused-exports.ts origin/main |
| Model String Drift | pnpm check:model-drift |
| Commit Messages | npx commitlint --from origin/main --to HEAD |
| Working-tree clean (#2872) | git status --porcelain (must be empty) |
| Secret scan | gitleaks detect --no-banner (runs in the pre-commit hook too) |
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 Changed 330a2f7d9c33
- 9d ago First seen · 131 lines · 130 tokens per session scan A 81603f22ab89
pre-push-parity is a skill published in the GitHub repository nexus-substrate/nexus-agents (18 stars, last pushed today), licensed MIT. It adds 130 tokens to every session and 1,542 once invoked, about $0.0006 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
Verification & Quality Assurance
Comprehensive truth scoring, code quality verification, and automatic rollback system with 0.95 accuracy threshold for ensuring high-quality agent outputs and codebase reliability.
migrate-vstest-to-mtp
Use this skill before answering, planning, or editing whenever .NET tests or CI are switching from VSTest to Microsoft.Testing.Platform (MTP), or an MTP migration behaves differently. Triggers include "switch from VSTest"; MSTest/NUnit/xUnit MTP enablement; OutputType=Exe only for test projects in…
ci
Configure Ginkgo for continuous integration — the recommended CLI flag set and the rationale for each flag (-r -p --randomize-all --randomize-suites --fail-on-pending --fail-on-empty --keep-going --cover --race --trace --json-report --timeout --poll-progress-after/-interval), invoking via go run to pin the CLI to…
playwright-ci
Production-ready CI/CD configurations for Playwright — GitHub Actions, GitLab CI, CircleCI, Azure DevOps, Jenkins, Docker, parallel sharding, reporting, code coverage, and global setup/teardown.
ci-maintenance-workflow
CI and GitHub Actions maintenance workflows — fix a failing test from a CI URL, fix a failing smoke test, add @pytest.mark.slow markers to slow tests, or review a PR against agent-checkable standards. Use when user asks to fix a failing test, fix a smoke test, mark slow tests, or review a PR. Trigger when the user…
test-setup
Scaffold the test framework and CI/CD pipeline for the project's engine. Creates the tests/ directory structure, engine-specific test runner configuration, and GitHub Actions workflow. Run once during Technical Setup phase before the first sprint begins.