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/45ck/skill-harness/noslop-setupnpx skills add 45ck/skill-harness --skill noslop-setupgit clone --depth 1 https://github.com/45ck/skill-harnessWrote 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/45ck/skill-harness/noslop-setup)<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="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.1 | $0.00030 | $0.00601 |
| Opus 5 | $0.00015 | $0.00300 |
| Sonnet 5 | $0.00006 | $0.00120 |
| Haiku 4.5 | $0.00003 | $0.00060 |
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 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.
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 viagit config core.hooksPath .githooks - run
noslop doctorto confirm all enforcement layers are present
What gets installed:
.githooks/pre-commit— runsnoslop check --tier=fastbefore every commit.githooks/pre-push— runsnoslop check --tier=slowbefore 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 withoutnoslop-approvedlabel.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 patternsAGENTS.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=fastbefore every commit - run
noslop check --tier=slowbefore opening a PR - never use
git commit --no-verify - never use
git push --forcewithout explicit human approval - never use
[skip ci],skip-checks, orSKIP_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.
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 First seen · 52 lines · 30 tokens per session scan A 996752f70863
noslop-setup is a skill published in the GitHub repository 45ck/skill-harness (15 stars, last pushed 2mo ago), licensed MIT. It adds 30 tokens to every session and 601 once invoked, about $0.0002 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
ship
Verify and publish by pushing, opening a PR, and watching CI; land mode merges then cleans branches. Triggers "ship it", "create PR", "/ship", "watch the PR", "babysit CI"; land mode "land it", "/ship land", "fix CI and merge".
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary. The complete landing pipeline.
ci-pipeline
Push current branch and return the pipeline tracking URL (GitLab or GitHub Actions).
ci-status
Show current pipeline status for the active branch (GitLab CI or GitHub Actions).
tfx-ship
Skill "tfx-ship" from tellang/triflux, covering tfx-ship — triflux 릴리즈 자동화, 배포 채널 (3개 현행 + 1개 future), 전제 조건, 기본 경로 — ci 릴리즈 (권장) and 권장 실행 — release.yml 디스패치.
deployment-patterns
Deployment workflows, CI/CD pipeline patterns, Docker containerization, health checks, rollback strategies, and production readiness checklists for web applications. Use when setting up deployment infrastructure or planning releases.