Agno is a framework and runtime for building, running, and managing platforms made of AI agents. Developers use its SDK, service runtime, and web interface to create agent applications with storage, integrations, APIs, and operational controls; the catalogue entries provide agent-oriented workflows and configuration for using Agno.
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.
npx agentmods add instructions/agno-agi/agno/agents-mdgit clone --depth 1 https://github.com/agno-agi/agnoWrote 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.
[](https://agentmods.dev/instructions/agno-agi/agno/agents-md)<a href="https://agentmods.dev/instructions/agno-agi/agno/agents-md"><img src="https://agentmods.dev/badge/instructions/agno-agi/agno/agents-md.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.01544 | $0.01544 |
| Opus 5 | $0.00772 | $0.00772 |
| Sonnet 5 | $0.00309 | $0.00309 |
| Haiku 4.5 | $0.00154 | $0.00154 |
Grade A, and why
agno AGENTS.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 5d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- agno CLAUDE.md — 86% identical, 21 lines differ
How it starts
The opening of the file, as written. The whole thing — 242 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — Agno
Instructions for AI coding agents 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.
Setting Up Symlinks
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
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.
- 5d ago First seen · 242 lines · 1,544 tokens per session scan A 1c7cdbf546ee
agno AGENTS.md is an instructions file published in the GitHub repository agno-agi/agno (42,001 stars, last pushed 3d ago), licensed Apache-2.0. It adds 1,544 tokens to every session, about $0.0077 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.
Other instructions, from other repositories
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).
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.
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.