Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add Redtropig/harness-anchor/plugin install harness-anchorWrote 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/redtropig/harness-anchor/init-verification)<a href="https://agentmods.dev/skills/redtropig/harness-anchor/init-verification"><img src="https://agentmods.dev/badge/skills/redtropig/harness-anchor/init-verification/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/redtropig/harness-anchor/init-verification"><img src="https://agentmods.dev/badge/skills/redtropig/harness-anchor/init-verification.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.00037 | $0.01546 |
| Opus 5 | $0.00018 | $0.00773 |
| Sonnet 5 | $0.00007 | $0.00309 |
| Haiku 4.5 | $0.00004 | $0.00155 |
Grade A, and why
init-verification 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 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.
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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Init Verification
Before writing any code, prove the environment is healthy. Anthropic's Nov 2025 harness guidance: the initializer agent runs init.sh, then the coding agent picks up — health is verified BEFORE work begins.
When to invoke
- First action of every fresh session
- After
git checkoutto a different branch - After dependency changes (package.json / Cargo.toml / etc. modified)
- After OS / toolchain updates
- When a previously-working command suddenly fails
- Before claiming a feature done (re-verify in case of drift)
Procedure
-
Locate
init.shin project root.- Missing → tell the user to run
/anchorto scaffold one. Do not proceed.
- Missing → tell the user to run
-
Run it.
bash init.shCapture stdout+stderr.
-
Interpret exit code.
Exit Meaning Action 0 All checks passed Proceed with work 1 One or more checks failed Stop. Fix the reported issues before doing anything else. other Unexpected Read output; either fix init.sh itself or report to user -
On failure: list the specific missing files/tools, propose fixes one at a time:
- Missing tool (e.g.
cmake not found) → suggest install command appropriate to platform (brew install cmakeon macOS) - Missing state file (e.g.
feature_list.json missing) → suggest/anchor - Missing build artifact (e.g.
compile_commands.json missing) → suggest correct configure command
- Missing tool (e.g.
-
After fix: re-run
init.sh. Repeat until exit 0. Then continue work. -
Re-check inherited NEGATIVE capability conclusions.
A line in
AGENTS.mdshaped likesearched <scope>, not found (as of <date>)records what a past session observed. It is not a current fact. Re-check each one. This step, by construction, only ever re-checks conclusions already recorded as absent, so it always takes the discovery chain's NOT_FOUND path — the slower, full-ladder search, not the fast PATH hit — and that path measures ~1.6s for two tools (51-entry PATH):
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 · 129 lines · 37 tokens per session scan A 10f0ccdf4ffc
init-verification is a skill published in the GitHub repository Redtropig/harness-anchor (13 stars, last pushed 1mo ago), licensed MIT. It adds 37 tokens to every session and 1,546 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
ci-debug
Diagnose a failing CI run against an 11-pattern playbook. Classifies the failure, cites the relevant memory entry, proposes the exact fix command — but NEVER applies without explicit user approval. Use when a specific PR check or GitHub Actions run failed and you want a diagnosis instead of speculation. Don't use for…
paired-probe
Refuse a verdict a probe did not earn. Runs a check where the fault IS present and where it is NOT, and blocks the answer when both arms print the same thing, because a check that cannot disagree with you has measured nothing. Also catches the zero-sample sweep that reads as "clean" and the swallowed error that reads…
simplifier
Replatform mode ("lift, tinker, and shift") — simplify a 1:1-lifted legacy system in place: modernize code and remove external dependencies, one pass at a time, each bracketed by characterization-tests replays, structure preserved. Owns the stack-neutral pass discipline; the transformation catalog and dependency…
error-handling
Apply error handling and recovery patterns in JavaScript/TypeScript or Node.js. Use when implementing error handling, retry logic, or when the user mentions domain errors, error recovery, error escalation.
implement
Implement a feature or fix with automatic validation.
error-handling
Validate error handling completeness across languages.