repos
Skill3 starsChanged 6 months agoMITView on GitHub
Query repos.ecosyste.ms for repository metadata across GitHub, GitLab, Bitbucket, Codeberg, SourceHut and 1900+ other forges. Use when looking up a repo by URL, listing an owner's repos, fetching tags/releases/manifests, finding which repositories depend on a package, or generating an SBOM for a repo.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- microsoft/TokenEconomizertheir own version, first seen Nov 1, 2026
- lukasrepublic/agentic-foundrytheir own version, first seen Oct 11, 2026
- jorekai/skillstheir own version, first seen Sep 7, 2026
- ecosyste-ms/skillsword for word, first seen May 5, 2026
Other versions4 projects use a version of this.
Word for word · 1
- ecosyste-ms/skills★ 3100% same
Edited · 0
None found.
Wrote their own version · 3
- microsoft/TokenEconomizer★ 5ksame name
- lukasrepublic/agentic-foundry★ 1same name
- jorekai/skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository5 other files it gives its agents.
- advisoriesSkill
- commitsSkill
- dockerSkill
- issuesSkill
- packagesSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 11
All responses are JSON. No auth required.
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
ecosyste.ms Repos API
Base URL: https://repos.ecosyste.ms/api/v1
All responses are JSON. No auth required. Set a User-Agent header identifying yourself. Unauthenticated clients share a rate limit and may see 429.
Full OpenAPI spec: https://repos.ecosyste.ms/docs/api/v1/openapi.yaml
Look up a repository
By URL or purl. Returns a single object (or 404).
curl -s 'https://repos.ecosyste.ms/api/v1/repositories/lookup?url=https://github.com/rails/rails'
curl -s 'https://repos.ecosyste.ms/api/v1/repositories/lookup?purl=pkg:github/ecosyste-ms/repos'Useful fields: full_name, description, stargazers_count, forks_count, archived, fork, license, language, topics, default_branch, pushed_at, homepage, metadata.files (readme, license, changelog, funding paths), commit_stats.
Hosts
Host names are case sensitive: GitHub, gitlab.com, Bitbucket.org, codeberg.org, salsa.debian.org. List all with GET /hosts.
Repository full names containing / must be URL-encoded (%2F).
curl -s 'https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/rails%2Frails'
curl -s 'https://repos.ecosyste.ms/api/v1/hosts/gitlab.com/repositories/gitlab-org%2Fgitlab'Owners
curl -s 'https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/rails'
curl -s 'https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/rails/repositories?sort=stargazers_count&order=desc'
curl -s 'https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/lookup?email=andrewnez@gmail.com'Tags, releases, manifests, SBOM
curl -s 'https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/rails%2Frails/tags'
curl -s 'https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/rails%2Frails/releases'
# parsed dependency manifests for the default branch
curl -s 'https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/numpy%2Fnumpy/manifests'
# manifests at a specific tag
curl -s 'https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/numpy%2Fnumpy/tags/v2.0.0/manifests'
# CycloneDX SBOM
curl -s 'https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/numpy%2Fnumpy/sbom'Package usage (dependent repositories)
Find repositories that depend on a package. Ecosystem here is the package manager name (npm, pypi, cargo, bundler, go, maven, nuget, composer), not the registry hostname.
# usage summary
curl -s 'https://repos.ecosyste.ms/api/v1/usage/npm/lodash'
# repos that depend on it
curl -s 'https://repos.ecosyste.ms/api/v1/usage/npm/lodash/dependent_repositories?per_page=20&sort=stargazers_count&order=desc'
# raw dependency edges (keyset pagination via ?after=ID)
curl -s 'https://repos.ecosyste.ms/api/v1/usage/npm/lodash/dependencies'Topics
curl -s 'https://repos.ecosyste.ms/api/v1/topics/cli?fork=false&archived=false'Pagination and filtering
List endpoints accept ?page=N&per_page=N. Repository lists accept fork=false, archived=false, created_after=ISO8601, updated_after=ISO8601, sort and order.
When to use
- The user asks about a repository on any forge (not just GitHub)
- Listing what dependencies a repo declares without cloning it
- Finding which projects use a given package in the wild
- Listing an organisation's repos sorted by stars or recency
- Getting a CycloneDX SBOM for an arbitrary public repo
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
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.

