agentmods.dev

tari-ootle: Instructions file for Claude Code

CLAUDE.md

tari-ootle CLAUDE.md is an instructions file for Claude Code from tari-project/tari-ootle. It costs 1,387 tokens per session, scanned A, original, BSD-3-Clause.

Project guidance for Tari Ootle, a Rust codebase with wallet applications, transaction components, and supporting libraries. It explains the repository layout, naming, and rules for useful code comments.

In plain words
What is it for?
Use it when changing the wallet daemon, wallet command-line tool, transaction parser, transaction types, template types, or CBOR serialization code.
Why use it?
It helps an agent find the right package and avoid incorrect names or comments that merely describe past changes.

Instructions file for Claude Code

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

This is tari-project/tari-ootle's own configuration. It tells Claude Code how to work on tari-ootle 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 tari-ootle configures →

not rated 28repo changed today A scan 1,387 tokens original BSD-3-Clause
View source ↗ tari-project/tari-ootle tari.com
Reuse

Borrowing it

Nothing to install: this file belongs to tari-project/tari-ootle. 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/tari-project/tari-ootle/development/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/tari-project/tari-ootle

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 tari-ootle CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/tari-project/tari-ootle/claude-md/github.svg)](https://agentmods.dev/instructions/tari-project/tari-ootle/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/tari-project/tari-ootle/claude-md"><img src="https://agentmods.dev/badge/instructions/tari-project/tari-ootle/claude-md/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.

agentmods 80×15 button for tari-ootle CLAUDE.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/tari-project/tari-ootle/claude-md"><img src="https://agentmods.dev/badge/instructions/tari-project/tari-ootle/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,387 This file is loaded in full into every session.
When invoked 1,387 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.01387 $0.01387
Opus 5 $0.00694 $0.00694
Sonnet 5 $0.00277 $0.00277
Haiku 4.5 $0.00139 $0.00139

Measured today against content hash 4c0e4f9df2f0, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

tari-ootle 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 today.

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 · 95 lines

How it starts

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

Tari Ootle - Claude Code Cheatsheet

Project Structure

  • The project is called "Ootle" or "Tari Ootle" (not "DAN" or "Tari DAN")
  • Crates are in crates/, applications in applications/, clients in clients/
  • Wallet daemon package: tari_ootle_walletd (in applications/tari_walletd/)
  • Wallet CLI: tari_wallet_cli (in applications/tari_wallet_cli/)
  • Transaction manifest parser: tari_transaction_manifest (in crates/transaction_manifest/)
  • Transaction types/instructions: tari_ootle_transaction (in crates/transaction/)
  • Template lib types (OwnerRule, RistrettoPublicKeyBytes, etc.): tari_template_lib_types (in crates/template_lib_types/)
  • CBOR serialization: tari_bor (in crates/tari_bor/) - wraps ciborium, re-exports serde

Code Comments

IMPORTANT: Comments must help a future reader understand code that isn't self-explanatory — non-obvious invariants, the reason for a non-obvious approach, tricky edge cases. They must NOT narrate changes.

  • When fixing a bug, lint, or doing a refactor, do not add a comment explaining what was wrong or why you changed it. The corrected code no longer has the issue, so such a comment describes a problem that isn't in the code — it serves no future reader.
  • Rationale for a fix belongs in the commit message and PR description, not in the source.
  • Never answer a reviewer in a code comment. When addressing review feedback, the justification goes in the reply on the review thread; the source gets only what a reader who never saw the review needs. A comment that argues for the new code over what the reviewer objected to is narrating a change — the thing it contrasts against isn't in the file.
  • Write present-tense statements of intent/invariant ("X must be Y because Z"), never history ("changed this from A to B", "without this guard X would happen", "previously this did A").

Key Facts

Token Amounts

  • All amounts in code/manifests are in microtari: 1 TARI = 1,000,000 microtari
  • In manifests, use TARI as the resource identifier (not XTR, which is deprecated)
  • User-facing: use tTARI (testnet) or $TARI (mainnet)

Read the full file on GitHub · 95 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. today Changed · +5 lines · +120 tokens per session 4c0e4f9df2f0
  2. 9d ago First seen · 90 lines · 1,267 tokens per session scan A 11bac85152e8

Subscribe to this mod's changes

tari-ootle CLAUDE.md is an instructions file published in the GitHub repository tari-project/tari-ootle (28 stars, last pushed today), licensed BSD-3-Clause. It adds 1,387 tokens to every session, about $0.0069 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.

Rustlayer-2tari
Related

Other instructions, from other repositories

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

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

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

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

deepseek-harness AGENTS.md

AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.

deepseek-ai/deepseek-harness · 3,735 tokens