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 mthines/agent-skills --skill confidencegit clone --depth 1 https://github.com/mthines/agent-skillsWrote 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/mthines/agent-skills/confidence)<a href="https://agentmods.dev/skills/mthines/agent-skills/confidence"><img src="https://agentmods.dev/badge/skills/mthines/agent-skills/confidence/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/mthines/agent-skills/confidence"><img src="https://agentmods.dev/badge/skills/mthines/agent-skills/confidence.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 5 findings, 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 Prompt Injection · line 79 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
- medium Prompt Injection · line 89 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
- medium Prompt Injection · line 126 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
- medium Prompt Injection · line 171 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
- medium Excessive Agency · line 197 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00080 | $0.01715 |
| Opus 5.5 | $0.00032 | $0.00686 |
| Sonnet 5.5 | $0.00016 | $0.00343 |
| Haiku 4.5 | $0.00008 | $0.00171 |
Grade A, and why
confidence 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 19d 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 — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Confidence Assessment
Rate your confidence that the current work fully solves the stated requirement.
Plan mode is gated on two signals — LLM dimensional scoring and deterministic rule checks; rationale: references/multi-signal-rationale.md.
Contents: Mode Detection · Assessment Dimensions · Output Format · Score Thresholds · Iteration Protocol
Mode Detection
Check the arguments: $ARGUMENTS
| Argument | Default | Validates | When to use |
|---|---|---|---|
plan |
Implementation plan completeness | After Phase 1 planning, before autonomous execution | |
code |
yes | Code implementation correctness | After writing code, before PR |
analysis |
Analysis accuracy (root cause, refactor rationale, or skill gap) | During investigation, before proposing a fix, refactor, or skill-source diff | |
bug-analysis |
Deprecated alias for analysis — behaves identically |
Backwards-compatible; emit a one-line deprecation note in the report header |
If no argument is provided, default to code.
Alias handling. bug-analysis resolves to analysis with identical dimensions, weights, thresholds, and Fix Mode behaviour. When invoked with the alias, prepend a single line to the report header: > Note: \bug-analysis` is a deprecated alias for `analysis`. Update the caller when convenient.`
If arguments contain "fix" (e.g., code fix, plan fix, analysis fix), run in Fix Mode: after the review, apply fixes for every concern found — read rules/fix-mode.md when in Fix Mode.
Assessment Dimensions
For plan mode
Both signals must pass for the gate to clear.
Step 1 — LLM dimensional scoring
| Dimension | Weight | What to evaluate |
|---|---|---|
| Completeness | 40% | Are ALL Phase 0 requirements captured? Are the Core sections populated (and the Extended sections present where the task needs them)? Could a new session execute from this plan alone? Do not penalize an Extended section legitimately omitted because its Include when trigger does not apply (e.g. no Existing Code Survey on a modification-only plan). Score down an Existing Code Survey whose "Searched for" column is vague ("looked around") or whose BUILD NEW verdicts show no searches — rule #10 checks presence, this dimension checks search quality. |
| Feasibility | 30% | Is the technical approach sound? Are patterns consistent with the codebase? Are risks identified where applicable? |
| No ambiguity | 30% | Are implementation steps specific enough to execute without interpretation? Are edge cases addressed where applicable? |
What ships with it
3 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.
- 19d ago Changed · -97 lines · -23 tokens per session dc8cfcefda5f
- 2mo ago First seen · 238 lines · 103 tokens per session scan A 1b3afa022211
confidence is a skill published in the GitHub repository mthines/agent-skills (20 stars, last pushed 5d ago), licensed MIT. It adds 80 tokens to every session and 1,715 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.
confidence compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| confidencemthines/agent-skills | Skill | 20 | 5d ago | MIT | A | 80 | Claude Code |
| ego-lite-simplifycitrolabs/ego-lite | Skill | 22k | today | MIT | A | 68 | Codex |
| code-review-and-qualityshennawardana23/skillme | Skill | 4 | 25d ago | Apache-2.0 | A | 86 | Claude Code |
| code-simplificationshennawardana23/skillme | Skill | 4 | 25d ago | Apache-2.0 | A | 74 | Claude Code |
| coding-standardsshennawardana23/skillme | Skill | 4 | 25d ago | Apache-2.0 | A | 106 | Claude Code |
| doubt-driven-developmentshennawardana23/skillme | Skill | 4 | 25d ago | Apache-2.0 | A | 81 | Claude Code |
| best-practicesshennawardana23/skillme | Skill | 4 | 25d ago | Apache-2.0 | A | 49 | Claude Code |