Loading the registry…
Set up or audit Claude Code project memory the right way — a lean CLAUDE.md plus offloaded docs, path-scoped .claude/rules/, and skills — so instructions stay high-signal instead of bloating context and getting ignored. Use this whenever setting up a repo for Claude Code, creating/scaffolding a CLAUDE.md, adding or organizing .claude/rules/, deciding how to structure project instructions, slimming a CLAUDE.md that has grown too long, or deciding which project-instruction content to move out of CLAUDE.md so it loads only when Claude needs it. Also covers monorepos (per-package CLAUDE.md, where to launch Claude, cross-package access). Reach for it even when the user just says "set up this project for Claude", "write a CLAUDE.md", "my CLAUDE.md is too long/getting ignored", or "how should I organize project instructions" — don't answer from memory, consult this skill and its references. NOT for human-facing docs (README, design docs, API docs), source-code comments/docstrings, or linter/formatter/ tooling setup — only files that configure how Claude Code reads a project (CLAUDE.md, .claude/rules/, skills).
Claude Skills are markdown + scripts loaded into Claude Code; scanned with the same pipeline.
We found this by crawling public sources and nobody has attested to it. That is how most of the registry gets here, and it is not a mark against the artifact — it only means no authenticated act of publication is on record. An artifact can be the vendor's own and still appear here.
Claude Skills install to a single target, no runtime picker.
nerlo install -- 'nebraskacoder/nebraskacoder-claude-plugins (claude-md-setup)'
Manual alternative: copy the skill folder into ~/.claude/skills/ so Claude Code loads it on next launch.
cp -r -- 'nebraskacoder/nebraskacoder-claude-plugins (claude-md-setup)' ~/.claude/skills/
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
4 of 11 scanners examined this package. The rest do not apply to it — language, ecosystem and packaging decide which analyzers can say anything, and a scanner that cannot examine an artifact reports nothing rather than passing it.
v1.4.0
0 findings · 1.4s
v2.0.11
12 findings · 15.7s
v0.3.74
3 findings · 2.3s
v0.1.0
0 findings · 6.7s
v0.1.0
No source files this scanner can analyze were found in this artifact. What each scanner covers
0 findings · 6.7s
vv0.3.2
No Go packages were found in this artifact. What each scanner covers
0 findings · 0.3s
v0.1.0
This scanner found nothing in this artifact that it assesses. What each scanner covers
0 findings · 2.2s
v0.71.0
No dependency manifest or lockfile was found in this artifact. What each scanner covers
0 findings · 0.5s
v2.3.8
No dependency manifest or lockfile was found in this artifact. What each scanner covers
0 findings · 0.4s
v0.71.0
No container image was published for this artifact. What each scanner covers
0 findings · 0.0s
vv1.6.0
No Go modules were found in this artifact. What each scanner covers
0 findings · 0.2s
1 scan on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Aug 18, 2026 | Flagged86 | — | agentshield: completecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral ·n/a: not applicablenerlo-install-instruction: completecapslock ·n/a: not applicablenerlo-multi-source ·n/a: not applicabletrivy ·n/a: not applicableosv-scanner ·n/a: not applicabletrivy_image ·n/a: not applicablegovulncheck ·n/a: not applicable | completed |
Findings in files this artifact installs stand as reported; a model re-read the rest and said which ones it believes are false positives. This is a second opinion published beside the evidence, not a correction to it: the per-scanner reports above are unchanged, every dismissed finding is still listed there at its original severity, and the score and the Flagged badge are computed from those raw severities alone. Nothing below moved them.
This review has not run for this scan yet. It runs once per scan, in the background, and is kept; it appears here when it has. Until then all 15 findings above stand exactly as their scanners reported them, at full severity.