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 CUHK-AIM-Group/NeuroClaw --skill harness-coregit clone --depth 1 https://github.com/CUHK-AIM-Group/NeuroClawWrote 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/cuhk-aim-group/neuroclaw/harness-core)<a href="https://agentmods.dev/skills/cuhk-aim-group/neuroclaw/harness-core"><img src="https://agentmods.dev/badge/skills/cuhk-aim-group/neuroclaw/harness-core/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/cuhk-aim-group/neuroclaw/harness-core"><img src="https://agentmods.dev/badge/skills/cuhk-aim-group/neuroclaw/harness-core.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00113 | $0.02756 |
| Opus 5 | $0.00056 | $0.01378 |
| Sonnet 5 | $0.00023 | $0.00551 |
| Haiku 4.5 | $0.00011 | $0.00276 |
Grade A, and why
harness-core 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 12d 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 — 417 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Harness Core Library
Overview
harness-core is the base SDK / plugin library for implementing NeuroClaw harness engineering standards across all skills.
Instead of reimplementing validation, checkpointing, logging, and drift detection in every skill, harness-core provides reusable, well-tested Python classes and utilities that all other skills can import and extend.
Key design principle: Harness-awareness is not optional — every data-processing, model-execution, and experiment-running skill should import from this library to achieve:
- Standardized self-verification across all skills
- Reproducible, hash-verified experiment logs
- Automatic checkpoint/resume capability
- Drift detection and anomaly alerts
- Privacy-preserving audit trails
When to Use This Skill
Directly: Rarely — this is a library, not a user-facing skill.
Indirectly (as a dependency):
- When developing or modifying skills like
experiment-controller,run_models,fmri-skill,smri-skill, etc. - When using skills that have been enhanced to support harness engineering
- When integrating external tools or models into NeuroClaw (inherit harness patterns)
Core Components
1. HarnessController (Main Orchestrator)
Purpose: Manages the full lifecycle of harness-compliant execution.
Usage:
from skills.harness_core import HarnessController
controller = HarnessController(
task_name="fmri_preprocessing",
session_id="exp_20260405_143000",
checkpoint_dir="./checkpoints",
log_dir="./logs"
)
# Automatic environment snapshot capture
controller.initialize()
# Define task phases
controller.add_phase("quality_check", description="Verify input BIDS compliance")
controller.add_phase("preprocessing", description="Apply fMRI preprocessing")
controller.add_phase("feature_extraction", description="Extract ROI time series")
# Execute with auto-checkpointing
for phase_name in ["quality_check", "preprocessing", "feature_extraction"]:
try:
phase = controller.get_phase(phase_name)
result = execute_phase(phase.name) # User-defined function
controller.record_phase_success(phase_name, result)
controller.save_checkpoint(f"after_{phase_name}")
except Exception as e:
controller.record_phase_failure(phase_name, str(e))
controller.save_checkpoint(f"failed_{phase_name}")
raise
# Auto-generates: audit_report.md, environment_manifest.json, checkpoints/
What ships with it
1 file 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.
- 12d ago First seen · 417 lines · 113 tokens per session scan A fe7831e467f7
harness-core is a skill published in the GitHub repository CUHK-AIM-Group/NeuroClaw (85 stars, last pushed 5d ago), licensed MIT. It adds 113 tokens to every session and 2,756 once invoked, about $0.0006 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…