Borrowing it
Nothing to install: this file belongs to AnEntrypoint/freddie. 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/AnEntrypoint/freddie/main/.agents/skills/freddie-pre-push-checks/SKILL.mdgit clone --depth 1 https://github.com/AnEntrypoint/freddieWrote 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/anentrypoint/freddie/freddie-pre-push-checks)<a href="https://agentmods.dev/skills/anentrypoint/freddie/freddie-pre-push-checks"><img src="https://agentmods.dev/badge/skills/anentrypoint/freddie/freddie-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/anentrypoint/freddie/freddie-pre-push-checks"><img src="https://agentmods.dev/badge/skills/anentrypoint/freddie/freddie-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.01350 |
| Opus 5 | $0.00033 | $0.00675 |
| Sonnet 5 | $0.00013 | $0.00270 |
| Haiku 4.5 | $0.00007 | $0.00135 |
Grade A, and why
freddie-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 3d 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
FREDDIE Pre-Push Checks
Use this skill to run relevant local evidence once before a freddie 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 runs one check, staged whitespace (git diff --cached --check); there is no pre-push hook. The workspace has no automated test suite and no build step; verification is live execution against the real running system.
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 automated test suite and no universal local baseline beyond the whitespace hook. Every behavior change is verified live — boot the real composition or app, drive the actual change, and read the real output — same turn as the work. A diff's own claim about itself is not evidence.
- Model-, editor-, CLI-, or terminal-visible output: boot the real example or app that owns the output and drive it.
- Package manifests, public exports, or the published file set: run
pnpm run publint, which validates each package's real relative imports against its ownpackage.jsonfilesarray. - Real provider or agent behavior: run the relevant demo (
pnpm run demo:cordis,pnpm run demo:acp,pnpm freddie --profile headless "...") 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.
- 3d ago First seen · 99 lines · 66 tokens per session scan A c80e08187a50
freddie-pre-push-checks is a skill published in the GitHub repository AnEntrypoint/freddie (0 stars, last pushed 2d ago), licensed MIT. It adds 66 tokens to every session and 1,350 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-09-06.
Other skills, from other repositories
github-copilot-upgrader
Use this to update the Github Copilot CLI/SDK.
workflow-patterns
Use this skill when implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, or understanding the verification protocol.
meta-pre-commit-quality-gate
Run three quality gates (ruff + mypy + pytest) in parallel over the staged diff, then arbitrate a single BLOCK/APPROVE verdict. Use before committing changes locally when you want a comprehensive pre-commit gate beyond per-file linting — exactly the same gate set CI enforces.
nw-quality-framework
Quality gates - 11 commit readiness gates, build/test protocol, validation checkpoints, and quality metrics.
strict-tdd
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.
Changelog Test Mapper
Map changelog entries and release notes to affected test cases, ensuring every user-facing change has corresponding test coverage verification.