Borrowing it
Nothing to install: this file belongs to stellar-experimental/stellar-raven. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/stellar-experimental/stellar-raven/main/.agents/skills/retrieval-system-audit/SKILL.mdgit clone --depth 1 https://github.com/stellar-experimental/stellar-ravenWrote 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/stellar-experimental/stellar-raven/retrieval-system-audit)<a href="https://agentmods.dev/skills/stellar-experimental/stellar-raven/retrieval-system-audit"><img src="https://agentmods.dev/badge/skills/stellar-experimental/stellar-raven/retrieval-system-audit/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/stellar-experimental/stellar-raven/retrieval-system-audit"><img src="https://agentmods.dev/badge/skills/stellar-experimental/stellar-raven/retrieval-system-audit.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.00066 | $0.01142 |
| Opus 5 | $0.00033 | $0.00571 |
| Sonnet 5 | $0.00013 | $0.00228 |
| Haiku 4.5 | $0.00007 | $0.00114 |
Grade A, and why
retrieval-system-audit 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 9d 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Retrieval System Audit
Measure the complete retrieval system before changing it. Ship only general improvements that survive real endpoint calls and reviewed golden questions.
Use the companion runbooks
- Read
PLAN.md,ARCHITECTURE.md,eval/EVALS.md, andeval/qa/README.md. - Use the global
herdrskill to run an explicitly requested multi-model audit, one agent per pane. - Use
run-evalsfor every evaluation run and spend decision. - Use
golden-truthbefore changing a golden question or answer. - Use
improvements-pipelinefor verified upstream defects. - Use
live-drift-resolutionfirst when the committed catalog differs from the live surfaces.
Keep fixed boundaries
- Treat the manifest as the exposed surface.
- Keep exact operation and skill identifiers.
- Keep data, soft-empty, and error responses distinct.
- Keep secrets and service traffic outside model-authored code.
- Do not call a paid or side-effecting service operation during inventory work.
- Do not tune production behavior for one question.
- Prefer deletion, simpler descriptions, and existing interfaces before new code.
- Keep raw paid results local and gitignored.
- Give Git, spending, deployment, and external filing authority to the coordinator.
Run the audit
1. Isolate and pin
Create a dedicated Git worktree and a round ledger under .agents/rounds/. Record the revision, clean-tree digest, manifest digest, runner digest, corpus digest, and evaluation gates.
Run the free baseline from AGENTS.md. Compile generated artifacts and verify that regeneration leaves the tree clean.
2. Build one surface ledger
Inventory every exposed operation and whole skill. Compare the committed manifest, generated specification, adapters, live catalog, and fresh-client MCP descriptions.
Record each input schema, output schema, retrieval description, retrieval profile, response class, authority scope, safety class, and evaluation coverage. Use references/evidence-contract.md for the required fields.
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.
- 9d ago First seen · 104 lines · 66 tokens per session scan A a9aed944c373
retrieval-system-audit is a skill published in the GitHub repository stellar-experimental/stellar-raven (6 stars, last pushed today), licensed Apache-2.0. It adds 66 tokens to every session and 1,142 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-08-31.
Other skills, from other repositories
potpie-cli
Use when the task is centered on running, explaining, configuring, or troubleshooting the potpie command: doctor, login, pot management, source registration, search, graph workbench reads/writes, and pot scope behavior.
potpie-debug-memory
Use while debugging or troubleshooting failures, flaky tests, incidents, production alerts, CI failures, local dev setup issues, repeated bugs, prior fixes, failed attempts, and verification history.
x-bug2rag
A knowledge-capture tool that turns reusable bug explanations into a local RAG collection, meaning a searchable store of text that an agent can retrieve later. It records the trigger, incorrect implementation, correct implementation, and observable difference.
ingest
Populate the gnosis-mcp knowledge base — from local files, git history, or a crawled website. Handles the full matrix of flags (--force, --prune, --wipe, --embed, --include-crawled) in one place.
setup
First-time setup wizard for Gnosis MCP. Install, init the database, ingest a docs folder, wire your editor — in that order.
tune
Find the chunk-size and retrieval config that maximizes quality on YOUR corpus. Sweeps chunk sizes, runs a golden-query set, reports nDCG / MRR / Hit@5. Use after first ingest or whenever your corpus changes shape significantly.