agentsclimarketplace

Context init

Skill lifan-builds/context-harness/context-init

Lightweight durable context for AI coding agents: 4 files, 9 rules, companion skills, and scripts that let agents self-iterate inside your workflow.

Install
npx -y skills add lifan-builds/context-harness --skill context-init

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Initialize context-harness in a new repository by creating AGENTS.md, CONTEXT.md, NOW.md, and optional PLAN.md.

SKILL.md

2.5 KB, 551 tokens by cl100k_base, as published. Nobody here has run it

Context Init

Use this only when a repository has no context-harness layout and should get a fresh AGENTS.md, CONTEXT.md, NOW.md, and optional PLAN.md.

If a repository already has partial, stale, or custom context-harness files, use explicit context-upgrade instead. Init does not repair existing layouts.

Goal

Create the smallest durable context layer that lets future agents catch up:

  • AGENTS.md as the automatic Context Contract
  • CONTEXT.md for project facts, operating constraints, language, relationships, and lessons
  • NOW.md for the current focus
  • PLAN.md only when there is an active multi-step task

Generated AGENTS.md and CONTEXT.md must include <!-- context-harness:schema v3 --> so future skill versions can detect the layout.

Init Flow

  1. Run the generator:

    node scripts/context-gen.js

    If running from an installed companion skill directory, use:

    node ../scripts/context-gen.js

  2. Present the generated ## Suggested Operating Constraints and ## Suggested Workflow as a starting point.

  3. Ask the user to keep only project-specific constraints a future agent would not infer from code or docs, and confirm workflow verification commands.

  4. Write CONTEXT.md, NOW.md, and AGENTS.md from the templates in the root context-harness skill.

  5. Install context-harness runtime scripts into the target repo:

    node <context-harness-skill-dir>/scripts/install-project.js

  6. Run node scripts/context-index.js update so AGENTS.md has a generated high-level index and .context-harness/ has retrieval cards.

  7. Ask whether there is a multi-step task. If yes, create PLAN.md.

Guardrails

  • Use PLAN.md Done Criteria and CONTEXT.md Workflow Verification instead of durable project-wide objectives.
  • Do not repair existing layouts here; route partial, stale, or custom context-harness files to explicit context-upgrade.
  • Keep generated files short enough to be read every session.
  • Keep AGENTS.md small: contract plus generated CONTEXT.md index and a pointer to hydrate.
  • Runtime scripts are project-local after init, so AGENTS.md can refer to node scripts/context-index.js update and hydrate.
  • Do not create ADRs unless the target project already has an ADR workflow.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 326,984. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.