Menu

Individual skill

agents-md-mapper

This skill should be used when creating, refreshing, or validating a repository `AGENTS.md` so it stays concise, current, and grounded in repository evidence. Use when `AGENTS.md` is missing or stale, after refactors or tooling changes, when new docs become the system of record, or when adding lightweight drift checks.

skills/agents-md-mapper/SKILL.md

Read pinned source

Source commit 7a9fa15a4e018c8e26dbf01b9e1c5bdcabd56d72

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
105
Repository last updated
Mar 17, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

  • docs Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# AGENTS.md Mapper

## Overview

Maintain a concise, current `AGENTS.md` for a repository as the codebase changes. Treat the file as a navigational map for future coding agents: show where to start, where important things live, how to validate changes, and which deeper docs outrank the map.

## When to Use

- Create a new `AGENTS.md` for a repository that does not have one
- Refresh an existing `AGENTS.md` that may be stale after refactors, path moves, package splits, or architecture changes
- Update the map after tooling, tests, CI, docs, or ownership signals changed
- Point `AGENTS.md` at new architecture docs, runbooks, or generated references that became the source of truth
- Add lightweight checks that detect drift between `AGENTS.md` and repository reality