What is noslop-setup?

A setup guide for installing noslop quality checks in an existing Git repository. Noslop is a tool that checks code and repository changes through hooks, continuous integration, and agent guardrails.

Use it to install or verify Git hooks, CI workflows, protected-file rules, Claude Code settings, and agent instructions.

It creates consistent checks before commits, pushes, and pull requests while blocking selected ways to bypass them.

noslop-setup — Skill for Claude Code and Codex by 45ck/skill-harness

Install

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.

Any agent

npx skills add 45ck/skill-harness --skill noslop-setup

Clone the repo

git clone --depth 1 https://github.com/45ck/skill-harness

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/45ck/skill-harness/noslop-setup/github.svg)](https://agentmods.dev/skills/45ck/skill-harness/noslop-setup)

Your own site

<a href="https://agentmods.dev/skills/45ck/skill-harness/noslop-setup"><img src="https://agentmods.dev/badge/skills/45ck/skill-harness/noslop-setup/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/45ck/skill-harness/noslop-setup"><img src="https://agentmods.dev/badge/skills/45ck/skill-harness/noslop-setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 30 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 601 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00030	$0.00601
Opus 5.5	$0.00012	$0.00240
Sonnet 5.5	$0.00006	$0.00120
Haiku 4.5	$0.00003	$0.00060

Measured 1mo ago against content hash 996752f70863, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

noslop-setup 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 1mo 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.

packs/noslop-skills/skills/noslop-setup/SKILL.md · 52 lines

What it actually says

Use this skill when setting up noslop in a repository for the first time or verifying an existing install.

Installation:

install noslop globally: npm install -g @45ck/noslop
go to the target repo root (must be an existing git repo)
run noslop init — detects language pack, copies templates, wires git hooks via git config core.hooksPath .githooks
run noslop doctor to confirm all enforcement layers are present

What gets installed:

.githooks/pre-commit — runs noslop check --tier=fast before every commit
.githooks/pre-push — runs noslop check --tier=slow before every push
.githooks/commit-msg — rejects CI-bypass patterns and enforces Conventional Commits
.github/workflows/quality.yml — required CI check on every PR and push to main
.github/workflows/guardrails.yml — blocks PRs touching protected files without noslop-approved label
.claude/settings.json — denies --no-verify, --force, and edits to protected paths
.claude/hooks/pre-tool-use.sh — intercepts every Claude Code tool call, blocks bypass patterns
AGENTS.md — plain-language rules for AI agents working in the repo

Configuring AGENTS.md rules:

The generated AGENTS.md must state:

run noslop check --tier=fast before every commit
run noslop check --tier=slow before opening a PR
never use git commit --no-verify
never use git push --force without explicit human approval
never use [skip ci], skip-checks, or SKIP_CI
do not weaken quality gates in .githooks/, .github/workflows/, or .claude/hooks/
additive changes to infrastructure files are allowed; removal or weakening is not

Two-tier check system:

--tier=fast — format, lint, spell check; must complete in seconds; runs on every commit
--tier=slow — type checking and full test suite; runs before every push and before opening a PR
--tier=ci — full pipeline; authoritative; cannot be skipped by any local trick

Verify setup:

noslop doctor

Expected healthy output confirms: hooks present and executable, core.hooksPath set, CI workflow files present, Claude settings and hook present.

For multi-pack repos, pass --pack repeatedly: noslop init --pack typescript --pack python.

Changes

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.

1mo ago First seen · 52 lines · 30 tokens per session scan A 996752f70863

Subscribe to this mod's changes

noslop-setup is a skill published in the GitHub repository 45ck/skill-harness (15 stars, last pushed 4mo ago), licensed MIT. It adds 30 tokens to every session and 601 once invoked, about $0.0001 per session on Opus 5.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.

CI and CD Claude Code DevOps and cloud Git and workflow agents claude codex codex-cli developer-tools

swarm-migrate

Cross-repo migration swarm — one coordinator + N parallel subagents (one per target repo) that apply the same transformation, open PRs, wait for CI, and report back to a shared JSON ledger. Coordinator handles topology, conflict auto-rebase, and stop-on-novel-failure. Use when bumping a shared dependency, rolling out…

yonatangross/orchestkit · 103 tokens

ship

Push, open a PR, and watch CI; land mode merges and cleans branches. Triggers "ship it", "create PR", "babysit CI", "land it", "fix CI and merge".

darkroomengineering/cc-settings · 45 tokens

zb-release-pipeline

Generate a GitHub Actions pipeline that builds a zb (Zero Dependencies Builder) project and publishes a GitHub Release with the produced JAR. Use whenever the user wants CI/CD, a build pipeline, a release workflow, or GitHub Actions for a zb-based Java project — phrases like "set up GitHub Actions for this zb…

AdamBien/airails · 148 tokens

noslop-setup