Borrowing it
Nothing to install: this file belongs to sachinshelke/codevira. 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/sachinshelke/codevira/main/.claude/skills/epistemic-honesty/SKILL.mdgit clone --depth 1 https://github.com/sachinshelke/codeviraWrote 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/sachinshelke/codevira/epistemic-honesty)<a href="https://agentmods.dev/skills/sachinshelke/codevira/epistemic-honesty"><img src="https://agentmods.dev/badge/skills/sachinshelke/codevira/epistemic-honesty/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/sachinshelke/codevira/epistemic-honesty"><img src="https://agentmods.dev/badge/skills/sachinshelke/codevira/epistemic-honesty.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.00106 | $0.01461 |
| Opus 5 | $0.00053 | $0.00731 |
| Sonnet 5 | $0.00021 | $0.00292 |
| Haiku 4.5 | $0.00011 | $0.00146 |
Grade A, and why
epistemic-honesty 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 10d 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 — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Epistemic honesty — calibrate every claim
You shipped codevira v2.0.0 with 23 silent-failure bugs because you stated "all tests pass → ready to ship" as a definitive truth. It wasn't. Test count is a proxy, not proof. This skill makes you calibrate every confident statement against actual evidence before saying it.
When this skill triggers
Anytime you are about to write any of:
- "This works."
- "Tests pass."
- "Done."
- "Fixed."
- "Ready to ship."
- "The bug is X."
- "The solution is Y."
- "It's because of Z."
- "All N items completed."
- "I verified ..."
The 4-statement contract for every claim
Before any definitive statement, output the 4-line confidence block:
Confidence: HIGH / MEDIUM / LOW
Evidence: <what you actually observed — file path, command output, test result>
Could fail because: <2-3 ways your claim could still be wrong>
What I don't know: <gaps in your verification>
Skip ANY of these four and the claim is unverified. Examples:
Example 1 — verified claim
Claim: ruff lint passes on mcp_server/
Confidence: HIGH
Evidence: ran `ruff check mcp_server` — exit code 0, no output
Could fail because: ruff doesn't catch type errors; another linter
(mypy) may still fail
What I don't know: whether mypy passes — haven't run it
Example 2 — unverified claim (refuse to make it)
Claim: "the configure command detects correctly"
Confidence: LOW
Evidence: NONE — I read the code once, several turns ago
Could fail because: I haven't re-read since; the user's recent log
shows configure writing to in-repo .codevira/ which contradicts
my recollection
What I don't know: actual current behavior of configure
→ Cannot make this claim without first re-reading and testing.
Example 3 — bug diagnosis
Claim: "the Claude Desktop disconnects are caused by sentence-
transformers loading on tools/list critical path"
Confidence: MEDIUM
Evidence: log shows tools/list response arrived 5s after transport
closed at 80ms; log includes "Loading weights 103/103"
Could fail because: there could be a different cause that happens
to correlate with the load time (e.g. macOS power management)
What I don't know: whether Claude Code (which works) takes the same
time for tools/list — if it does, the load time isn't the cause
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.
- 10d ago First seen · 183 lines · 106 tokens per session scan A a3ce9afd76c2
epistemic-honesty is a skill published in the GitHub repository sachinshelke/codevira (12 stars, last pushed 25d ago), licensed MIT. It adds 106 tokens to every session and 1,461 once invoked, about $0.0005 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 skills, from other repositories
replen-onboard
One-time Replen setup — profiles your active repos so matches are relevant, not generic. Runs autonomously in the background. Invoke with /replen-onboard.
replen
Triage today's Replen matches for this repo: a verdict and effort estimate per candidate, grounded in your code. Invoke with /replen or "what's new from Replen?".
memory-distill
Destilliert rohe Staging-Inbox-Bullets (staging/captured.md) in bleibende, getypte Memory-Dateien. Verwende diesen Skill, wenn der User 'distill', 'Staging aufräumen', 'Inbox abarbeiten', 'Memory verdichten' sagt oder nach einem Ingest-Lauf oder Staging-Nag.
memory-sync
Audits and updates local agent memory. Scans configured coding folders, registers or ignores new projects, writes PROJECTS.md, syncs your Agent injection. Use when the user says Bestandaufnahme, memory sync, neues Projekt, inventory, Projekte updaten, register project, or wants agents to know a new repo path.
docs-search
Search local framework documentation (Svelte 5, FastAPI, Tailwind, Tauri, Next.js, Supabase) and AI Models documentation (Claude 3.7/3.5, GPT-4.5/o1/o3, Gemini 2.0/3.0, DeepSeek V3/R1, Qwen 2.5 Coder, benchmarks, pricing, routing) via agents-docs MCP before guessing API methods or hallucinating stale model knowledge.
docs-sync
Synchronize and maintain fresh framework documentation in /.agents/docs/ using agents-docs catalog or custom URLs.