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 instructions/gizele1/harness-init/claude-mdgit clone --depth 1 https://github.com/Gizele1/harness-initWrote 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/instructions/gizele1/harness-init/claude-md)<a href="https://agentmods.dev/instructions/gizele1/harness-init/claude-md"><img src="https://agentmods.dev/badge/instructions/gizele1/harness-init/claude-md.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 | $0.00299 | $0.00299 |
| Opus 5 | $0.00150 | $0.00150 |
| Sonnet 5 | $0.00060 | $0.00060 |
| Haiku 4.5 | $0.00030 | $0.00030 |
Grade A, and why
harness-init CLAUDE.md 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 5d 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
Development Instructions
Project overview
harness-init is a Claude Code plugin (v1.1.0) that scaffolds agent-ready repos. It is a documentation-only project — no app code, no runtime, no dependencies.
Rules
- Always update README.md and README_CN.md together. Same sections, same order, same data.
- Keep version in sync across:
plugin.json,marketplace.json,SKILL.mdfrontmatter. - SKILL.md is the source of truth for skill behavior. README describes it for humans.
- Reference files in
skills/harness-init/references/are loaded on-demand by SKILL.mdReaddirectives. Every directive must point to an existing file. - Run
bash scripts/check-docs.shbefore committing to catch consistency issues. - Run
claude plugin validate .to verify plugin structure.
Commit conventions
- Use descriptive commit messages: what changed and why
- Reference issue numbers when fixing issues (e.g., "Fixes #29")
- Keep PRs focused: one concern per PR
File editing guidelines
- Do not add features or phases to SKILL.md without updating README.md, README_CN.md, and relevant reference files
- When adding a new reference file, add a corresponding
Read references/filename.mddirective in SKILL.md - Phase count in README tables must match SKILL.md (currently 8: Phase 0-7)
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.
- 5d ago First seen · 27 lines · 299 tokens per session scan A 74ae9a08b95e
harness-init CLAUDE.md is an instructions file published in the GitHub repository Gizele1/harness-init (53 stars, last pushed 5mo ago), licensed MIT. It adds 299 tokens to every session, about $0.0015 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.