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 GDM-Pixel/stellaris-code-search --skill stellaris-exploregit clone --depth 1 https://github.com/GDM-Pixel/stellaris-code-searchWrote 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/gdm-pixel/stellaris-code-search/stellaris-explore)<a href="https://agentmods.dev/skills/gdm-pixel/stellaris-code-search/stellaris-explore"><img src="https://agentmods.dev/badge/skills/gdm-pixel/stellaris-code-search/stellaris-explore/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/gdm-pixel/stellaris-code-search/stellaris-explore"><img src="https://agentmods.dev/badge/skills/gdm-pixel/stellaris-code-search/stellaris-explore.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.00064 | $0.00872 |
| Opus 5 | $0.00032 | $0.00436 |
| Sonnet 5 | $0.00013 | $0.00174 |
| Haiku 4.5 | $0.00006 | $0.00087 |
Grade A, and why
stellaris-explore 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 today.
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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Stellaris explore
search_code classifies the query (query_kind, skipped_vector, QUERY_TOO_BROAD). Trust that. Do not add a second search_code "to be sure".
Grep/rg wins on a known name for occurrences. Stellaris wins for intent, ranked definition, and large-file outline/symbol. Identifier / dotted / quoted string → FTS only (never embeds; empty = no symbol, not a vector guess). Language keywords like export function are refused.
Routing
| Need | Tool |
|---|---|
| Identifier / exact string, definition | search_code (FTS, no vector) or grep/rg |
| All occurrences, logs, lockfiles, generated dumps, CSS | grep/rg |
| Intent / name unknown | search_code (hybrid) |
| File known, ≳150 lines | get_file_outline then get_symbol for ONE body |
| File known, small | Read the file — get_symbol wrapping an 80-line file costs more |
| Impact | get_blast_radius |
| Imports | get_dependents / get_dependencies |
| Docs meaning | search_docs |
Identifier / exact miss (skipped_vector: true, empty) |
grep/rg — do not rephrase as intent |
| Intent miss | rewrite the intent once, or grep/rg if you now have a name |
Optional path on search_code / search_docs / reindex / get_file_tree = another already-indexed project root. Not a reason to index $HOME. Not a substitute for cwd when you will edit.
Default search_code filter is code extensions only. Pass extensions (e.g. [".html"]) to include content files.
Sequence
session_briefingonly at session start (or after compact).- If you already have a file path →
get_file_outline(file ≳150 lines) or Read (small file). Neversearch_codeto rediscover it. Skipget_file_foldedunless outline is not enough. - If you have a symbol name and need the definition →
search_code(name)(FTS, never embeds). Empty → grep/rg. Do not retry as intent. Then outline/symbol on the file it returned. - If you have an intent and no name →
search_codein natural language. Then outline the top file,get_symbolfor ONE body. - All call sites, logs, lockfiles, CSS dumps → grep/rg. Stellaris is a definition/intent index, not
rg.
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.
- today First seen · 61 lines · 64 tokens per session scan A 00766cc16bc8
stellaris-explore is a skill published in the GitHub repository GDM-Pixel/stellaris-code-search (4 stars, last pushed yesterday), licensed MIT. It adds 64 tokens to every session and 872 once invoked, about $0.0003 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-09-09.
Other skills, from other repositories
rawq
Context retrieval engine. Semantic + lexical hybrid search over codebases. Returns ranked code chunks with file paths, line ranges, scope labels, and confidence scores.
context-efficient-coding
Use ContextFlux to minimize coding-agent context and tool calls when exploring, planning, debugging, reviewing, or modifying an unfamiliar or multi-file repository. Trigger for codebase discovery, symbol search, architecture questions, cross-file changes, error tracing, review feedback, test discovery, or any request…
slides
A slide generator that creates PNG images for presentation decks, including simple backgrounds for spoken-video scripts and fuller layouts for standalone presentations.
typescript-project
Modern TypeScript project architecture guide for 2025. Use when creating new TS projects, setting up configurations, or designing project structure. Covers tech stack selection, layered architecture, and best practices.
idea-team
A structured group discussion for exploring a product idea through three roles: researcher, critic, and analogy finder. The roles look for evidence, weaknesses, and useful comparisons.
product-analytics
Product analytics and growth expert. Use when designing event tracking, defining metrics, running A/B tests, or analyzing retention. Covers AARRR framework, funnel analysis, cohort analysis, and experimentation.