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 skills add agno-agi/agno --skill summarygit 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/skills/agno-agi/agno/summary)<a href="https://agentmods.dev/skills/agno-agi/agno/summary"><img src="https://agentmods.dev/badge/skills/agno-agi/agno/summary/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.
<a href="https://agentmods.dev/skills/agno-agi/agno/summary"><img src="https://agentmods.dev/badge/skills/agno-agi/agno/summary.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00013 | $0.00131 |
| Opus 5.5 | $0.00005 | $0.00052 |
| Sonnet 5.5 | $0.00003 | $0.00026 |
| Haiku 4.5 | $0.00001 | $0.00013 |
Grade A, and why
summary 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 2d 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.
What it actually says
Read the Product identified in the message, its Tasks and attention counts. Explain what changed, what awaits the owner and what failed, using actual records and summary.md. That page may retain an undelivered attempt; the summary tool compares changes against the last successfully delivered snapshot. Pass your narrative to summarize_company_product to write the summary to its wiki and deliver it through the configured interface and destination. Do not invent progress. Do not accept or complete work, alter Sources or schedules. When nothing needs attention, record a quiet successful check.
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.
- 2d ago First seen · 14 lines · 13 tokens per session scan A eec03c23fe08
summary is a skill published in the GitHub repository agno-agi/agno (42,799 stars, last pushed yesterday), licensed Apache-2.0. It adds 13 tokens to every session and 131 once invoked, about $0.0001 per session on Opus 5.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-10-17.
Other skills, from other repositories
vigilante-issue-implementation-on-python
Implement a GitHub issue end-to-end when Vigilante dispatches work for a Python repository with idiomatic tooling and security guidance.
infoops
Use for maintaining a workspace/infoops operating system: signal collection and classification, thread management, source profiles, and PULSE dashboard refresh. Triggers when working with the workspace/infoops directory, refreshing PULSE, managing threads, or tracking source profiles.
python-packaging
Comprehensive guide to creating, structuring, and distributing Python packages using modern packaging tools, pyproject.toml, and publishing to PyPI.
python-feature-lifecycle
Guidance for package and feature lifecycle in the Agent Framework Python codebase, including stage meanings, feature-stage decorators, feature enums, and how to move APIs from one stage to the next.
python-development
Coding standards, conventions, and patterns for developing Python code in the Agent Framework repository. Use this when writing or modifying Python source files in the python/ directory.
effect-v4
Write, review, or upgrade Effect v4 code in the Composio CLI, cli-keyring, and json-schema-to-effect-schema packages, all pinned exactly to [email protected] — Context.Service and explicit layers, Schema.TaggedError and typed recovery, the effect/cli command surface, and the vendored effect source oracle. Use when writing…