agent-context-loader
PROACTIVE AUTO-LOADING: Automatically detects and loads AGENTS.md files from the current working directory when starting a session or changing directories. This skill ensures agent-specific instructions are incorporated into Claude Code's context alongside CLAUDE.md, enabling specialized agent behaviors. Triggers automatically when Claude detects it's working in a directory, when starting a new session, or when explicitly requested to "load agent context" or "check for AGENTS.md file".
Best use case
agent-context-loader is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
PROACTIVE AUTO-LOADING: Automatically detects and loads AGENTS.md files from the current working directory when starting a session or changing directories. This skill ensures agent-specific instructions are incorporated into Claude Code's context alongside CLAUDE.md, enabling specialized agent behaviors. Triggers automatically when Claude detects it's working in a directory, when starting a new session, or when explicitly requested to "load agent context" or "check for AGENTS.md file".
Teams using agent-context-loader should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/agent-context-loader/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How agent-context-loader Compares
| Feature / Agent | agent-context-loader | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
PROACTIVE AUTO-LOADING: Automatically detects and loads AGENTS.md files from the current working directory when starting a session or changing directories. This skill ensures agent-specific instructions are incorporated into Claude Code's context alongside CLAUDE.md, enabling specialized agent behaviors. Triggers automatically when Claude detects it's working in a directory, when starting a new session, or when explicitly requested to "load agent context" or "check for AGENTS.md file".
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
Best AI Skills for Claude
Explore the best AI skills for Claude and Claude Code across coding, research, workflow automation, documentation, and agent operations.
AI Agents for Coding
Browse AI agent skills for coding, debugging, testing, refactoring, code review, and developer workflows across Claude, Cursor, and Codex.
ChatGPT vs Claude for Agent Skills
Compare ChatGPT and Claude for AI agent skills across coding, writing, research, and reusable workflow execution.
SKILL.md Source
# Agent Context Auto-Loader
**⚡ This skill activates AUTOMATICALLY - no user action required!**
## Purpose
This skill makes Claude Code recognize and load `AGENTS.md` files with the same priority as `CLAUDE.md` files, enabling specialized agent-specific instructions for your projects.
## How It Works
### Automatic Trigger Conditions
This skill automatically activates when:
1. **Starting a new Claude Code session** in any directory
2. **Changing directories** during a session (via `cd` or file operations)
3. **Any other agent skill is invoked** (ensures agent context is loaded first)
4. **User explicitly requests**: "load agent context", "check for AGENTS.md", or "read agent rules"
### Execution Flow
When triggered, Claude Code will:
1. **Check for AGENTS.md**: Look for `./AGENTS.md` in the current working directory
2. **Read the file** (if it exists): Use the Read tool to load full content
3. **Incorporate into context**: Treat AGENTS.md rules as session-level instructions
4. **Announce loading**: Confirm with user: "📋 Loaded agent-specific context from AGENTS.md"
5. **Apply for session**: Follow these rules for all subsequent operations
### Priority and Conflict Resolution
- **AGENTS.md supplements CLAUDE.md**: Both are active simultaneously
- **In case of conflicts**: AGENTS.md takes precedence for agent-specific behaviors
- **Scope**: AGENTS.md applies to agent workflows; CLAUDE.md applies to general project context
## Expected Behavior
### If AGENTS.md exists:
```
📋 Loaded agent-specific context from AGENTS.md
Following specialized agent rules for this session:
- [rule 1 from AGENTS.md]
- [rule 2 from AGENTS.md]
...
```
### If AGENTS.md doesn't exist:
```
No AGENTS.md found - using standard CLAUDE.md context only
```
## User Experience
**Fully Automatic** (preferred):
- Install plugin → AGENTS.md loads automatically → Agent rules active → No user action needed
**Manual Invocation** (fallback):
```bash
# If auto-loading doesn't trigger, user can say:
"load agent context"
"check for AGENTS.md"
"read agent rules from AGENTS.md"
```
## Implementation Details
### Step 1: Check for File
```bash
# Claude executes internally:
if [ -f "./AGENTS.md" ]; then
echo "📋 AGENTS.md detected"
fi
```
### Step 2: Read Content
```markdown
Use Read tool:
file_path: ./AGENTS.md
Load full content into session context
```
### Step 3: Apply Rules
```
Treat AGENTS.md content as:
- Session-level instructions (like CLAUDE.md)
- Agent-specific behavioral rules
- Overrides for agent workflows
```
## Example AGENTS.md Structure
```markdown
# AGENTS.md - Agent-Specific Instructions
## Agent Behavior Rules
When working with Agent Skills in this project:
1. **Always use TypeScript strict mode** for all generated code
2. **Never create files** without explicit user permission
3. **Follow naming convention**: use kebab-case for all file names
4. **Auto-commit after changes**: Create git commits automatically when tasks complete
## Specialized Workflows
### Code Generation
- Use templates from `./templates/` directory
- Run ESLint after generating any .ts/.js files
- Add comprehensive JSDoc comments
### Testing
- Generate tests alongside implementation files
- Use Jest for all test files
- Achieve 80%+ code coverage
## Priority Overrides
These rules override CLAUDE.md when agent skills are active:
- AGENTS.md → agent-specific strict rules
- CLAUDE.md → general project context
```
## Integration with Other Skills
This skill runs **before** other agent skills to ensure agent context is loaded first. When any other skill is invoked, this skill checks if AGENTS.md has been loaded for the current directory and loads it if not already present.
## Troubleshooting
**If AGENTS.md isn't loading automatically:**
1. **Manual invoke**: Say "load agent context"
2. **Check file location**: Ensure `AGENTS.md` is in current working directory (`pwd`)
3. **Check file permissions**: Ensure `AGENTS.md` is readable
4. **Use slash command**: Run `/sync-agent-context` to merge AGENTS.md into CLAUDE.md permanently
## Related Features
- **Slash Command**: `/sync-agent-context` - Permanently merges AGENTS.md into CLAUDE.md
- **Hook Script**: Runs on directory change to remind Claude to load context
- **Manual Loading**: Can always explicitly request "load AGENTS.md"
## Benefits
- **Zero configuration**: Just create `AGENTS.md` and it works
- **Project-specific rules**: Different agent behaviors per project
- **No CLAUDE.md pollution**: Keep agent-specific rules separate
- **Automatic synchronization**: Always up-to-date with current directory
---
**Status**: Proactive Auto-Loading Enabled
**Requires User Action**: No (automatic)
**Fallback**: Manual invocation if auto-loading failsRelated Skills
windsurf-cascade-context
Manage Cascade context window and memory for complex projects. Activate when users mention "cascade context", "ai memory", "context management", "large codebase navigation", or "multi-session development". Handles context optimization and persistence. Use when working with windsurf cascade context functionality. Trigger with phrases like "windsurf cascade context", "windsurf context", "windsurf".
openrouter-context-optimization
Optimize context window usage for OpenRouter models to reduce cost and improve quality. Use when hitting context limits, managing long conversations, or building RAG systems. Triggers: 'openrouter context', 'context window', 'openrouter token limit', 'reduce tokens openrouter'.
cursor-context-management
Optimize context window usage in Cursor with @-mentions, context pills, and conversation strategy. Triggers on "cursor context", "context window", "context limit", "cursor memory", "context management", "@-mentions", "context pills".
dataset-loader-creator
Dataset Loader Creator - Auto-activating skill for ML Training. Triggers on: dataset loader creator, dataset loader creator Part of the ML Training skill category.
react-context-setup
React Context Setup - Auto-activating skill for Frontend Development. Triggers on: react context setup, react context setup Part of the Frontend Development skill category.
schema-optimization-orchestrator
Multi-phase schema optimization workflow orchestrator. Creates session directories, spawns phase agents sequentially, validates outputs, aggregates results. Trigger: "run schema optimization", "optimize schema workflow", "execute schema phases"
test-skill
Test skill for E2E validation. Trigger with "run test skill" or "execute test". Use this skill when testing skill activation and tool permissions.
example-skill
Brief description of what this skill does and when the model should activate it. Use when [describe the user's intent or situation]. Trigger with "example phrase", "another trigger", "/example-skill".
testing-visual-regression
Detect visual changes in UI components using screenshot comparison. Use when detecting unintended UI changes or pixel differences. Trigger with phrases like "test visual changes", "compare screenshots", or "detect UI regressions".
generating-unit-tests
Test automatically generate comprehensive unit tests from source code covering happy paths, edge cases, and error conditions. Use when creating test coverage for functions, classes, or modules. Trigger with phrases like "generate unit tests", "create tests for", or "add test coverage".
generating-test-reports
Generate comprehensive test reports with metrics, coverage, and visualizations. Use when performing specialized testing. Trigger with phrases like "generate test report", "create test documentation", or "show test metrics".
orchestrating-test-execution
Test coordinate parallel test execution across multiple environments and frameworks. Use when performing specialized testing. Trigger with phrases like "orchestrate tests", "run parallel tests", or "coordinate test execution".