Skip to content
HEY Research Lab
Menu

Kosmo Protocol

AI Agents

Is this your project? Claim it →

Agent skills for Kosmo Protocol: launch tokens on Ethereum, BNB, Base, Robinhood Chain and Ink. Your token, your rules.

What HEY knows

Development

Last shipped yesterdayShipping: 1 counted ship in 30 days; latest ship yesterday. Evidence Source

Build Momentum 25How it is measured

Latest: Code changes, week of 2026-10-26 – 2026-11-01 · 3 commits

Token

No token tracked
FollowCreate alertTerminal preview
Get updates

Get updates

Follow puts Kosmo Protocol on your private watchlist; its changes then lead “Since you were last here” when you come back. Following needs an account; browsing never does.

Sign in to follow Kosmo Protocol

No account? Email me Kosmo Protocol’s changes

No account and no password. HEY stores the address and what you asked for, sends one confirmation, and nothing else until you confirm. Every email has a one-click unsubscribe that deletes the address.

Or read its RSS feed.

View latest ship
Share
More detail
Not yet known
Unknown2 gaps: Published packages (not enough yet), API description (no source). Packages name its repository, but none is confirmed as the project’s own.
Compare with…The same summary, with every line’s evidence: snapshot API
What HEY checked — why it says this
Shipping.
“Shipping” by the activity rule: 1 counted ship in the last 30 days, the newest 2026-11-01.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes, week of 2026-10-26 – 2026-11-01 · 3 commitsWhat HEY derivedHEY’s activity rule reads the counted events as “Shipping”.Not concludedIt says what HEY can read of the building, not how good the project is, who is behind it, or what its token will do. Quiet or unknown is not "abandoned".
Verified Builder.
The quality gate found counted building from the project's own sources.
Source8 registered sources, 0 of them context only.ReadRecordsCode changes, week of 2026-10-26 – 2026-11-01 · 3 commitssource:87756671-fd71-4eb4-9377-ca6cd886737dsource:6a5a4add-3e49-4e9d-af64-67e44d495545+3 moreWhat HEY derivedThe quality gate’s stored decision: “Verified Builder”.Not concludedA verified builder is one whose shipping HEY confirmed from public evidence. It does not say who runs the project — that is the ownership claim, a separate check.
Research coverage: HEY can answer 8 of the 10 research questions that apply.
8 of 10 applicable dimensions measured.

Identity

  • IdentityMeasuredRead 4h ago.

Building

  • Building activityMeasuredRead 22m ago.
  • RepositoriesMeasured
  • ReleasesMeasured
  • TimelineMeasured

Official site

  • Official docsMeasuredRead 3h ago.
  • API descriptionNo sourceIts website links no API description.
  • Official site changesMeasuredRead 3h ago.

Code and packages

  • Repository detailsMeasuredRead 4h ago.
  • Published packagesNot enough yetPackages name its repository, but none is confirmed as the project’s own.

Not applicable here: Package advisories, Contract creation, Contract activity, Published source code, Contract interface, Current market, Market history, Supply distribution, Locks, Market checks, Protocol economics.

A count of what HEY has read, never a score: projects are not compared or ordered by it. Unknown is never zero. The same states: coverage API.

Market figures are context only and never change activity status. Methodology
LinksWebsite (opens in a new tab)GitHub (opens in a new tab)X (opens in a new tab)Sources

Latest ship

Checked

Code changes, week of 2026-10-26 – 2026-11-01 · 3 commits kosmo-protocol/kosmo-mcp

Code activitySource-backed

Why it matters: The first week of code changes HEY has recorded for this project.

What changed, in the repository’s own words:

1 active day in kosmo-protocol/kosmo-mcp.

This week HEY looked inside 1 of 3 commits to see what changed: 1 changed code. One code change is enough for the week to count, so HEY stopped there.

Record ship:1125b979… · HEY counts it as building; it does not judge the release’s quality.

View evidence ↗ (opens in a new tab)

Builder activity

Bars: meaningful, source-backed ships per week (count). Weeks run Monday to Sunday, UTC, labelled by their Monday. Commits are aggregated, a code week counted once. Hatched: 10 weeks before HEY began reading this project’s sources — not yet read, not zero.

Build timeline

  1. Code changes this week (since Mon 2 Nov) · 1 commit kosmo-protocol/kosmo-skills

    Code activitySource-backed

    1 active day in kosmo-protocol/kosmo-skills.

    Documentation or maintenance only — not counted as building. This week HEY looked inside 1 commit to see what changed: 1 documentation or maintenance only.

    View evidence: Code changes this week (since Mon 2 Nov) · 1 commit (opens in a new tab)

Other changes on HEY’s record

4 changes on HEY’s record for Kosmo Protocol: 1 new Verified Builder or owner proof · 1 new project on HEY · 2 weeks of code pushed.

All 4 changes for Kosmo Protocol →

The full change record holds 3 more, of kinds this list leaves out — new locks, unlock reminders and HEY’s own research bookkeeping among them. Full record (JSON)

Questions HEY can answer about Kosmo Protocol — as of 2 Nov

Show the answers
Is Kosmo Protocol still being built?
DerivedShipping: 1 counted ship in 30 days; latest ship yesterday. Evidence
What did Kosmo Protocol ship last?
FactCode changes, week of 2026-10-26 – 2026-11-01 · 3 commits — Code activity, yesterday. Evidence
What does HEY not know about Kosmo Protocol?
Unknown2 gaps: Published packages (not enough yet), API description (no source). Packages name its repository, but none is confirmed as the project’s own.

Sources

8 places HEY reads for Kosmo Protocol
1 more source (docs)