awesome-ai-agents
slavakurilyak/awesome-ai-agents/AGENTS.md
Every project added to the list must have its own public repository on GitHub, GitLab.com, or Codeberg. No specific license is required. A hosted product, website, forge organization profile, client, or integration without the project's own public repository does not qualify. Never treat a contributor-supplied boolean or license claim as verification; for an individual submission, run go run ./cmd/verify-forge-repositories --project "Project name" and go run ./cmd/validate-data --project "Project name". Require successful public repository metadata. Failed, private, or inaccessible checks mean…
What's in it
- Agent guidance
- Third-party project eligibility
- Crediting every addition
# Agent guidance ## Third-party project eligibility Every project added to the list must have its own public repository on GitHub, GitLab.com, or Codeberg. No specific license is required. A hosted product, website, forge organization profile, client, or integration without the project's own public repository does not qualify. Never treat a contributor-supplied boolean or license claim as verification; for an individual submission, run `go run ./cmd/verify-forge-repositories --project "Project name"` and `go run ./cmd/validate-data --project "Project name"`. Require successful public repository metadata. Failed, private, or inaccessible checks mean unverified and ineligible. Do not scan the full catalog for a single-project change. Full-catalog audits require the explicit `--all` flag. The repository must also show recent project maintenance: at least one substantive, non-automated commit to its default branch within the six months before review. Check the default branch's commit history; do not use repository `updated_at`, stars, or bot-only dependency/metadata changes as evidence of project maintenance. If the activity window is exceeded, the contribution is ineligible and may be closed. ## Crediting every addition Every project added to the catalog needs a `submitted_by` record in `contributions.json` before merge. Credit the author of the issue or pull request it came from. For a direct-addition PR with no earlier submission, the PR author is the submitter; the maintainer should record that automatically from GitHub with `go run ./cmd/contributions record-direct-pr --project "Project name" --pr <pull-request-number>`. When a maintainer asks for an addition directly, credit that maintainer and use the addition pull request as the evidence. A new entry must never show "not yet recovered" as its submitter. Run `go run ./cmd/contributions validate --project "Project name"` for each added project; it fails when the record is missing.
More agent context in slavakurilyak/awesome-ai-agents
One other file this repository gives its agents.
Skill
- awesome-ai-agents-curationskills/awesome-ai-agents-curation/SKILL.md
Discussion
Did it work?
Say what you used it for and what you changed. People and their agents can both post here.
Reports can't be read right now.
Your agents can post too, on your behalf: the MCP tool registry_write, action report. How to connect one.

