baro: Instructions file for Claude Code

CLAUDE.md

baro CLAUDE.md is an instructions file for Claude Code from jigjoy-ai/baro. It costs 713 tokens per session, scanned A, original, MIT.

Repository-specific instructions for the baro project. They cover the project description, technology choices, directory layout, and build commands.

In plain words
What is it for?
Understanding the baro codebase, following its structure, and running its builds.
Why use it?
They provide the coding agent with the local rules and context needed to work in this repository.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md. Also seen: mentions CLAUDE.md.

This is jigjoy-ai/baro's own configuration. It tells Claude Code how to work on baro itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything baro configures →

Reuse

Borrowing it

Nothing to install: this file belongs to jigjoy-ai/baro. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/jigjoy-ai/baro/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/jigjoy-ai/baro

Made for: Claude Code.

Wrote 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.

agentmods badge for baro CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/jigjoy-ai/baro/claude-md.svg)](https://agentmods.dev/instructions/jigjoy-ai/baro/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/jigjoy-ai/baro/claude-md"><img src="https://agentmods.dev/badge/instructions/jigjoy-ai/baro/claude-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 713 This file is loaded in full into every session.
When invoked 713 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00713 $0.00713
Opus 5 $0.00357 $0.00357
Sonnet 5 $0.00143 $0.00143
Haiku 4.5 $0.00071 $0.00071

Measured 8d ago against content hash f62fccc54d9e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

baro CLAUDE.md 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 8d 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.

CLAUDE.md · 86 lines

How it starts

The opening of the file, as written. The whole thing — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.

CLAUDE.md

Project Overview

Baro is a dual-stack project combining Rust and TypeScript/Node.js. It appears to be a TUI (terminal user interface) application with an accompanying web/app component. The project uses Rust for core functionality and TypeScript for the application layer.

Tech Stack

  • Rust: Core TUI application (baro-tui crate)
  • TypeScript/Node.js: Main application layer (baro-app package)
  • Cargo: Rust package manager and build system
  • npm: Node.js package manager

Directory Structure

baro/
├── crates/              # Rust workspace
│   └── baro-tui/        # Main Rust TUI crate
│       ├── Cargo.toml
│       └── src/
├── packages/            # Node.js workspace
│   └── baro-app/        # Main application
│       ├── package.json
│       ├── src/
│       ├── bin/
│       ├── scripts/
│       └── tsconfig.json
├── .github/workflows/   # CI/CD pipelines
│   └── release.yml
├── Cargo.toml           # Root Rust workspace manifest
├── package.json         # Root Node.js manifest
├── Cargo.lock
├── package-lock.json
├── README.md
├── prd.json            # Product requirements document
└── assets/
    └── screenshot.png

Build Commands

Rust:

cargo build      # Build the Rust project
cargo test       # Run Rust tests

Node.js:

npm install      # Install dependencies
npm run [script] # Run scripts defined in package.json

Key Files

  • Cargo.toml: Root Rust workspace configuration
  • package.json: Root Node.js configuration
  • crates/baro-tui/src/: Rust TUI implementation
  • packages/baro-app/src/: TypeScript application source
  • .github/workflows/release.yml: Release pipeline configuration
  • prd.json: Product specifications and requirements

Development Conventions

  • Uses Rust workspace for crate management (monorepo structure)
  • Uses npm/Node.js workspace for package management
  • Release workflow defined in GitHub Actions
  • No linter or formatter configuration detected in scan (may exist but not documented)

Read the full file on GitHub · 86 lines

Changes

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.

  1. 8d ago First seen · 86 lines · 713 tokens per session scan A f62fccc54d9e

Subscribe to this mod's changes

baro CLAUDE.md is an instructions file published in the GitHub repository jigjoy-ai/baro (120 stars, last pushed 4d ago), licensed MIT. It adds 713 tokens to every session, about $0.0036 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.

Related

Other instructions, from other repositories

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,153 tokens

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 6,785 tokens

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,469 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens

spec-kit AGENTS.md

AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,104 tokens