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 agents/madappgang/dingo/astro-reviewergit clone --depth 1 https://github.com/MadAppGang/dingoWhat 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.01114 | $0.05469 |
| Opus 5 | $0.00557 | $0.02735 |
| Sonnet 5 | $0.00223 | $0.01094 |
| Haiku 4.5 | $0.00111 | $0.00547 |
Grade A, and why
astro-reviewer 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 yesterday.
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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- yesterday First seen · 569 lines · 1,114 tokens per session scan A 2da842f10765
astro-reviewer is an agent published in the GitHub repository MadAppGang/dingo (1,911 stars, last pushed 1mo ago), with no licence file. It adds 1,114 tokens to every session and 5,469 once invoked, about $0.0056 per session on Opus 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-08-30.
Other agents, from other repositories
demo-site
Owns the fitter demo/documentation site under demo/ — the WebAssembly playground, the docs, the examples gallery, and the GitHub Pages deploy. Use for any work on demo/index.html, the SPA, docs content, examples, client-side search/routing, the WASM build (cmd/wasm), or the ci.yaml pages job. Trigger phrases: "demo…
deploy-reviewer
Reviews fold's deployment surface — the Helm chart's rendered output, Kubernetes security posture, the four Dockerfiles, and the compose stack — for what only shows up in the manifest rather than in the templates. Use after changes under deploy/, before a chart release, or when auditing how fold actually runs in a…
release-verifier
Verifies a published fold release end to end from the outside — archives, checksums and their cosign signature, SBOMs, the four ghcr images, the OCI chart, and every sigstore attestation. Use after a tag's release workflow goes green, before announcing a release, or when someone asks whether a published artifact is…
CREATING_AGENTS
Station agents are intelligent AI assistants that can execute tasks using MCP (Model Context Protocol) tools. This guide covers creating, configuring, and deploying agents.
station-operator
Station AI agent operator. Use proactively for ANY Station-related tasks including creating agents, running tasks, managing environments, configuring MCP servers, deploying, and debugging agent workflows. Has full access to Station's 55+ MCP tools.
security-auditor
Security review of fold changes against the documented threat model — inbound auth chain, deny-by-default policy, credential confinement, tenant isolation, and the trust boundaries in docs/security-model.md. Use for changes to auth/, policy/, host validation, EMA, discovery, or credential handling, and for periodic…