jeremylongshore/tons-of-skills-marketplace

agent-context-loader

'Execute proactive auto-loading: automatically detects and loads agents.md files.

View source

How to use

  1. Copy the installation command and review the source package before installing it in your own agent environment.
  2. Check the source document for required tools, credentials and supported hosts.
  3. Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/jeremylongshore/tons-of-skills-marketplace --skill agent-context-loader

Before you start

  • Installation does not include a model subscription, API allowance or permission to access your files.
  • Repository stars and installation counts describe activity, not an independent quality or security test.
Original skill document

Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.

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
  • Session cache status indicating whether results are fresh or reused

Error Handling

ErrorCauseSolution
No AGENTS.md foundWorkspace has no agent instruction filesConfirm the correct working directory; create an AGENTS.md at the project root if needed
Permission denied on directory traversalRestricted parent directories above the workspaceLimit scan depth to the repository root (detected via .git/ presence)
Circular symlink detectedSymlinked directories create an infinite traversal loopSkip symlinked directories during the scan; log a warning with the symlink path
Conflicting instructions across levelsA subdirectory AGENTS.md contradicts the root-level fileFlag the conflict in the output; apply the more specific (deeper) instruction by default
File encoding errorAGENTS.md uses a non-UTF-8 encodingAttempt 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

  • AGENTS.md open specification: https://agents.md/
  • Monorepo workspace patterns for agent configuration: https://code.claude.com/docs
  • File discovery best practices for hierarchical configuration loading
from this repository

More skills

All skills
jeremylongshore
Community

agent-creator

'Create production-grade agent .md files aligned with the current Anthropic subagent contract. Also validates existing agents against the marketplace compliance rules. Use when building custom subagents, reviewing agent quality, or creating parallel agent architectures for orchestrator skills. Trigger with "/agent-creator", "create an agent", "build a subagent", or "validate my agent". Make sure to use this skill whenever creating agents/.md files for plugins or standalone use. '

1h installs
2
GitHub stars
2.9K
Updated
Nov 8
jeremylongshore
Community

agent-patterns

'Execute this skill should be used when the user asks about "SPAWN REQUEST format", "agent reports", "agent coordination", "parallel agents", "report format", "agent communication", or needs to understand how agents coordinate within the sprint system. Use when appropriate context detected. Trigger with relevant phrases based on skill purpose. '

1h installs
2
GitHub stars
2.9K
Updated
Nov 8
jeremylongshore
Community

agent-safety-preflight

Generate a local repository risk receipt before Claude Code or other AI-agent edits. Use when the user asks to prepare a repository for agent changes, check for risky hooks or credential-writing automation, or run the /agent-preflight command. Trigger with "run agent preflight", "check this repo before agent edits", or "/agent-preflight".

1h installs
2
GitHub stars
2.9K
Updated
Nov 8
jeremylongshore
Community

brand-strategy

Build or review a seven-part brand strategy covering identity, audience, positioning, messaging, visual principles, channels and measurement. Use when creating a brand brief, defining positioning or revising brand messaging. Trigger with "create brand strategy", "build brand brief" or "brand messaging".

1h installs
2
GitHub stars
2.9K
Updated
Nov 8