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 easyinplay/harnessed --skill simplifygit clone --depth 1 https://github.com/easyinplay/harnessedWrote 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/easyinplay/harnessed/simplify)<a href="https://agentmods.dev/skills/easyinplay/harnessed/simplify"><img src="https://agentmods.dev/badge/skills/easyinplay/harnessed/simplify/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/easyinplay/harnessed/simplify"><img src="https://agentmods.dev/badge/skills/easyinplay/harnessed/simplify.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.00107 | $0.01409 |
| Opus 5.5 | $0.00043 | $0.00564 |
| Sonnet 5.5 | $0.00021 | $0.00282 |
| Haiku 4.5 | $0.00011 | $0.00141 |
Grade A, and why
verify-simplify 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 25d 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
verify-simplify workflow (v3)
Overview
1-phase sub-workflow mapping CLAUDE.md "Verify 阶段 — 末尾 code-simplifier" onto harnessed runtime (Phase v3.0-3.4 W0.13d — D-04 Stage ④ Verify 7 sub + Pattern A sub-workflow ship)。
| phase | id | upstream | model | capability | gate |
|---|---|---|---|---|---|
| 1 | 01-simplify |
mattpocock-skills | sonnet | {{ capabilities.code-simplifier.cmd }} |
judgments.stage-routing.verify-simplify-tail.fires |
Per-phase config loads from workflows/verify/simplify/workflow.yaml; engine 4-level gate
resolver evaluates phase.is_final_step == true via expr-eval — true 则 invoke
/code-simplifier (移除重复 / 多余逻辑), false 则 skip。verify 链末尾步骤,
sister verify-work v2 phase 08-code-simplifier verbatim 位置。
Capability refs
Sister workflows/capabilities.yaml entries:
code-simplifier— Bucket 1 mattpocock 高频招式 (impl: mattpocock-skills, cmd: /code-simplifier, fires_when: stage=='verify' AND is_final_step)
Gate ref
Sister workflows/judgments/stage-routing.yaml:
verify-simplify-tail.fires—phase.stage == 'verify' and phase.is_final_step == true
Routing rules
- ✅ 触发: verify chain 末尾步骤 (所有其他 verify sub 已 ship, 准备 code 简化收尾)
- ❌ 跳过: verify chain 中间步骤 (避免过早简化干扰后续 review)
How to invoke
!harnessed checkpoint intent verify-simplify
The banner above (when present) means this invocation is REGISTERED with the engine (an intent marker) — not yet compliant: the steps below (prompt → spawn → checkpoint complete) resolve it, and a per-turn
<workflow-intent>reminder persists until they run.
The numbered sequence below is the state machine — execute it with Bash. Do NOT improvise an equivalent flow from the Overview above: freelancing bypasses the engine (no ledger, no evidence guard). harnessed gives you the spawn-ready prompt; YOU spawn the subagent with a {{ host.native }} {{ host.spawn_subagent }} (keeps the session responsive + lets clarification round-trips reach the user).
What ships with it
2 files 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.
- 25d ago Changed · -1 lines 1c51e75900cd
- 1mo ago First seen · 82 lines · 107 tokens per session scan A 627736837f86
verify-simplify is a skill published in the GitHub repository easyinplay/harnessed (2 stars, last pushed 3d ago), licensed Apache-2.0. It adds 107 tokens to every session and 1,409 once invoked, about $0.0004 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-31.
Other skills, from other repositories
audit
Project health audit and health check — architecture, performance, tests, dependencies, code quality. Use when assessing overall project health, before releases, or after refactors.
issue-analyze
GitHub Issue and PR review thread deep analysis with Codex blind verdict. Use when: analyzing issue root cause, classifying problems, investigation planning, triaging PR review comments for actionability. Not for: fixing bugs (use bug-fix), code exploration (use code-explore). Output: classified analysis + verdict…
codebase-hygiene
Two-mode skill: (1) find semantic duplicates — functions doing the same thing under different names, invisible to copy-paste detectors; (2) deepen shallow modules — thin wrappers and pass-through layers that spread complexity. Advisory and read-only; changes route through BUILD with full gates.
deadeye-sweep
Applies the findings from /deadeye-review, /deadeye-pr, and /deadeye-guard, verifies the build, and re-scans on a loop until nothing (critical/high, or every severity with --all) survives. In --pr mode also answers the PR's own open review comments, replying and resolving.
lsp-investigate
Investigate code using LSP tools. Register a project, then use definitions, references, call hierarchies, type hierarchies, hover, and diagnostics to understand code structure, trace bugs, and assess change impact.
daily-prevention
Use this skill to help a developer keep day-to-day code simple, maintainable, and robust — through automatable prevention (linters, type checkers, static analysis, and — for what static analysis structurally can't catch — AI-assisted review skills) rather than after-the-fact fixes. Trigger on "how do I keep this…