stevesolun/ctx / imported-skills/agents-md/skills/agents-md-protocol
agents-md-protocol
VerifiedCreate or review an AGENTS.md file so coding agents get stable repo-local instructions: environment setup, testing, style, security boundaries, PR policy, and handoff rules. Use when a repo lacks durable agent guidance or when a custom harness needs a predictable context file.
AGENTS.md Protocol
Purpose
Create or tighten a repository-level AGENTS.md contract for coding agents.
Treat it as durable operating context, not a chat prompt.
When to Use
- Repo has no
AGENTS.md,CLAUDE.md, or equivalent agent instructions. - Existing instructions are stale, vague, or missing test commands.
- A custom/API/local harness needs stable context it can load every run.
- A multi-agent workflow needs explicit handoff and review rules.
Procedure
- Inspect repo layout, package managers, CI files, and test commands.
- Capture only durable facts and team rules.
- Keep commands exact and runnable from the documented directory.
- Add security and destructive-operation boundaries.
- Add PR/review expectations and required verification.
- Keep the file short enough to load every session.
Recommended Sections
Dev environment tipsTesting instructionsBuild and lintCode styleSecurity boundariesPR instructionsAgent handoff notes
Quality Bar
- Every command has a working directory or clear scope.
- No secrets, tokens, or private URLs.
- No vague rules such as "be careful" without a concrete check.
- No roadmap or marketing text.
- Instructions match current CI and package metadata.
Harness Attachment
For non-Claude-Code harnesses, load AGENTS.md as outer-loop project context.
The harness should also keep explicit task state outside conversation history.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 465k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 465k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 465k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 192k | Updated | Claude CodeCodex | Verified | Install |