Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/siriusneo/staragent/staragent-devnpx skills add SiriusNEO/StarAgent --skill staragent-devgit clone --depth 1 https://github.com/SiriusNEO/StarAgentWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/siriusneo/staragent/staragent-dev)<a href="https://agentmods.dev/skills/siriusneo/staragent/staragent-dev"><img src="https://agentmods.dev/badge/skills/siriusneo/staragent/staragent-dev.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00036 | $0.01029 |
| Opus 5 | $0.00018 | $0.00515 |
| Sonnet 5 | $0.00007 | $0.00206 |
| Haiku 4.5 | $0.00004 | $0.00103 |
Grade A, and why
staragent-dev scanned grade A with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Use `curl --noproxy '*'` for LAN or Tailscale endpoints when proxy variables may be set. How it starts
The opening of the file, as written. The whole thing — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
StarAgent Development
StarAgent is a tmux-first control plane for coding CLI sessions. Treat live tmux state as the behavioral source of truth. Config and persisted metadata should only enrich or route live tmux state, not replace it.
Architecture
- Hub: web dashboard, coordinator, local node, and proxy for remote node APIs.
- Node: machine-local API that owns tmux sessions and workspace file access.
- Agent session: tmux session running a coding CLI.
- System session: tmux session running infrastructure such as
staragent-hub,staragent-node, orstaragent-tailscaled. - Terminal: live tmux PTY view.
- Chat: transcript projection from tmux pane output using CLI-specific parsers.
Keep the agent vs node vocabulary clean: agents are coding CLIs, nodes are machines.
Key Files
staragent/main.py: Typer CLI commands.staragent/hub.py: node registry and remote request helpers.staragent/node/app.py: remote node API.staragent/dashboard/app.py: Hub dashboard routes and API surface.staragent/runtime.py: tmux session operations.staragent/status.py: session collection and live status.staragent/transcript.pyandstaragent/session_parser.py: Chat transcript parsing.staragent/presets.py: coding CLI command presets.staragent/dashboard/templates/: Jinja views.staragent/dashboard/static/: CSS and browser-side JS.
Development Rules
- Keep tmux as the source of truth.
- Keep local and remote behavior aligned; remote sessions should go through the node API like normal network traffic.
- Preserve the distinction between
agentandsystemsessions. - Avoid compatibility aliases for renamed concepts unless explicitly requested. This project prefers clean refactors.
- Keep StarAgent runtime files project-local under
.staragent/unlessSTARAGENT_STATE_DIRexplicitly overrides it. - Keep Tailscale-specific operational docs under
tailscale/; core StarAgent code should only require a reachable endpoint. - For UI changes, check desktop and mobile behavior for Sessions, Nodes, Chat, Terminal, File Explorer, and Changed Files.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 4d ago First seen · 101 lines · 36 tokens per session scan A 2bf5135ab927
staragent-dev is a skill published in the GitHub repository SiriusNEO/StarAgent (56 stars, last pushed yesterday), licensed MIT. It adds 36 tokens to every session and 1,029 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
html-artifacts
Author the HTML for a plan artifact, dashboard iframe, or Slack attachment — structure, design plan, available runtime, theming, and craft. Read this before writing HTML for saveplan, outputiframe, or slackattachhtml.
bootstrap-repo-analysis
First-time analysis of a repository with no prior reviewer outcomes. Crawl historical merged-PR review feedback with the gh CLI (plus any preloaded samples), extract the team's review norms, and synthesize the initial per-repo review-style prompt. Use this for a cold-start repo; use continual-learning instead once the…
langbot-eba-adapter-dev
Build, refactor, and test LangBot platform adapters for the Event-Based Agents architecture. Use when adding or migrating Telegram, Discord, or other messaging platform adapters to the EBA adapter layout, validating unified event/message conversion, writing live adapter probes, or using standalone plugin runtime plus…
langbot-plugin-dev
Develop, debug, and test LangBot plugins. Use when creating new LangBot plugins, fixing plugin bugs, setting up a LangBot test environment, or testing plugins via WebSocket. Covers plugin component architecture (EventListener, Command, Tool), the plugin SDK API (invokellm, getllmmodels, sendmessage, plugin storage)…
langbot-dev
Develop, build, and debug the LangBot core backend and web frontend. Use when working inside the LangBot repository — backend (Python/Quart, src/langbot/pkg), the Vite/React web UI, HTTP API controllers/services, Alembic migrations, or the MCP server. Covers the dev environment (uv, pnpm), repo layout, the API auth…
langbot-mcp-ops
Operate a LangBot instance through its built-in MCP (Model Context Protocol) server. Use when an AI agent needs to manage LangBot — list/create/update/delete bots, pipelines, models, knowledge bases, MCP servers, and skills — over MCP instead of raw HTTP. Covers the /mcp endpoint, API-key auth (web-UI lbk keys and the…