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/golden-truth/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/golden-truth)<a href="https://agentmods.dev/skills/stellar-experimental/stellar-raven/golden-truth"><img src="https://agentmods.dev/badge/skills/stellar-experimental/stellar-raven/golden-truth/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/golden-truth"><img src="https://agentmods.dev/badge/skills/stellar-experimental/stellar-raven/golden-truth.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 48 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00071 | $0.04199 |
| Opus 5.5 | $0.00028 | $0.01680 |
| Sonnet 5.5 | $0.00014 | $0.00840 |
| Haiku 4.5 | $0.00007 | $0.00420 |
Grade A, and why
golden-truth 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 28d 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 — 265 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Golden truth verification
North star
The golden Q→A corpus is the gospel every eval round is judged against. A wrong agent answer costs one verdict; a wrong golden silently corrupts every future round, every A/B, every re-judge — and a golden "corrected" from thin evidence is worse than the error it replaced, because it now carries the authority of a review. Therefore:
Never change gospel from a single source class. Live-probing the corpus, or reading one docs page, is discovery — not verification. Gospel changes require multi-source triangulation across independent source classes, and disputed facts are encoded as disputes, never pinned.
This skill governs ANY change to judge-facing gospel — question, golden.answer,
golden.keyFacts, golden.avoid, golden.notes, tags.freshness, tags.trap — and to the
judge-blind truth block that carries its provenance. The corpus is owned: edits land
directly in the per-case file eval/qa/corpus/battery/<category>/<id>.json, reviewed like
code. The CI gospel-change lint (eval/qa/lint-corpus.mjs, diff-aware against the merge
base) refuses any judge-facing change whose truth.verified did not change in the same diff
with non-empty evidence + rootCause — that lint is the successor to the retired
override-file enforcement, and it moves the check from compile-time bookkeeping to the moment
of change.
The same evidence bar applies to a separately frozen provenance-bearing suite when its contract invokes this skill. Keep that suite in its contract-owned file. Do not compile it into the battery or existing routing lanes. Evaluation lanes never merge.
Step 1 — classify the truth domain (this picks the verification standard)
| Domain | What gospel means | Examples |
|---|---|---|
| real-world / protocol | Authoritative primary sources + source code. The corpus/aggregators may lag or be wrong — that's an improvements/ finding, never an excuse to weaken the golden. |
RPC limits, CLI commands, SEP semantics, build targets |
| corpus-grounded | What the live community corpora (Scout, Lumenloop) support NOW, cross-checked against the real world. Distinguish real-world-confirmed from corpus-only (in the aggregator, no external footprint). Corpus-only facts may appear in goldens but must be labeled so graders treat them as source-relative. A corpus-vs-world contradiction → improvements/ finding + grade leniently on both sides. |
Regional community events, builder directories, project records |
| freshness-sensitive | A behavior, never a pinned value. Point-in-time figures require an asOf date in the golden text itself, tags.freshness: "scheduled", and a truth.reverifyBy date. |
SCF amounts, country counts, versions, rosters |
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.
- 28d ago Changed · -8 lines 78fb8c3c2727
- 1mo ago Changed · +2 lines 200aa8759567
- 1mo ago First seen · 271 lines · 71 tokens per session scan A e8b1552226a1
golden-truth is a skill published in the GitHub repository stellar-experimental/stellar-raven (13 stars, last pushed yesterday), licensed Apache-2.0. It adds 71 tokens to every session and 4,199 once invoked, about $0.0003 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-08-31.
Other skills, from other repositories
unified-code-review
Risk-first code review for PRs and branch audits: blast-radius triage, agent-authored discipline (tests first, intent evidence), call-graph pincer for integration defects between modules, then structural code-judo bar. Use when reviewing PRs, auditing agent-written diffs, catching rubber-stamp green CI, or wiring bugs…
migration-review
Review database migration files when a change adds or modifies paths under migrations/. Use it before merge to collect forward, rollback, locking, and data-safety evidence.
otto-pr-review-loop
Run Polly and OCR on a PR until all findings settle.
adk-go-self-review
Review an ADK Go change the way a maintainer will — a fresh-context pass over the whole diff, five lenses (correctness and tests, scope, simplicity, style, adk-python parity), and the mutation check that proves your tests pin the change. Use before opening a PR, before any later push that changes code, and when asked…
learn-from-sage
Detection-gap (miss) analysis for Code Review Sage. Learn from shipped fixes, acted-on human comments, and design outcomes to close reviewer blind spots. Inline during review stages a candidate; a human triggers a one-shot AI consolidation into the live ruleset.
no-mistakes
Validate committed feature-branch changes through the no-mistakes pipeline: intent, rebase, review, test, docs, lint, push, PR, and CI. Use when the user asks to run no-mistakes, ship safely, validate before pushing, or gate a change before it reaches upstream.