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 wayne930242/straw-boss --skill create-great-harnessgit clone --depth 1 https://github.com/wayne930242/straw-bossWrote 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/wayne930242/straw-boss/create-great-harness)<a href="https://agentmods.dev/skills/wayne930242/straw-boss/create-great-harness"><img src="https://agentmods.dev/badge/skills/wayne930242/straw-boss/create-great-harness/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/wayne930242/straw-boss/create-great-harness"><img src="https://agentmods.dev/badge/skills/wayne930242/straw-boss/create-great-harness.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.00057 | $0.02155 |
| Opus 5 | $0.00028 | $0.01077 |
| Sonnet 5 | $0.00011 | $0.00431 |
| Haiku 4.5 | $0.00006 | $0.00215 |
Grade B, and why
create-great-harness scanned grade B with 1 finding 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 9d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
1. **Dedup check.** Read `<app-dir>/.claude/settings.json` if it exists. If a hook already covers the same event+matcher: How it starts
The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Overview
A lightweight agent-system bootstrap for an app that has none. CLAUDE.md is the only unconditional artifact. A guard hook or skill-authoring rule is included only when concrete project evidence or explicit confirmed scope calls for it.
Runs either inline (a user asked for this directly) or as a dispatched agent rooted in <app-dir> (init's own bootstrap step dispatches it via dispatching-work). The dispatch instruction, when present, states that scope was already confirmed and how to report completion — Task 1 and Task 6 both branch on whether that's the case.
Task 1: Confirm scope before writing anything
State the confirmed scope before writing: <app-dir>/CLAUDE.md, plus any optional hook or rule the user or dispatch instruction explicitly requested. The survey may support a recommendation for another artifact, but extending the confirmed scope remains a user-owned decision.
- Invoked directly by a user in this session: get explicit confirmation before proceeding — this writes into the app's own checkout, not just plugin state.
- Invoked as a dispatched agent: the dispatch instruction already states the scope was confirmed — that confirmation is
init's own per-app yes/skip ask. Don't ask again; there's no user in this session to answer, and re-asking just stalls aclaude -pdispatch. State the scope for the record and proceed straight to Task 2.
Verification: either the user confirmed in this session or the dispatch instruction carried the confirmed scope before any file was written.
Task 2: Survey the app for non-obvious content
Read what's actually there: package.json/pyproject.toml/Cargo.toml/go.mod/equivalent manifest, lockfile (which package manager — bun.lock vs package-lock.json vs pnpm-lock.yaml matters), top-level directory listing, existing README if short. Filter everything through one question: can a fresh Claude session derive this from reading the code, the manifest, or running ls? If yes, it doesn't belong in CLAUDE.md.
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.
- 9d ago First seen · 88 lines · 57 tokens per session scan B a7fdec983dba
create-great-harness is a skill published in the GitHub repository wayne930242/straw-boss (3 stars, last pushed yesterday), licensed MIT. It adds 57 tokens to every session and 2,155 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
push-ci
Push to remote and monitor CI. Validates branch safety, executes git push WITH explicit user approval, then monitors CI run status via gh CLI. Use when: user says 'push', 'push and watch CI', 'ship it', 'push-ci'. Not for: committing (use /smart-commit), creating PRs (use /create-pr), merging (use /merge-prep).
codex-setup
Initialize sd0x-dev-flow infrastructure for Codex CLI and other non-Claude agents. Generates AGENTS.md, installs the commit-msg hook, copies runner scripts. The pre-push gate is opt-in via --with-push-gate. Use when setting up a new project or after updating skills.
create-request
Create, update, or scan per-task request tickets for progress tracking. These are date-prefixed non-lifecycle docs under requests/, NOT feature-level requirements (use /req-analyze for those). Use when: tracking task progress, updating completion status, scanning incomplete requests, checking request status dashboard.…
smart-rebase
Smart partial rebase for squash-merge repositories. Auto-detect which commits to keep/drop when base branch was squash-merged into target. Use when: user says 'rebase', 'partial rebase', 'base already merged', 'smart rebase', or /smart-rebase. Not for: simple git rebase (the developer runs it — Claude never executes…
remind
A correction helper that checks which project rules or required steps were missed and loads the relevant guidance.
adr
Write an Architecture Decision Record (ADR) for a feature — Context / Decision / Status / Consequences / Alternatives, filed as docs/features/ /adr- - .md with a 3-digit zero-padded number. Handles the Superseded case: bidirectional linking when a new ADR replaces an old one. Use when: recording why an architectural…