CLAUDE.md@hackathonA

CLAUDE.md@hackathon from oist/neuro-workflow is a CLAUDE.md file: the standing instructions Claude Code reads in that repo.

Install it, pinned
mdr add oist/neuro-workflow/hackathon/CLAUDE.md@git:20260619.fe65609

Pins git:20260619.fe65609 in mdr.lock. Pin the fingerprint instead.

Audit grade
A, 14 of 14 checks passed
Kind
CLAUDE.md file
Repository
oist/neuro-workflow
Path
hackathon/CLAUDE.md
Versions recorded
1
Latest version
git:20260619.fe65609, committed Jun 19, 2026
Size
12,931 bytes
Repository stars
19
License
a license file GitHub does not identify

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# NeuroWorkflow Hackathon — Agent Instructions

> **This file is the canonical participant instruction set. It is shipped as TWO identical files:**
> **`CLAUDE.md`** (read automatically by Claude Code) and **`AGENTS.md`** (read automatically by Codex).
> Each agent additionally auto-loads the `create-node` skill from its own path —
> `.claude/skills/create-node/SKILL.md` for Claude Code, `.codex/skills/create-node/SKILL.md` for Codex —
> which is the preferred path. This file is still written to be fully **self-contained** — an agent that
> has only this file (even on a small model) can still succeed.
> See `SETUP.md` for the exact per-agent environment setup and the prompt to give the agent.

---

## Who you are and what we are doing

You are an AI coding agent helping a neuroscientist at a hackathon. The participant has **their
own Python code** (a neuron/network model, a data-loading or analysis script — possibly messy and
unstructured). They do **not** know NeuroWorkflow internals.

**Your mission:** turn their Python code into one or more **NeuroWorkflow nodes**, wire those nodes
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint
mdr add oist/neuro-workflow/hackathon/CLAUDE.md@sha256:e8c74071320b7b68

The line at the top of this page pins the label git:20260619.fe65609, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.

Badge

mdr badge

[![mdr](https://markdownregistry.com/badge/art_rafcmuw6ib3izliv.svg)](https://markdownregistry.com/a/art_rafcmuw6ib3izliv)

4 badge image fetches in 30 days. What the badge shows.

Versions

The registry has recorded 1 version of this file, committed on Jun 19, 2026.

versioncommittedcommitsizeaudit
git:20260619.fe65609 latest2026-06-19 fe65609 12,931 BA view

Audit of the latest version

A  14 of 14 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
  • pass: Size between 200 bytes and 200 KB (12931 bytes)
  • pass: No zero-width or bidi control characters
  • pass: No instruction hidden inside an HTML comment
  • pass: No link to an exfiltration or paste host
  • pass: No credential-shaped string
  • pass: No instruction to send local credentials anywhere
  • pass: No text hidden with inline styles
  • pass: No prompt-injection phrasing
  • pass: No curl or wget piped into a shell
  • pass: No recursive delete of root, home or parent
  • pass: No instruction to read or print local credentials
  • pass: No base64 blob over 200 characters
  • pass: No link to a raw IP address
  • pass: No script tag

Source

GitHub

oist/neuro-workflow · 19 stars · license a license file GitHub does not identify · pushed 2026-10-22 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_rafcmuw6ib3izliv
GET https://markdownregistry.com/api/v1/resolve?ref=oist/neuro-workflow/hackathon/CLAUDE.md
GET https://markdownregistry.com/api/v1/blob/e8c74071320b7b686b8e61e6db36c11fa3ccef073e3c97d16afd7e4d0f6f35e9

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: what a CLAUDE.md file is · keeping AGENTS.md and CLAUDE.md in sync · which agent file does what.

More from oist/neuro-workflow

create-node SKILL.md skill
oist/neuro-workflow · .claude/skills/create-node/SKILL.md · Create a new NeuroWorkflow node (NEST / TVB / Brian2 / custom computation) following the NODE_CREATION_GUIDE.md…
git:20260619.e8f49ba · audit A · 19 stars
optimize-model-parameters SKILL.md skill
oist/neuro-workflow · .claude/skills/optimize-model-parameters/SKILL.md · Tune the parameters of an existing NeuroWorkflow graph until a measured quantity lands in a target range — choose what…
git:20260913.9bb9bce · audit A · 19 stars
CLAUDE.md CLAUDE.md file
oist/neuro-workflow · CLAUDE.md
git:20261013.17d1d76 · audit A · 19 stars
AGENTS.md@hackathon AGENTS.md file
oist/neuro-workflow · hackathon/AGENTS.md
git:20260619.31493a6 · audit A · 19 stars

Every file in oist/neuro-workflow

Browse by kind, by grade A, or by owner.