Borrowing it
Nothing to install: this file belongs to singula-ai/alego. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/singula-ai/alego/main/.agents/skills/alego-pre-push-checks/SKILL.mdgit clone --depth 1 https://github.com/singula-ai/alegoWrote 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/singula-ai/alego/alego-pre-push-checks)<a href="https://agentmods.dev/skills/singula-ai/alego/alego-pre-push-checks"><img src="https://agentmods.dev/badge/skills/singula-ai/alego/alego-pre-push-checks/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/singula-ai/alego/alego-pre-push-checks"><img src="https://agentmods.dev/badge/skills/singula-ai/alego/alego-pre-push-checks.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00066 | $0.02361 |
| Opus 5.5 | $0.00026 | $0.00944 |
| Sonnet 5.5 | $0.00013 | $0.00472 |
| Haiku 4.5 | $0.00007 | $0.00236 |
Grade A, and why
alego-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 6d 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.
This is a copy
88% identical to dsh-pre-push-checks — 14 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ALEGO Pre-Push Checks
Use this skill to run relevant local evidence once before an alego push. The sole ordering exception is gh stack sync, which may publish a cascading rebase before the rewritten layers can be validated; validate them immediately afterward and do not merge until the evidence passes. Git hooks are intentionally narrow: pre-commit fixes staged lint, checks staged whitespace, and guards vendored-source metadata; pre-push runs only the incremental repository typecheck. CI owns exhaustive coverage and the platform matrix.
Inspect the outgoing change
- Confirm the checkout and branch.
git status --short --branch
git rev-parse --show-toplevel
- Verify the live PR base or stack parent, fetch that ref, and inspect the complete scope against it.
pnpm --silent run change-scope --base <verified-base-ref>
The command never guesses or fetches a base. Supply the ref verified from current remote or stack state; use --head <ref> when inspecting a commit other than HEAD. Its versioned JSON records committed paths relative to the resolved merge base, while staged, unstaged, and untracked paths describe the current worktree. After merging a changed base, rerun the report, reassess which behavior the combined scope can affect, and rerun only checks invalidated by the merge.
Select relevant evidence
There is no universal local baseline beyond the hooks. Every behavior change needs the narrowest available test or purpose-built check that would fail for its regression; add broader checks only for surfaces the diff actually reaches.
When the outgoing change adds or changes a resource-owning or asynchronous test, fixture, helper, or CI execution path, use alego-ci-test-reliability first to decide whether restoration, negative-control, quiescent-teardown, or concurrent-process evidence applies. This skill still selects the commands and avoids repeating evidence that already passed.
- Package or script behavior: run the owning Vitest file or focused test name. Add adjacent package tests when a shared contract changes; leave repository-wide coverage to CI unless the change is genuinely cross-cutting or the user requests it.
- Remote mock typing: unbuilt
anyis an explicit local fallback, not strict evidence. Runpnpm run typecheckbefore handing off Remote/mock changes; rebuild missing, stale, or partial generated declarations before diagnosing remaining errors. Keep the exception in the test proxy, never in production Remote types, ambient flags, or copied signatures. - Documentation, Agent Notes, catalogs, or doc-linked comments: run
pnpm run doc-sync; run full lint when the documentation workflow requires it. - Model-, editor-, CLI-, or terminal-visible output: run the focused keyless snapshot or real runnable-example scenario that owns the output.
- Expected-output placement: a test whose selected recorded Session generation is replay input and expected persisted output belongs under top-level
snapshots/, withsnapshot.ymlnaming its shippedalegoprofile and composition/header pin. Canonical parent files aresession[.vN].jsonl, children aresession.<ordinal>[.vN].jsonl, and the harness selects the highest generation per role. ARIA, geometry, generator, CLI, and unit expectations without that Session round trip stay beside their owning test undertests/expected/; do not place them insnapshots/or give them a*.snapshot.tsowner. Use the owningtest:expected,test:web, ortestlane. - Profile and configuration placement: cross-package behavior of a shipped
alegoprofile belongs underapps/cli/tests/profiles/; a package-specific Loader composition belongs under that package'stests/fixtures/. User-facing optional overlays live underapps/cli/config/examples/and pair with a guide underdocs/user/. - Package manifests, public exports, build configuration, worker/bin entries, or built runtime paths: run
pnpm run build, the relevant hygiene checks, and the owning built-artifact smoke. - Repository test and script types:
pnpm run build:artifactschecks package projects only. Before claiming completion of TypeScript changes, runpnpm run build:checkafter the latestbuild:artifacts, or runpnpm run build;build:checkreads the existingbuild:artifactsoutput and never rebuilds it. - Real provider or agent behavior: run the relevant
pnpm run test:e2etarget when credentials are available; never print secrets.
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.
- 6d ago Changed · +1 lines 7e020e295dfe
- 26d ago Changed · +8 lines bcc851d7fc6a
- 1mo ago Changed · +1 lines e3a5b17993b5
- 1mo ago Changed · +4 lines 39678b51a876
- 1mo ago First seen · 124 lines · 66 tokens per session scan A 1be30ea65664
alego-pre-push-checks is a skill published in the GitHub repository singula-ai/alego (109 stars, last pushed 3d ago), licensed MIT. It adds 66 tokens to every session and 2,361 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 88% identical to dsh-pre-push-checks, differing in 14 lines, and is treated as a copy.
Other skills, from other repositories
agent-harness-testing
A testing method for coding tasks in unfamiliar projects. It first discovers how the project is tested, then uses a failing check followed by a passing check to verify a change.
visual-acceptance
A visual final-review method for user-interface changes. It checks the rendered result with repeatable screenshots, pixel values, computed styles, and CSS layering checks across themes.
shipping-a-pr
Use when finished work needs to ship as a pull request, or when creating, syncing, updating metadata, checking status, monitoring CI, or addressing review comments on a PR. Not for reviewing a PR you are not shipping.
safe-extraction
Apply when extracting code from a large monolith file into submodules. Covers barrel re-exports, internals DI seam proxy patterns, CI invariant allowlist updates, and cross-file test verification. Prevents CI failures, broken imports, and test regressions from code extraction.
merge-queue-readiness
Pre-queue merge-group CI simulation. Triggered before adding a PR to a GitHub merge queue. Prevents merge-queue kick-outs from integration test failures.
release-notes
Draft user-facing release notes from a git log range. Trigger when the user asks for "release notes", "changelog entry", or "what shipped this week" with a git ref range. Output is markdown sections grouped by Features / Fixes / Breaking with PR links.