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 shimo4228/claude-harness --skill context-syncgit clone --depth 1 https://github.com/shimo4228/claude-harnessWrote 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/shimo4228/claude-harness/context-sync)<a href="https://agentmods.dev/skills/shimo4228/claude-harness/context-sync"><img src="https://agentmods.dev/badge/skills/shimo4228/claude-harness/context-sync/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/shimo4228/claude-harness/context-sync"><img src="https://agentmods.dev/badge/skills/shimo4228/claude-harness/context-sync.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.00071 | $0.04396 |
| Opus 5.5 | $0.00028 | $0.01758 |
| Sonnet 5.5 | $0.00014 | $0.00879 |
| Haiku 4.5 | $0.00007 | $0.00440 |
Grade A, and why
context-sync scanned grade A 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
`curl` loop here. How it starts
The opening of the file, as written. The whole thing — 294 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context Sync
Detect and fix documentation role overlaps, stale content, and missing context files across your project. Ensures every piece of project knowledge lives in exactly one place with a clear purpose.
Why This Matters
In LLM-driven development, organizing concepts is implementation. Markdown carries the same weight as executable code — a stale number in CLAUDE.md or a misplaced design rationale silently degrades every AI-assisted session that reads it. Context consistency is not housekeeping; it is a prerequisite for core concepts to reach the system without noise.
When to Use
- After a major refactoring or architecture change
- When CLAUDE.md / .cursorrules has grown large and feels cluttered
- When you suspect docs are out of date with the code
- When starting a new project and want proper doc structure from the beginning
- When design decisions are buried in context files instead of formal records
- Periodically (monthly or per milestone) as documentation hygiene
Core Concept: Four Documentation Roles
Every project document should serve exactly one of these four roles. Overlap causes drift and contradiction.
| Role | Purpose | What belongs here | Examples |
|---|---|---|---|
| Context | How to work in this project | Conventions, build/test commands, policies | CLAUDE.md, .cursorrules, AGENTS.md |
| Architecture | What concepts the code defines and how they relate (concept-level) | Domain entities / relationships (concept-level triples); at most a short hand-written overview | graph.jsonld, docs/architecture/ |
| Decisions | Why the code is this way | Trade-offs, rejected alternatives, rationale | docs/adr/ |
| External | What this project is | Purpose, quickstart, API overview | README.md |
Do not store file-level structure: "which file X lives in / who calls whom" is derived from the code every time (Claude Code's LSP tool / an import graph from grimp etc.). Store only the concept layer (graph.jsonld — "what X is / how X and Y relate"), design rationale (ADRs), and a pipeline's stage layout (the header comment of the script that runs it). A hand-written module map is a mirror of derivable structure; it pays a sync cost on every source commit while nobody reads it. Your knowledge-graph skill (the author's harness uses jsonld-knowledge-graph) holds the canonical details of the role boundaries.
What ships with it
8 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.
- 9d ago Changed · +6 lines 205edb4667d4
- 10d ago Changed · +2 lines 1cae46fca0e3
- 11d ago Changed · +20 tokens per session 40cf758746f8
- 13d ago Changed · +3 lines · -1 tokens per session e317af768138
- 24d ago Changed 089a189060f9
- 25d ago Changed · -1 lines ff0b0e67d0b0
- 1mo ago Changed 2715c4f02ac5
- 1mo ago Changed · -1 lines 10d33d1f1de1
- 1mo ago Changed · -63 lines 1877e88e4852
- 1mo ago First seen · 348 lines · 52 tokens per session scan A 1f85a3dd8b69
context-sync is a skill published in the GitHub repository shimo4228/claude-harness (3 stars, last pushed 2d ago), licensed MIT. It adds 71 tokens to every session and 4,396 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
agent-adoption-triage
Five-question triage for routing AI work to the right architecture — script, algorithmic search, LLM workflow, or autonomous agentic loop — before any agent is built. Use when someone says "let's build an agent for X", when deciding whether a use case actually needs an autonomous agent, when reviewing an agent…
git-commit
A guided Git commit workflow that examines changes and creates a commit message using the Conventional Commits format, a shared style for labeling changes such as features, fixes, tests, or documentation.
zod
Zod v4 best practices, patterns, and API guidance for schema validation, parsing, error handling, and type inference in TypeScript applications. Covers safeParse, object composition, refinements, transforms, codecs, branded types, v3→v4 migration, and testing schemas with Jest or Vitest. Baseline: zod ^4.6.0. Triggers…
pi-triage
Decide whether an upstream pi change needs porting to the Go port. Use when assessing upstream commits/PRs ("should we port X?"), or as the triage stage of /pi-sync. Outputs a WHY/WHAT/SCOPE verdict per change.
trailhead-work
Skill "trailhead-work" from ToRvaLDz/trailhead, covering load first, in order, routing: verb to engine, work the map: work, work one ticket whole, without splitting: quick and pause, resume, split.
pi-parity-review
Adversarially verify that a ported change is faithful to the original pi implementation (TS source + published npm build). Use after porting upstream pi changes, or standalone on any area of this repo ("is X faithful to pi?").