agent-context-loader

Productivity Community

Repo stars 2,235
Author repo claude-code-plugins-plus-skills

Interpretation is structured for decision-making; original keeps the upstream SKILL.md unchanged.

Decide Fit First

Core job: 'Execute proactive auto-loading: automatically detects and loads agents.md Automatic discovery and loading of AGENTS.md files ac…
Best fit: Use it when the task has reusable inputs, steps, and validation criteria rather than a one-off answer.
Avoid forcing it: If the source lacks commands, platform support, or external-service evidence, keep those fields unknown instead of guessing.

Design Intent

Structure: The skill is organized around “Overview”, “Prerequisites”, “Instructions”, “Output”, showing how the author expects the agent to judge fit, collect context, and produce verifiable output.
Trigger evidence: Prioritize the author’s wording around when to use it, what context to collect, and what output shape to produce.
Evidence boundary: Author text states facts, repository files prove commands and paths, and Fluxly only adds fit, limits, and usage judgment.

How To Use It

Inputs: Provide target material, scope, expected result, forbidden changes, and validation method.
Invocation: Name agent-context-loader directly; if the source includes slash commands, start with the command and then add task context.
Validation: Start small and check whether the result follows “Overview / Prerequisites / Instructions” before expanding.

Boundaries And Review

Dependencies: It usually needs no extra API key, so start with a small validation task.
Permissions: Declared permissions include read / write; ask the agent to state file, command, and rollback boundaries before acting.
Quality bar: A useful result names the deliverable, evidence, and next action. Generic prose means the task needs tighter context.

Agent Context Loader

Overview

Automatic discovery and loading of AGENTS.md files across project hierarchies for AI coding agents. This skill scans the current workspace and its parent directories to locate agent instruction files, then surfaces their contents so the active agent session has full operational context.

Prerequisites

A project workspace containing one or more AGENTS.md files at any directory depth
Read and Glob permissions to traverse the directory tree
Grep access for searching file contents when multiple candidates exist

Instructions

Scan the current working directory and all ancestor directories (up to the filesystem root or repository root) for files named AGENTS.md or agents.md.
Search subdirectories of the current workspace for additional AGENTS.md files that may apply to sub-projects or modules.
Determine load order: files closer to the repository root load first (global context), files in deeper directories load later (override or supplement).
Read each discovered AGENTS.md file and extract its instruction blocks, workflow definitions, and constraint declarations.
Merge instructions into a unified context, noting any conflicts between levels (e.g., a subdirectory agent overriding a root-level rule).
Present the loaded context as a structured summary: source file path, instruction count, and any detected conflicts.
Cache the discovery results for the current session to avoid redundant filesystem scans on subsequent activations.

Output

Ordered list of discovered AGENTS.md file paths with their directory depth
Merged instruction set combining all discovered agent contexts
Conflict report highlighting any contradictory directives between levels
Session cache status indicating whether results are fresh or reused

Error Handling

Error	Cause	Solution
No `AGENTS.md` found	Workspace has no agent instruction files	Confirm the correct working directory; create an `AGENTS.md` at the project root if needed
Permission denied on directory traversal	Restricted parent directories above the workspace	Limit scan depth to the repository root (detected via `.git/` presence)
Circular symlink detected	Symlinked directories create an infinite traversal loop	Skip symlinked directories during the scan; log a warning with the symlink path
Conflicting instructions across levels	A subdirectory `AGENTS.md` contradicts the root-level file	Flag the conflict in the output; apply the more specific (deeper) instruction by default
File encoding error	`AGENTS.md` uses a non-UTF-8 encoding	Attempt latin-1 fallback; report the file path and encoding issue

Examples

Example 1: Monorepo with per-package agent instructions

Structure: Root AGENTS.md sets global conventions; packages/api/AGENTS.md adds API-specific tooling rules.
Result: Both files loaded in order. The API-specific rules supplement the global context without conflict.

Example 2: Nested workspace with conflicting commit policies

Structure: Root AGENTS.md says "always sign commits"; services/legacy/AGENTS.md says "skip commit signing."
Result: Conflict detected and reported. The deeper (legacy) directive is applied with a warning noting the override.

Example 3: First-time setup with no agent files

Structure: A freshly cloned repository with no AGENTS.md anywhere.
Result: Scan completes with zero files found. Output includes a suggestion to create AGENTS.md at the repository root with a minimal template.

Resources

Claude Code AGENTS.md specification: https://docs.anthropic.com/en/docs/agents
Monorepo workspace patterns for agent configuration: https://docs.anthropic.com/en/docs/claude-code
File discovery best practices for hierarchical configuration loading

Fluxly profile Author and license come from source; runtime, permissions, and network are Fluxly detections or estimates

Fluxly category: Productivity
Author-declared agents: No explicit declaration found; this is not inferred or tested compatibility
Static check: 88 / 100 · heuristic scan, not runtime safety proof
Author / version / license: @jeremylongshore · no license declared
Fluxly token estimate: Lean
Fluxly setup estimate: Plug-and-play
External API key: No requirement detected
Detected OS requirements: Unspecified
Runtime requirements: Unspecified
Detected file/system behavior: Read-only
Write / modify
Detected network behavior: Local-only
Install commands: None (reference only)

Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.

Heads up: 未限定 allowed-tools，默认拥有全部工具权限。

Output preview agent-context-loader.preview

The current SKILL.md does not define a fixed output example.

SKILL.md SKILL.md

# Agent Context Loader

## Overview

Automatic discovery and loading of `AGENTS.md` files across project hierarchies for AI coding agents. This skill scans the current workspace and its parent directories to locate agent instruction files, then surfaces their contents so the active agent session has full operational context.

## Prerequisites

- A project workspace containing one or more `AGENTS.md` files at any directory depth
- Read and Glob permissions to traverse the directory tree
- Grep access for searching file contents when multiple candidates exist

## Instructions

1. Scan the current working directory and all ancestor directories (up to the filesystem root or repository root) for files named `AGENTS.md` or `agents.md`.
2. Search subdirectories of the current workspace for additional `AGENTS.md` files that may apply to sub-projects or modules.
3. Determine load order: files closer to the repository root load first (global context), files in deeper directories load later (override or supplement).
4. Read each discovered `AGENTS.md` file and extract its instruction blocks, workflow definitions, and constraint declarations.
5. Merge instructions into a unified context, noting any conflicts between levels (e.g., a subdirectory agent overriding a root-level rule).
6. Present the loaded context as a structured summary: source file path, instruction count, and any detected conflicts.
7. Cache the discovery results for the current session to avoid redundant filesystem scans on subsequent activations.

## Output

- Ordered list of discovered `AGENTS.md` file paths with their directory depth
- Merged instruction set combining all discovered agent contexts
- Conflict report highlighting any contradictory directives between levels

…

Evidence boundary and execution chain

Author text anchors workflow facts; Fluxly only indexes current sections, terms, files, and commands.

sections -> Overview → Prerequisites → Instructions → Output → Error Handling → Examples
terms    -> Example 1: Monorepo with per-package agent instructions · Example 2: Nested workspace with conflicting commit policies · Example 3: First-time setup with no agent files · Automatic discovery and loading of AGENTS.md files across project hierarchies for AI coding agents. · - Structure: Root AGENTS.md sets global conventions; packages/api/AGENTS.md adds API-specific tooling rules. · - Structure: A freshly cloned repository with no AGENTS.md anywhere.
files/cmd -> AGENTS.md · agents.md · .git/ · packages/api/AGENTS.md · services/legacy/AGENTS.md
body sha256 -> a45b85ffa4d5