confidence-scorer

confidence-scorer is a skill for Claude Code from a-ariff/ariff-claude-plugins. It costs 51 tokens per session (547 once invoked), scanned A, original, MIT.

A response-review method that assigns a confidence score from 0 to 100 to each claim. The score indicates whether a statement was verified, supported by evidence, inferred, or uncertain.

In plain words
What is it for?
It helps annotate factual answers, research summaries, and technical explanations with confidence levels. It is useful when users need to judge which claims require further checking.
Why use it?
It makes the level of trust behind an answer visible instead of presenting every statement as equally certain. This helps readers separate checked facts from guesses.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the confidence-scorer plugin — 1 skill shipped together

Good fit It helps annotate factual answers, research summaries, and technical explanations with confidence levels. It is useful when users need to judge which claims require further checking.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/a-ariff/ariff-claude-plugins/confidence-scorer
Install

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.

Any agent
npx skills add a-ariff/ariff-claude-plugins --skill confidence-scorer
Clone the repo
git clone --depth 1 https://github.com/a-ariff/ariff-claude-plugins

Made for: Claude Code.

Or install confidence-scorer, the plugin that ships this one along with the rest of its 1 skill.

Wrote 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.

agentmods badge for confidence-scorer

README.md
[![agentmods](https://agentmods.dev/badge/skills/a-ariff/ariff-claude-plugins/confidence-scorer/github.svg)](https://agentmods.dev/skills/a-ariff/ariff-claude-plugins/confidence-scorer)
Your own site
<a href="https://agentmods.dev/skills/a-ariff/ariff-claude-plugins/confidence-scorer"><img src="https://agentmods.dev/badge/skills/a-ariff/ariff-claude-plugins/confidence-scorer/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.

agentmods 80×15 button for confidence-scorer

Your own site · 80×15
<a href="https://agentmods.dev/skills/a-ariff/ariff-claude-plugins/confidence-scorer"><img src="https://agentmods.dev/badge/skills/a-ariff/ariff-claude-plugins/confidence-scorer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 51 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 547 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00051 $0.00547
Opus 5 $0.00026 $0.00273
Sonnet 5 $0.00010 $0.00109
Haiku 4.5 $0.00005 $0.00055

Measured 9d ago against content hash 6ddaf4b222b3, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

confidence-scorer 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.

plugins/confidence-scorer/skills/confidence-scorer/SKILL.md · 58 lines

How it starts

The opening of the file, as written. The whole thing — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Confidence Scorer

Assign a numerical confidence score to every claim, so users know exactly how much to trust each part of your response.

Scoring scale

Score Meaning Example
95-100 Verified against code just now "src/auth.ts exports validateToken (I just read it)"
80-94 Confirmed by search/tool output "Grep found 3 references to this function"
60-79 Strong inference from evidence "Based on the error handling pattern, this likely..."
40-59 Educated guess from general knowledge "Express middleware typically handles this by..."
20-39 Uncertain, limited evidence "This might be related to the session config..."
0-19 Speculation, no evidence "It could be a race condition, but I haven't checked"

How to apply

After making claims, add confidence annotations:

"The authentication flow works as follows:

  • Users hit /api/login which calls validateUser() [95 - read the route file]
  • Passwords are hashed with bcrypt [90 - confirmed in package.json]
  • Sessions are stored in Redis [70 - inferred from redis import, haven't confirmed config]
  • Session timeout is 24 hours [40 - common default, haven't checked actual config]"

Threshold rules

Situation Minimum score to state as fact
Code changes 80+ (must have read the code)
Security advice 90+ (must have verified)
Production commands 95+ (must be certain)
Explanations 60+ (inference OK if labeled)
Suggestions 40+ (clearly framed as suggestions)

When to score

Use confidence scoring when:

  • The user asks "are you sure?"
  • You're giving advice that will be acted on
  • Multiple possible explanations exist
  • You're working with unfamiliar code
  • The stakes are high (production, security, data)

Improving low scores

If a claim scores below the threshold:

  1. Use tools to gather more evidence
  2. Read the relevant files
  3. Search for confirming/denying evidence
  4. Re-score based on new evidence
  5. If still low, state it as uncertain rather than fact

Read the full file on GitHub · 58 lines

Changes

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.

  1. 9d ago First seen · 58 lines · 51 tokens per session scan A 6ddaf4b222b3

Subscribe to this mod's changes

confidence-scorer is a skill published in the GitHub repository a-ariff/ariff-claude-plugins (14 stars, last pushed 5mo ago), licensed MIT. It adds 51 tokens to every session and 547 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-30.