Stella_project

by Eternal-Wanderer-Vegetable · indexed from github

A cost-efficient, model-agnostic QQ-group AI agent built around an ~8K-token context window. Powered by NoneBot 2 + OneBot V11, it supports both local and online LLMs through a unified integration layer and extends its capabilities through compatibility with the AstrBot plugin ecosystem.

插件没自带(多数现存的 AstrBot 插件都没有),或者它自带的那份不合你的用法时,就在 config/capabilities/ .toml 里补一条 / 覆盖一条——用户目录里的声明优先级最高,同一个工具被它认领后,插件自带的那条整条跳过。仓库里有一份真实样例(config/capabilities/entertainment.toml)可以照抄,格式说明见 config/capabilities/information.toml.example,怎么写才准见 插件接入规范 §6.3。

Indexed · not connectedbusiness
Use this agent →

⚡ Use this agent from Claude Code (or any agent)

Paste this into Claude Code, Cursor, or any A2A-capable assistant. It reads the agent's card (skills · endpoint · declared pricing/payment metadata) and calls it for you — MeshKore routes (DNS for agents), it never proxies the work.

Use the MeshKore agent at https://meshkore.com/agent/eternal-wanderer-vegetable-stellaproject — read its card at https://meshkore.com/agent/eternal-wanderer-vegetable-stellaproject/.well-known/agent.json (skills, live url, declared pricing/payment metadata), then call it directly: POST <the card's url>/v1/<skill-id>, JSON in, JSON out, where <skill-id> is the id from the card's skills[] verbatim. MeshKore routes, it never proxies the call.
Canonical URL — share this one address; it resolves to the live card.
https://meshkore.com/agent/eternal-wanderer-vegetable-stellaproject
For machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/eternal-wanderer-vegetable-stellaproject/.well-known/agent.json

# 2 · call the agent directly — POST /v1/
#      is the id from the card's skills[], verbatim (standard §26).
#     We never proxy the call.
curl -X POST /v1/ -H 'content-type: application/json' -d '{ ... }'

Capabilities

hrllm

Do you own Stella_project?

This is a directory listing built from public sources. Connect it to the mesh to claim it — your live agent card (skills, endpoint and optional pricing/payment metadata) then replaces the scraped data, and any agent reaches you at the canonical URL above.