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 skills/eveld/claude/agent-awarenessnpx skills add eveld/claude --skill agent-awarenessgit clone --depth 1 https://github.com/eveld/claudeWrote 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/eveld/claude/agent-awareness)<a href="https://agentmods.dev/skills/eveld/claude/agent-awareness"><img src="https://agentmods.dev/badge/skills/eveld/claude/agent-awareness.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.1 | $0.00038 | $0.00716 |
| Opus 5 | $0.00019 | $0.00358 |
| Sonnet 5 | $0.00008 | $0.00143 |
| Haiku 4.5 | $0.00004 | $0.00072 |
Grade A, and why
agent-awareness 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 6d 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Awareness Guide
You have access to specialized agents that are MORE EFFICIENT than basic tools. You MUST use these agents instead of grep, glob, or generic Task agents.
Decision Tree
Finding files or components?
→ Use codebase-locator agent
- Better than: grep, glob, find, ls
- Example: "Find all authentication-related files"
Understanding how code works?
→ Use codebase-analyzer agent
- Better than: Reading multiple files manually
- Example: "Analyze how the login flow works"
Finding similar implementations or patterns?
→ Use codebase-pattern-finder agent
- Better than: Searching and reading manually
- Example: "Find examples of API handlers"
Finding documentation in thoughts/?
→ Use thoughts-locator agent
- Better than: grep in thoughts directory
- Example: "Find research about authentication"
Understanding specific documents?
→ Use thoughts-analyzer agent
- Better than: Reading docs manually
- Example: "Extract key insights from these research docs"
Researching external information?
→ Use web-search-researcher agent
- Only when user explicitly asks for web research
- Example: "Research how JWT tokens work"
Analyzing complex errors or stack traces?
→ Use error-analyzer agent
- Better than: Reading multiple files manually to understand error
- Example: "Analyze this panic: nil pointer dereference at handler.go:42"
Available Agents
| Task Type | Use This subagent_type |
|---|---|
| Finding files/components | codebase-locator |
| Understanding code | codebase-analyzer |
| Finding similar patterns | codebase-pattern-finder |
| Finding documentation | thoughts-locator |
| Analyzing documents | thoughts-analyzer |
| Web research | web-search-researcher |
| Analyzing errors | error-analyzer |
Implementation Agents
During implementation, use aggressive agent orchestration:
- See
spawn-implementation-agentsskill for full pattern - Keep main agent under 40k tokens per phase
- Use sub-agents for file reading, pattern finding, testing, verification
- 60% token reduction per phase
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.
- 6d ago First seen · 98 lines · 38 tokens per session scan A eb0e5503b4f7
agent-awareness is a skill published in the GitHub repository eveld/claude (10 stars, last pushed 7mo ago), licensed MIT. It adds 38 tokens to every session and 716 once invoked, about $0.0002 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-31.
Other skills, from other repositories
ai-ml-development
AI and machine learning development with PyTorch, TensorFlow, and LLM integration. Use when building ML models, training pipelines, fine-tuning LLMs, or implementing AI features.
android-development
Android development with Kotlin, Jetpack Compose, and modern Android architecture. Use when building Android apps, implementing Material Design, or following Android best practices.
authentication-patterns
OAuth 2.0, JWT, SSO, MFA, NextAuth/Clerk/Supabase Auth implementation patterns.
case-interview-practice
Interactive consulting case interview practice with structured frameworks, feedback mechanisms, and progressive difficulty. Use when preparing for management consulting interviews, case competitions, or business problem-solving exercises.
email-systems
Transactional email (Resend, SendGrid, SES), templates (React Email, MJML), deliverability (SPF/DKIM/DMARC), and inboxing best practices. Use when building email infrastructure, designing templates, or troubleshooting deliverability.
customer-persona-builder
Data-driven customer persona development combining market research, user behavior analysis, and segmentation frameworks. Use when creating buyer personas, ideal customer profiles (ICPs), or user archetypes.