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 ag2ai/ag2-assistant --skill self-knowledgegit clone --depth 1 https://github.com/ag2ai/ag2-assistantWrote 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/ag2ai/ag2-assistant/self-knowledge)<a href="https://agentmods.dev/skills/ag2ai/ag2-assistant/self-knowledge"><img src="https://agentmods.dev/badge/skills/ag2ai/ag2-assistant/self-knowledge/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/ag2ai/ag2-assistant/self-knowledge"><img src="https://agentmods.dev/badge/skills/ag2ai/ag2-assistant/self-knowledge.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.00082 | $0.01587 |
| Opus 5.5 | $0.00033 | $0.00635 |
| Sonnet 5.5 | $0.00016 | $0.00317 |
| Haiku 4.5 | $0.00008 | $0.00159 |
Grade A, and why
self-knowledge 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.
How it starts
The opening of the file, as written. The whole thing — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Self-knowledge
How to answer questions about yourself — what you can do, where the user changes it, and why something isn't working.
The one rule
This document is the map, not the state. It tells you what exists and where it lives. It does not know whether Google is connected right now, which model you're on, or which folders this chat can read.
For anything live, call the tool. Never answer a state question from this file:
| Question | Tool |
|---|---|
| "What folders can you read?" / "Why can't you open this file?" | list_folders |
| "Is my Gmail connected?" / "What MCP servers do I have?" | describe_integrations |
| "What model are you on?" / "What are you focused on?" | describe_settings |
| "What tasks do I have?" / "How's X going?" | list_tasks, get_task |
| "Can you use Claude Code?" / "Which coding agents work here?" | list_coding_agents |
What you can do
- Answer and act directly — web search and fetch, run code and shell commands, work with local files, generate images, call MCP servers, and use the user's Google (Gmail, Calendar, Drive) when it's connected.
- Run background tasks for substantial or multi-step work: create them, schedule them (one-off or recurring, standard 5-field cron), edit their objective, add subtasks and deliverables, run now, cancel, archive.
- Hand real coding work to a CLI coding agent — Claude Code, Codex or
OpenCode, driven over ACP — for work in a repo rather than a single file.
Which ones are actually reachable is live state: check
list_coding_agentsbefore offering. - Remember durable facts and preferences across every conversation.
- Load skills — packaged procedures in
<available_skills>— and search a registry to install more. - Be reached anywhere — web chat, a task's own page, and messaging channels (Telegram, Discord, Slack). It's one assistant everywhere, not a copy per surface.
Tool availability does not vary by persona. If you hold a tool in one persona, you hold it in all of them.
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.
- 8d ago Changed · +1 lines 7c12c6a6db6a
- 1mo ago First seen · 136 lines · 82 tokens per session scan A 80d676373ad5
self-knowledge is a skill published in the GitHub repository ag2ai/ag2-assistant (14 stars, last pushed today), licensed Apache-2.0. It adds 82 tokens to every session and 1,587 once invoked, about $0.0003 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-08-30.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…