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 code-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/code-wiki)<a href="https://agentmods.dev/skills/androoagi/starnet/code-wiki"><img src="https://agentmods.dev/badge/skills/androoagi/starnet/code-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/code-wiki"><img src="https://agentmods.dev/badge/skills/androoagi/starnet/code-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.00043 | $0.03530 |
| Opus 5.5 | $0.00017 | $0.01412 |
| Sonnet 5.5 | $0.00009 | $0.00706 |
| Haiku 4.5 | $0.00004 | $0.00353 |
Grade A, and why
code-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 — 393 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codebase Wiki
Generate a full wiki for any codebase: overview, architecture, per-module deep dives, and Mermaid class and sequence diagrams. It works on local repos, private repos, and any language, with the station's own tools (fs.search, fs.read, fs.write, shell.exec). No containers, no external services, no extra dependencies.
This skill produces reference documentation (what and how). It does not produce strategic narrative (why the project exists).
When to use
- The Commander says "document this codebase", "generate a wiki", or "make architecture diagrams".
- Onboarding to an unfamiliar repo and wanting a structured reference.
- The Commander points at a repository URL and asks for documentation.
- A stable artifact (Markdown + Mermaid) that renders on common code hosts is needed.
Do NOT use it for:
- Single-file or single-function documentation: answer directly.
- Reference for one specific endpoint: read the file and answer inline.
- Strategic "why does this exist" narrative.
- A codebase the Commander is actively changing in this session: answer questions as they come.
Prerequisites
giton the PATH for repo SHA tracking and remote clones (WORKBENCH).- Optional: language-breakdown statistics with the Codebase Inspection recipe (
skill.viewwithlibrary:codebase-inspection), if installed.
Where the wiki goes
- Default:
code-wiki/<repo-name>/in your workspace. - If this session is scoped to the target project, relative paths land inside that repo. Confirm with the Commander first, and write into the repo (
docs/wiki/) only when they ask for it.
Quick reference
| Step | Action |
|---|---|
| 1 | Resolve the target: a local path, or git clone --depth 50 <url> into the workspace |
| 2 | Scan the structure: tree, manifest files, README |
| 3 | Pick 8-10 modules to document |
| 4 | Write README.md (overview + module map) |
| 5 | Write architecture.md with a Mermaid flowchart |
| 6 | Write per-module docs in modules/ |
| 7 | Write diagrams/class-diagram.md (Mermaid classDiagram) |
| 8 | Write diagrams/sequences.md (Mermaid sequenceDiagram, 2-4 workflows) |
| 9 | Write getting-started.md |
| 10 | Write api.md if applicable, else skip |
| 11 | Write .codewiki-state.json |
| 12 | Report the paths to the Commander |
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 · 393 lines · 43 tokens per session scan A abc34dc64333
code-wiki is a skill published in the GitHub repository androoAGI/starnet (1,468 stars, last pushed 3d ago), licensed MIT. It adds 43 tokens to every session and 3,530 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
hps-academic-paper
A review deck on compositional generalization in large language models — the field map, the gap, the evidence, and open questions. Built as a decision-grade academic research deck for PI, lab group, reviewers.
fs-notebook-tabs
A computer-science capstone: an on-device ML keyboard that predicts next words privately — problem, method, evaluation, and defense answers. Built as a decision-grade coursework defense deck for professor, defense committee.
hps-bauhaus
A visual-design fundamentals course for new brand designers — grid, type, color, and the exercises that build the eye. Built as a decision-grade professional training deck for junior designers, new hires.
hps-memphis-pop
A pop-culture retrospective on how 1980s design language shaped today's apps — the scenes, the turning point, and the takeaway. Built as a decision-grade story deck for talk audience, design community.
html-ppt-zhangzara-pin-and-paper
A field-biology capstone on urban pollinator decline — the survey design, the data, the contribution, and the caveats. Built as a decision-grade coursework defense deck for faculty reviewers.
html-ppt-zhangzara-cartesian
An economics senior thesis on the employment effects of local minimum-wage increases — identification strategy, evidence, and limitations. Built as a decision-grade coursework defense deck for thesis committee.