agno CLAUDE.md

A set of instructions for working on the Agno software repository, including its folders, setup commands, and development environments. Agno is a software framework project.

In plain words
What is it for?
Use it when modifying Agno, especially when working with its code, examples, scripts, tests, documentation links, or virtual environments.
Why use it?
It gives coding agents the project-specific context they need to place changes correctly and follow the repository's setup conventions.

Instructions file

Install

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.

agentmods
npx agentmods add instructions/agno-agi/agno/claude-md
Clone the repo
git clone --depth 1 https://github.com/agno-agi/agno
Per session 1,804 This file is loaded in full into every session.
When invoked 1,804 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin 86% copy Near-identical to another mod 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 $0.01804 $0.01804
Opus 5 $0.00902 $0.00902
Sonnet 5 $0.00361 $0.00361
Haiku 4.5 $0.00180 $0.00180

Measured yesterday against content hash b260ff3cc8ba, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

agno 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 yesterday.

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.

Origin

This is a copy

86% identical to agno AGENTS.md — 21 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

CLAUDE.md · 259 lines

How it starts

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

CLAUDE.md — Agno

Instructions for Claude Code when working on this codebase.


Repository Structure

.
├── libs/agno/agno/          # Core framework code
├── cookbook/                # Examples, patterns and test cases (organized by topic)
├── scripts/                 # Development and build scripts
├── specs/                   # Design documents (symlinked, private)
├── docs/                    # Documentation (symlinked, private)
└── .cursorrules             # Coding patterns and conventions

Conductor Notes

When working in Conductor, you can use the .context/ directory for scratch notes or agent-to-agent handoff artifacts. This directory is gitignored.


The specs/ and docs/ directories are symlinked from external locations. For a fresh clone or new workspace, create these symlinks:

ln -s ~/code/specs specs
ln -s ~/code/docs docs

These contain private design documents and documentation that are not checked into the repository.


Virtual Environments

This project uses two virtual environments:

Environment Purpose Setup
.venv/ Development: tests, formatting, validation ./scripts/dev_setup.sh
.venvs/demo/ Cookbooks: has all demo dependencies ./scripts/demo_setup.sh

Use .venv for development tasks (pytest, ./scripts/format.sh, ./scripts/validate.sh).

Use .venvs/demo for running cookbook examples.


Testing Cookbooks

Apart from implementing features, your most important task will be to test and maintain the cookbooks in cookbook/ directory.

See cookbook/08_learning/ for the golden standard.

Quick Reference

Test Environment:

# Virtual environment with all dependencies
.venvs/demo/bin/python

# Setup (if needed)
./scripts/demo_setup.sh

# Database (if needed)
./cookbook/scripts/run_pgvector.sh

Run a cookbook:

.venvs/demo/bin/python cookbook/<folder>/<file>.py

Read the full file on GitHub · 259 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. yesterday First seen · 259 lines · 1,804 tokens per session scan A b260ff3cc8ba

Subscribe to this mod's changes

agno CLAUDE.md is an instructions file published in the GitHub repository agno-agi/agno (41,969 stars, last pushed yesterday), licensed Apache-2.0. It adds 1,804 tokens to every session, about $0.0090 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to agno AGENTS.md, differing in 21 lines, and is treated as a copy.