StarNet is a local-first desktop harness for creating AI agents and arranging them in a pixel-art space station whose layout represents their capabilities, permissions, and workflow. It lets people run real model calls and tools through multiple bounded agents, using their own provider keys or accounts and optionally messaging the station through chat services. The catalogue entries are skills that extend or support work performed by StarNet agents.
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 skills add androoAGI/starnet --skill llm-wikigit clone --depth 1 https://github.com/androoAGI/starnetWrote 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/androoagi/starnet/llm-wiki)<a href="https://agentmods.dev/skills/androoagi/starnet/llm-wiki"><img src="https://agentmods.dev/badge/skills/androoagi/starnet/llm-wiki/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/androoagi/starnet/llm-wiki"><img src="https://agentmods.dev/badge/skills/androoagi/starnet/llm-wiki.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00041 | $0.03881 |
| Opus 5.5 | $0.00016 | $0.01552 |
| Sonnet 5.5 | $0.00008 | $0.00776 |
| Haiku 4.5 | $0.00004 | $0.00388 |
Grade A, and why
llm-wiki scanned grade A with 0 findings 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 12d 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 305 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LLM Wiki
Build and maintain a persistent, compounding knowledge base as interlinked Markdown files. Based on Andrej Karpathy's LLM Wiki pattern (https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f).
Unlike retrieval that rediscovers knowledge from scratch on every question, the wiki compiles knowledge once and keeps it current. Cross-references are already there. Contradictions have already been flagged. The synthesis reflects everything ingested.
Division of labor: the Commander curates sources and directs the analysis. You summarize, cross-reference, file, and keep everything consistent.
When to use
- The Commander asks to create, build, or start a wiki or knowledge base.
- The Commander asks to ingest, add, or process a source into their wiki.
- The Commander asks a question and a wiki already exists at the saved path.
- The Commander asks to lint, audit, or health-check the wiki.
- The Commander refers to their wiki, knowledge base, or research notes.
Wiki location
- Check
notebook.readfor a saved wiki path. If none is saved, ask the Commander where the wiki should live, then save the answer withnotebook.write(for example "LLM wiki: "). - Default: a
wiki/folder in your own workspace (relative paths work with no extra prompt). - If the Commander wants it somewhere else (for example a
wikifolder in their home directory, or inside their notes vault), use that absolute path. The first file-tool call there asks the Commander to trust the folder; an unattended routine can only use a folder that was already trusted.
The wiki is only a folder of Markdown files. It opens in any editor or Markdown notes app. No database, no special tooling.
Architecture: three layers
wiki/
├── SCHEMA.md # Conventions, structure rules, domain config
├── index.md # Sectioned content catalog with one-line summaries
├── log.md # Chronological action log (append-only, rotated yearly)
├── raw/ # Layer 1: immutable source material
│ ├── articles/ # Web articles, clippings
│ ├── papers/ # PDFs, papers
│ ├── transcripts/ # Meeting notes, interviews
│ └── assets/ # Images, diagrams referenced by sources
├── entities/ # Layer 2: entity pages (people, orgs, products, models)
├── concepts/ # Layer 2: concept and topic pages
├── comparisons/ # Layer 2: side-by-side analyses
└── queries/ # Layer 2: filed query results worth keeping
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 12d ago First seen · 305 lines · 41 tokens per session scan A 81ebc990398f
llm-wiki is a skill published in the GitHub repository androoAGI/starnet (1,468 stars, last pushed 3d ago), licensed MIT. It adds 41 tokens to every session and 3,881 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-04.
Other skills, from other repositories
context-engineering
Use when designing, reviewing, or debugging how an agent's context window gets filled, pruned, or shared — choosing what loads at boot versus on demand, sizing an install or an always-loaded file, fixing an agent that drifts, repeats itself, or forgets constraints mid-task, planning compaction or summarization…
claude-compaction-restore
Use when a Claude Code session is about to compact, has just compacted, reached its context limit, resumed after /compact, or must rebuild its working picture of a long-running seat from its own restore map, its JSONL transcript and the files it touched.
retiring-and-inheriting-a-seat
Use when you are a sitting agent near your context threshold (85%) and a PLANNED seat transition is due — retire deliberately and hand your seat to a fresh successor primed from a packet, rather than let compaction degrade you. Covers the handover packet, the append-only lineage ledger (one row per tenure)…
knowledge-base
Skill "knowledge-base" from Pinvou/pinvou-agent, covering ima knowledge base, operations, routing rules, examples and file upload guard.
notes
Skill "notes" from Pinvou/pinvou-agent, covering ima notes, operations, write rules, examples and response handling.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…