diriendirien/yet-another-agent-harness/.claude/skills/agent-rules/AGENTS.md

yet-another-agent-harness / agent-rules

AGENTS.md19 starsChanged 8 months agoMITView on GitHub

Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 31,700 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository53 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .github/workflows/AGENTS.mdAGENTS.md
- pkg/AGENTS.mdAGENTS.md
- agent-ready-goSkill
- agent-rulesSkill
- architecture-designerSkill
- cli-developerSkill
- cloudformation-to-pulumiSkill
- code-reviewerSkill
- commitlintSkill
- commitSkill
- csharp-developerSkill
- decideSkill
- dep-upgradeSkill
- design-principlesSkill
- devops-engineerSkill
- flux-cliSkill
- flux-operator-cliSkill
- golang-proSkill
- go-nolint-auditSkill
- javascript-proSkill
- kubernetes-specialistSkill
- lint-fixSkill
- markdownlintSkill
- prSkill
- pull-request-msg-with-ghSkill
- pulumi-arm-to-pulumiSkill
- pulumi-automation-apiSkill
- pulumi-best-practicesSkill
- pulumi-cdk-to-pulumiSkill
- pulumi-cliSkill
- pulumi-componentSkill
- pulumi-escSkill
- pulumi-goSkill
- pulumi-neoSkill
- pulumi-pythonSkill
- pulumi-terraform-to-pulumiSkill
- pulumi-typescriptSkill
- python-proSkill
- reviewSkill
- roadmapSkill
- rust-async-patternsSkill
- rust-best-practicesSkill
- rust-engineerSkill
- scoutSkill
- security-auditSkill
- spring-boot-engineerSkill
- sre-engineerSkill
- sync-websiteSkill
- tailscale-installSkill
- tech-debtSkill
- the-foolSkill
- typescript-proSkill

The file

We split this AGENTS.md into the rules it gives an agent

6 rules. About 1 is common, 3 are distinctive, and 2 are very specific to this project.

≈1
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Distinctive:
Keep skills focused on one domain/task
line 60
Common:
Never include secrets or credentials in skills
line 76
Very specific:
Use placeholder values in examples: your-api-key, example.com
line 78
Distinctive:
Check existing skills for patterns
line 100
Very specific:
Test skills with claude --skill <name>
line 102
Distinctive:
Check root AGENTS.md for project conventions 
line 103

≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

AGENTS.md

AGENTS.md — agents

Overview

Claude Code skill/plugin providing AI agent capabilities

Key Files

File	Purpose
`skills/agent-rules/scripts/verify-commands.sh`	!/usr/bin/env bash
`skills/agent-rules/scripts/generate-file-map.sh`	!/usr/bin/env bash
`skills/agent-rules/scripts/analyze-git-history.sh`	!/usr/bin/env bash
`skills/agent-rules/scripts/detect-utilities.sh`	!/usr/bin/env bash
`skills/agent-rules/scripts/extract-platform-files.sh`	!/usr/bin/env bash

Golden Samples (follow these patterns)

Pattern	Reference
Standard implementation	`skills/agent-rules/SKILL.md`

Setup & environment

Plugin: agents v2.8.0
Skills: 1 skill(s) in skills/
Install: composer require netresearch/agent-rules-skill

Directory structure

.claude-plugin/
  plugin.json          → Plugin manifest (name, version, skills)
skills/
  <skill-name>/
    SKILL.md           → Skill definition and instructions
    assets/            → Templates, reference docs
    scripts/           → Shell scripts for automation
    references/        → Examples, golden samples

Build & tests

Lint scripts: shellcheck skills/*/scripts/*.sh
Validate plugin: jq . .claude-plugin/plugin.json

Code style & conventions

SKILL.md: Clear, actionable instructions for AI agents
Shell scripts: Follow ShellCheck recommendations
Templates: Use `` syntax for variables
Keep skills focused on one domain/task
Include checkpoints for verification
Provide golden samples for pattern demonstration

Skill design principles

Actionable: Tell agents WHAT to do, not just WHAT things are
Verifiable: Include checkpoints agents can run to verify work
Scoped: One skill = one domain (don't mix concerns)
Referenced: Point to golden samples, not generic examples
Minimal: Include only what agents need; avoid documentation bloat

Security & safety

Never include secrets or credentials in skills
Validate all user inputs in scripts
Use placeholder values in examples: your-api-key, example.com
Review generated content for sensitive information

PR/commit checklist

ShellCheck passes: shellcheck skills/*/scripts/*.sh
SKILL.md instructions are clear and actionable
Templates use whole-line placeholders (not inline)
Golden samples exist for key patterns
Checkpoints are verifiable
plugin.json version updated if releasing

Patterns to Follow

Prefer looking at real code in this repo over generic examples. See Golden Samples section above for files that demonstrate correct patterns.

When stuck

Check existing skills for patterns
Review Claude Code documentation
Test skills with claude --skill <name>
Check root AGENTS.md for project conventions

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

It worked
Partly
It didn't

What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free